Consent across every site you look after
Consent stops being something you redo on every project and becomes one thing you run across the whole portfolio, however many stacks it spans.
- Every client in one place
- Set up once per stack
- Partner rate per domain
From €10 a month. No credit card, no per-visitor billing.
Consent gets harder the more sites you run
One site is an afternoon. Thirty is a different job, and it is not thirty afternoons. Four things change once you are running consent for other people.
You did not choose the stack
Every client arrived with what they already had. A WordPress build from four years ago, a headless front end somebody clever wrote, two sites on a platform nobody at the agency has touched since. A method that assumes one stack works on the sites you built and fails on the ones you inherited.
Tags arrive without you
A client’s marketing lead adds a remarketing pixel through the tag manager on a Friday. Nobody tells the agency, because from their side nothing broke. The site is now running a tracker that the banner does not know about, and the first person to find out will not be you.
Nothing announces the breakage
A theme update, a new plugin, a developer clearing a cache the wrong way, and the consent script stops loading. There is no error and no alert. The site keeps working, keeps selling and keeps tracking, and the only visible symptom is that the banner stopped appearing on a page nobody checks.
You get asked, and then you get blamed
The agency is who the client calls, whether or not the agency built the thing that broke. Responsibility lands on you without the authority to prevent it landing again, and that gap is the actual problem this page is about.
What running consent across a portfolio needs
Not more features. The same product, arranged so that thirty domains cost less attention than thirty times one.
Every client under one login
One dashboard listing every domain you look after, each with its own configuration and its own data. Adding a client is adding a domain, not opening another account and another invoice and another password nobody wrote down.
- One dashboard
- Separate per client
- Add a domain, not an account
A configuration you can repeat
Settle how your agency handles categories, wording and defaults once, then apply it to the next site rather than deciding it again. The second WordPress client should not cost what the first one did.
- Decide once
- Reuse per stack
- Consistent across clients
A weekly scan on every domain
Every site is crawled once a week and anything new is reported, which is what turns a tag you were never told about into an email instead of an incident. This is the part that keeps working after the project closes and the retainer thins out.
- Every domain, weekly
- Finds what was added
- Works after handover
Each client looks like themselves
Colours, wording and language follow the client rather than the agency, so the banner belongs to their brand and not to your toolkit. Regional defaults follow their visitors, which matters when one client trades in one country and another trades in nine.
- Client’s own branding
- Multilingual
- Defaults by visitor region
Agencies get Etiënne and the support team, and they genuinely take the time to learn an account and what it needs. I admire them for it, and getting these people in one room is the part of this job I am proudest of.
What an agency gets that a single site owner does not
Not what the software does. What running it for other people’s clients is actually worth.
Ten minutes, then three a site
The first client on a stack is an install and a styling pass, and most people finish in about ten minutes. Every site after it starts from the configuration you already settled, so what is left is roughly three.
It pays every month, not once
Consent is installed once and maintained for years without ever reaching an invoice. The partner rate changes that: a margin on every domain you look after, arriving monthly rather than at the point of sale. What the rate is, and who qualifies, is the Partner Programme’s own page.
A person answers, on every plan
When a client site breaks, or just does not look right, somebody who works on the product replies, within one working day and on every plan. Your client can come to us directly with you on the thread, or you stay the only voice. No ticket queue either way.
You do not wait for thirty renewal dates
A portfolio normally moves one client at a time, as each contract happens to lapse. Essential and Professional cost nothing with us until the old contract runs out, so the whole portfolio can come across now and no client pays for two platforms in the same month.
Taking on a portfolio
Start with one client
Pick a site you know well. Seven days free, and the first one is where you learn what your house configuration should be.
Settle the house configuration
Agree categories, wording and defaults once, at the agency rather than per project. This is the step that makes the rest repeatable.
Roll out per stack, not per site
Do all the WordPress clients together, then the next platform. On a batch we do the move in Google Tag Manager or Launcher and create the domains in bulk.
Let the scan hold the line
Weekly crawls report what changed on every domain, so drift after handover reaches you as a message rather than as a complaint.
The people who answer are the people who build it
Support is not a separate department here and it is not a tier you buy. The person who replies works on Consent Studio, which is why the answer is usually a fix rather than a ticket reference.
Built in Tilburg, by people you can look up
Consent Studio is made by Vallonic, in one office in Tilburg, and the names and faces are on the about page. Knowing who is on the other end is part of what you are reselling.
The tag that breaks a client site is usually one the client added themselves. An agency needs to see that without owning the site it happened on, and that is what the account structure is for.
Agencies buy at a partner rate
Agencies looking after client domains buy Essential and Professional at a reduced rate and resell at their own price. The Partner Programme page covers the rate, the tiers and how to apply.
Running on sites like these
Other things people are working out
Questions agencies ask
Do we resell it, or does the client buy it directly?
Either, and most agencies do both depending on the client. Under the Partner Programme you buy Essential and Professional at a reduced rate and resell at your own price, keeping the difference on every client you look after. Where a client prefers their own contract and invoice, they can hold the account and you keep access to it. The Partner Programme page has the detail.
We have thirty sites elsewhere. Do you help with the move?
Yes, on both halves of it. On a batch we do the migration with you, in Google Tag Manager or in Launcher, and create the domains in bulk, so the portfolio arrives as one job. And Essential and Professional cost nothing with us until each client’s existing contract runs out, so nobody pays two suppliers for the same months.
What happens after we hand a site over?
The weekly scan keeps running, which is the honest answer to the thing that actually goes wrong. Consent breaks months after launch, when somebody adds a tag or updates a theme, and by then the project is closed and nobody is looking. The crawl reports it whether or not anyone is still being paid to check.
Do we need a separate account for every client?
No. One account holds every domain you look after, each with its own configuration, its own banner and its own consent records kept separate from the rest. You are adding a domain rather than starting again.
Our clients are on different platforms. Is it a different job each time?
The first site on a given platform is, and the ones after it are not. Install routes differ, so a WordPress client and a headless build genuinely take different steps, and we have pages for the thirteen platforms we support most closely. What does not change is the configuration, which is why settling a house version early is worth more than it looks.
Can we see what a client’s site is running before we quote?
Yes, and it is usually the fastest way to size the work. The first scan lists every tag on the domain, including the ones added after launch by somebody who is no longer there. On an inherited site that list is the difference between a quote and a guess.
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.
Start with one client, or start as a partner
Either route works and most agencies take both. Try Consent Studio on a site you know well, and apply to the Partner Programme when you are ready to put it on the rest of them.
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.