A CookieYes alternative that sets the banner up with you
Self-serve consent tools look identical on the pricing page. A banner, a scanner, some categories, a per-domain price. The difference turns up two weeks later, when you're trying to work out why your analytics numbers moved.
One Privacy covers the same ground and adds the part most tools leave to a documentation link: we wire the Google Tag Manager side with you, so your tags really do wait for consent.
Switching consent tools is mostly a load-order problem
The banner is the easy half. The hard half is that consent state has to be set before your tag manager runs, and every tool words that setup slightly differently. Get it wrong and you keep a banner that looks correct while the tracking has already fired.
Install One Privacy above your tag manager, run a scan, then open a fresh incognito window with the network tab up. Nothing non-essential should leave the page before someone clicks.
What to test before you move
Two tools with the same feature list can still behave differently on your site. These are worth checking yourself rather than reading about.
- Run a fresh scan and compare the result against your dev tools on a few real pages.
- Export your existing consent records before you cancel anything.
- Load the site through a VPN in two regions you sell into and confirm each gets the banner its law expects.
- Watch the network tab before first click, on whichever page carries the most third-party scripts.
Where we spend the effort
Scans run on a schedule so the cookie list keeps up with the site instead of describing it as it was at signup. Region rules decide what each visitor sees, so an EU visitor gets the opt-in flow and a California visitor gets the opt-out one from a single install.
Every decision is stored with the banner version and the categories on offer at that moment, which is what proving consent actually takes. The log exports whenever you want it.
The setup session is the point
Most tools hand you a snippet and a link to the docs. That works if you already know how consent triggers behave in Google Tag Manager. If you don't, you end up with a compliant-looking banner sitting on top of tags that never waited for it.
We sit through that part with you, on the free plan as well. It is the one thing we would not cut.
What actually differs
| Most self-serve consent tools | One Privacy | |
|---|---|---|
| Tag manager setup | Docs and a support ticket | We wire it with you, on any plan |
| Support on the free plan | Often docs or community only | Email support, answered by the builders |
| Pricing unit | Varies by site size or session count | Per domain, every limit published |
| Consent records | Stored, export varies by plan | Exportable, with the banner version kept |
| Getting started | Free tier or a timed trial | Free tier, no card, no countdown |
Frequently asked questions
How long does switching take?
Most of an afternoon. Install the script above your tag manager, run a scan, check the categories look right, then pull the old snippet. Keep both live for a day if you want to compare what each one blocks.
Can I bring my old consent records across?
Export them from your current tool and keep the file. Our log starts at install, and the export you already hold stays valid evidence for the period it covers.
Do I pay per domain or by site size?
Per domain. Page views, scans a month and pages per scan are published for every tier, so you can see the next step before you reach it.
Is the free plan enough for a small site?
Often yes. 15,000 page views a month, four manual scans, every consent template and GPC signal detection. No card, and it does not quietly turn into a paywall.
Scan your site before you decide anything
Run a free scan and compare the cookie list to what your current tool reports.
Get Started For Free