Consent management across a municipal estate

A municipality does not run one website. It runs the main portal, district sites, participation platforms, cultural venues and a long tail of campaign sites, and every one of them needs the same consent decision applied the same way. This handles the estate from one place.

  • One configuration, every site
  • Billed per domain, not per visitor
  • Every site in one dashboard

From €36 a month. No credit card, no per-visitor billing.

Where consent gets hard across an estate

A single site is straightforward. The difficulty is doing the same thing forty times and keeping it that way.

  1. Every site drifted somewhere different

    Sub-sites are built by different teams and agencies over years, so one carries a different banner, one loads a tag nobody remembers adding, and one has no banner at all. Nobody holds a full list of what is out there.

  2. Per-visitor pricing makes the bill unpredictable

    A campaign site can go from nothing to the busiest property in the estate in a week. Pricing that moves with traffic turns a communications success into an unplanned invoice, and it punishes exactly the archive a public body is obliged to keep online.

  3. The archive still counts

    A municipality cannot take down the sites nobody visits. Election information, finished projects and statutory notices stay up for years, they still set cookies, and they still need a compliant banner even though their traffic is close to zero.

  4. One change, forty deployments

    When the law shifts or a new vendor is approved, the update has to reach every site. If that means a separate request to each site’s builder, most of the estate is out of date most of the time.

What running the estate from one place gives you

  • One configuration, applied everywhere

    Set the categories, the wording and the vendor list once. Every site inherits it, and a new site starts covered instead of starting from a blank banner that somebody has to remember to fill in.

    • Inherited defaults
    • One vendor list
    • New sites start covered
  • Billed per domain, not per visitor

    The price follows the number of sites, not the traffic across them. A campaign that goes viral and an archive nobody opens cost the same, so the figure is something a team can budget a year ahead.

    • Traffic-independent
    • No page limits
    • Predictable annually
  • Every site in a single dashboard

    The main portal and the smallest campaign site sit in the same list, with the same scan history and the same consent records. Finding the one site with an unapproved tag takes a filter rather than an audit.

    • One site list
    • Shared scan history
    • Records in one place
  • A weekly scan that finds what drifted

    Every site is crawled each week and new tracking is checked against the approved vendor list, so a tag added to a district site in a hurry surfaces within days rather than at the next external review.

    • Weekly crawl
    • Checked against approved vendors
    • Flagged within days

How a rollout usually goes

  1. Start with the main portal

    Put the busiest site live first. It sets the configuration the rest of the estate inherits.

  2. Pull in the known sites

    Add the sites communications and IT already track. Each is scanned as it joins, and the first scan is usually where the surprises are.

  3. Find the rest

    The sites nobody listed show up in DNS records and analytics. Add them, scan them, and the estate is finally a known quantity.

  4. Hand it to the site owners

    Each owner gets their own view and can adjust wording within the bounds you set, while the central configuration still holds.

Start on Professional, not Essential

Essential is enough to be compliant, but Professional is the sensible default across an estate: it sets the consent cookie server-side, so a choice lasts and a resident who visits twice a year is not asked again. Billing is per domain either way, and large estates should start on Enterprise.

Professional

€36/month

For growing teams that run on data, and the agencies serving them.

  • Server-side consent cookies
  • Consent re-prompting
  • Every add-on included
Try Professional for FreeNo credit card required. 7 day free trial.
  • Essential

    €10/month

    For a single site that has to be compliant, and stay that way.

    Try Essential for Free
  • Enterprise

    From €250/month

    For a volume, or an obligation, a standard plan cannot answer.

    Explore Enterprise
  • Agencies & Resellers

    Buy at a partner rate and resell client sites at your own price.

    Discover Partner Programme
  • Public Sector

    Government, healthcare and education run on Enterprise.

    See Enterprise

Trusted by public bodies that get audited


  • Philips, the Dutch electronics group, using Consent Studio for cookie consent
  • Gemeente Leiden, a Dutch municipality running Consent Studio on its public websites
  • Erasmus Universiteit Rotterdam, managing cookie consent with Consent Studio
  • America Today, a fashion retailer using Consent Studio across its webshop
  • Van Vulpen, an infrastructure contractor using Consent Studio for cookie consent
  • EuroParcs, a European holiday park operator running Consent Studio on its booking sites
  • Optica, a Dutch opticians chain using Consent Studio for consent management
  • Movisie, the Dutch social policy institute, managing cookie consent with Consent Studio
  • Jeans Centre, a Dutch fashion retailer using Consent Studio for cookie consent
  • Mondiaen, a Tilburg primary school foundation, running Consent Studio across its school websites
  • Nederlands Jeugdinstituut, the Dutch national youth institute, running Consent Studio on its websites
  • Fiterman Pharma, a pharmaceutical company using Consent Studio for cookie consent
  • Eddie Rockets, a hospitality group managing cookie consent with Consent Studio
  • Veneta, a kitchen retailer using Consent Studio for consent management
  • MS Mode, a fashion retailer running Consent Studio across its European webshops

Questions from municipal teams

We run dozens of sites. Does the price scale with all that traffic?

No. Billing is per domain, so you pay for the number of sites under management and the traffic across them does not change the figure. That is what stops a busy campaign month from producing a surprise invoice.

Do we have to migrate every site at once?

No. Sites come in one at a time, usually starting with the main portal, and each is scanned as it joins. The estate can be brought in over weeks without a single switchover date.

Can individual site owners still make changes?

Yes, within bounds you set. A site owner can adjust wording and see their own scan results, while the categories and the approved vendor list stay centrally controlled.

What about the old sites nobody visits?

They are covered on the same terms as the busy ones. Because billing is per domain rather than per visitor, an archive with almost no traffic costs the same as a live service, and it still gets a weekly scan and a compliant banner.

What does Consent Studio cost?

Ten euro a month per domain, with no limit on pages and no billing per visitor. That covers the banner, the tag manager and the weekly scan together, because all three are on every plan. Agencies and organisations running many domains have a partner rate, and organisations outside the fair use range have an Enterprise plan.

Where is our consent data stored?

In Amsterdam, on infrastructure owned and operated by Scaleway, a French company. That matters beyond the map pin: Scaleway is independently French rather than a European subsidiary of a US parent, so neither they nor we fall under the US CLOUD Act. Consent Studio itself is built and owned in the Netherlands by Vallonic.

Get Started with the Full Consent Stack

Everything you need in one bundle. Consent Studio provides you with a consent banner, scanner and client-side tag manager that guarantees no data ever gets transferred overseas.

Read the documentation

Our help center walks through every integration, plugin and template step by step, with screenshots. It is written and kept current by the people who build Consent Studio.

Which privacy policy?

We publish two, and they cover different audiences. Pick the one that describes you.