Partner program
You pick the tools your clients trust. Earn on every one.
You are already the one your clients lean on for compliance. Refer them to ConsentStack through the partner program and earn a share of every invoice they pay, for as long as they stay. Up to 50% lifetime, paid monthly. The consent conversation you are already having becomes recurring revenue.
Up to 50% lifetime
Every partner starts at 15% and climbs to 50% at the top tier. You earn on every invoice your referred clients pay, for as long as they stay.
Paid every month
Commissions pay out on the 1st via Stripe. No minimums, no caps, no invoicing us. One KYC flow and the payouts handle themselves.
Compounds across your roster
Every client you bring stacks another recurring line. A portfolio of referrals becomes a portfolio of monthly income.
Compliance scanner
The audit is the pitch.
Drop any client or prospect domain into the free scanner and see exactly what is firing before consent. Hand them the report, scope the cleanup, win the work. Every new client arrives with a predecessor's tracker mess, and from there every consent decision is logged into an audit trail you can hand the client.
See it before you pitch
Drop a prospect's domain and the scanner flags every tracker firing before consent. Walk into the call already knowing what is broken.
Scope the cleanup fast
On a new client, the scanner replaces the by-hand audit of an inherited setup. Know what the last agency left behind in seconds, not an afternoon.
Hand over the proof
The report is a deliverable. Show the client the leak on their own site, then show it gone the day after you ship.
Honest blocking
Do exactly what you told the user.
When a visitor declines, a client's trackers actually stop. Most banners gate the script tag and let pixels keep firing through a downstream integration, so attribution breaks in ways you cannot debug and you get the angry email when an EU user screenshots Meta Pixel still loading. ConsentStack gates third-party requests at the network layer, so a decline blocks the request before it leaves the browser.
The request never fires
Decline, and the call to Meta, Google, or Klaviyo never leaves the browser. Blocked, not recorded as a preference and hoped honored downstream.
Attribution stays debuggable
Your client's analytics reflect what consent actually allowed. No silent fire-through to explain away when the numbers look off.
Provable in the network tab
Decline, open devtools, and the trackers simply are not there. The kind of proof you can show a client who is worried.
Multi-site
Every client, every jurisdiction, one team.
Hold your whole roster under one team. Each client site gets its own regional defaults: GDPR for the EU brand, CCPA for the California store, Quebec's Law 25 for the bilingual one, resolved per visitor at the engine layer. Per-site analytics and logs live on the same team home, so you check any client without a separate account per login.
One login, every client
Your whole client roster lives under one team. No separate account per site, no password spreadsheet, no per-client login dance.
Defaults per jurisdiction
Each site ships the rules its client's region calls for, resolved per visitor. The EU brand and the California store do not share one compromise config.
Per-site logs and analytics
Open any client from the team home and see their consent logs and opt-in rates. The evidence is there per site the day a client asks.
One install
One script tag. Any stack.
Your clients are on Webflow, Shopify, WordPress, Wix, Framer, and the occasional custom build. ConsentStack is one script tag that drops into all of them, no per-CMS plugin to maintain, no snowflake integration per client. Paste it once per site and the banner, blocking, and logging come with it.
No per-CMS plugin
Skip the WordPress plugin, the Shopify app, the Webflow embed quirks. The same tag behaves the same way everywhere your clients build.
Paste once, done
Drop the snippet in the site head and you are live. No build step, no package install, no deploy pipeline to touch.
Updates without redeploys
Change a client's banner or rules from the dashboard and it propagates. You do not redeploy six client sites to fix a typo.
“Your agency reputation is on the line. If a client gets fined, they will blame their developer.”
Finsweet, Consent Pro audit of Webflow sitesWebflow consent tool, cited as field admission.
Common questions
Yes. One team holds your whole client roster. Each client site is its own property with its own regional defaults, consent logs, and analytics, all reachable from the team home without a separate login per client. Per-site billing keeps each client's subscription clean.
Pricing is per site, by unique monthly visitors. Pro is $29/mo and includes 2 domains; extra domains are $5/mo each. There is no per-domain enterprise tax and no separate account required per client. An agency running many client sites pays a flat plan per site plus $5 for each extra domain, not a compounding per-domain rate.
Yes. ConsentStack signals consent state to Google, Meta, TikTok, Microsoft, LinkedIn, and analytics SDKs using the signaling each platform expects, and blocks only what the visitor's jurisdiction requires. Consented traffic keeps flowing to your client's marketing stack; declined traffic is actually blocked at the request layer.
You can remove ConsentStack branding from client banners on the Pro plan and above, and theme the banner to match each client's site with color tokens, layouts, and custom CSS. Fully agency-branded, co-labeled white-label is on the roadmap, not shipped today. The honest answer is remove-our-branding now, your-logo-on-the-banner later.
Yes. The free compliance scanner takes any domain and flags every tracker firing before consent, with no account required. Run it on a prospect to scope the work and open the conversation, or on a new client to see what the previous setup left behind.
ConsentStack is built for agencies that want trackers to actually stop on a decline, fair per-site pricing instead of compounding per-domain fees, and a banner that matches each client's brand. CookieYes leans on per-domain plans and free-tier limits; Termly pairs a policy generator with its banner. For agencies standardizing a portfolio on one honest engine, ConsentStack is the cleaner fit. See ConsentStack vs CookieYes and ConsentStack vs Termly for details.
100+ happy customers
Consent, handled for every client. Forever.
Audit a site, deploy in minutes, and earn on every client you bring. Get back to the work they actually hired you for.