Cookie consent for SaaS companies
Your marketing site runs ad and analytics tags. Your app runs product analytics and support chat. allowedit covers both with one consent choice and an API your developers will like.
Starting product analytics in your app
analytics.init() on page load
allowedit.onChange(c => c?.analytics && analytics.init())
What goes wrong
- Product analytics and session replay tools start recording the moment the app loads, before anyone has agreed.
- The marketing site and the app use different consent setups, so visitors are asked twice or not at all.
- Engineers end up hand-writing consent checks around every SDK, and they drift as tools are added.
- Marketing adds new tags through Google Tag Manager that nobody on the engineering side reviews.
How allowedit helps
A JavaScript API
Read consent with window.allowedit.getConsent(), react to changes with onChange(), and start your product analytics only when it's allowed.
Tag Manager triggers
An allowedit_consent dataLayer event after every choice, plus Consent Mode v2, so marketing can set up tags without engineering.
Session recording waits
Hotjar and Microsoft Clarity are blocked until analytics is allowed. Add a rule or a manual tag for other tools.
Proof for security reviews
Customers' security questionnaires ask how you handle consent. The consent log and DPA give you the answer.
Setup checklist
- Add the script first in the head of your marketing site and your app shell.
- Load product analytics, replay and chat SDKs only after window.allowedit.getConsent() allows their category, and listen with onChange().
- Use the allowedit_consent event as a trigger for tags in Google Tag Manager.
- Add a Cookie settings link to your app's account menu with data-allowedit="settings".
- Scan the marketing site and categorise what it finds; the app's signed-in pages need a manual review.
Tips
- Treat your authentication and session cookies as necessary, and keep them that way so sign-in never depends on a banner.
- Error monitoring that doesn't track individuals is often argued to be necessary; anything that records sessions isn't. Decide with your legal adviser and categorise accordingly.
- If your app is on a subdomain (app.yourproduct.com), add it under the same site so the banner runs there too.
- Wrap analytics start-up in one helper that checks consent, rather than checking at every call site.
Can one choice cover the marketing site and the app?
A site in allowedit covers its domain and its subdomains, so yourproduct.com and app.yourproduct.com can share one banner. Whether a choice carries across subdomains depends on where the consent cookie is set; the docs explain how to check.
If your app is on a different domain entirely, add it as a second site. Pro covers three sites.
What about the scanner and signed-in pages?
The scanner can't sign in, so it won't see cookies that only appear inside your app. Review those by hand and add them with a category, or rely on the JavaScript API so app tools never start without consent.
Questions
Do I need consent for product analytics in my app?
For EU, UK and Quebec users, analytics that use cookies or similar storage generally need consent, even inside a logged-in product. Some tools can run without cookies; check with your adviser how yours is set up.
Is there an npm package?
No. The script tag defines window.allowedit, and you call it from your code. That keeps the banner and its settings in one place.
Which plan fits a SaaS company?
Free covers 1 site. Pro, $10 a month, covers 3 sites, such as a marketing site, a docs site and an app on another domain, and keeps a year of consent records.
Related guides
Features and guides
Cookie consent that just works
Free for 1 site with every feature. One flat price when you need more. No card needed.
Create a free account