How to enable cross-domain consent
Cross-domain consent is useful when you want to collect user's consent across multiple domains using a single cookie banner.
Cross-domain consent is useful when you want to collect user's consent across multiple domains using a single cookie banner. It is good for the user experience when you redirect users to multiple websites/domains. You can see a video of the functionality here.
Follow these steps to enable cross-domain consent. We assume that you have already added your domains inside the domain management panel, and onboarding is complete for all domains.
1. Install Secure Privacy script on all domains.
2. Click on All Domains and navigate to Domains page.
3. Scroll the table to the right, where you can see Domain Consent Group.
4. Edit the column Domain Consent Group for all the domains on which you want to enable cross-domain consent.
5. Make sure that the enable of each group is the same. For example in the below image the Group name is GroupA.

6. Once done, cross-domain consent is enabled for these domains.

What is Cookie Consent? A Quick 2026-Ready Glance
Your website loads. Cookies track users. But without proper cookie consent, you're violating GDPR — risking fines up to €20 million or 4% of global revenue. Cookie consent is the legally required mechanism by which websites obtain explicit user approval before deploying non-essential tracking technologies. This requirement stems from GDPR Article 4(11) and the ePrivacy Directive, mandating that consent must be freely given, specific, informed, and unambiguous.
- Legal & News

DSAR Tools Explained: Best Software for Automating Privacy Requests
You're drowning in data subject access requests. Manual searches through dozens of systems miss regulatory deadlines and expose organizations to fines starting at $2,500 per violation. The solution? DSAR tools — purpose-built software that automates the entire process of responding to data subject access requests, from intake to delivery.
- Legal & News

IAB TCF 2.3 Explained: Requirements, Updates, and Implementation Guide (2026)
Your ad revenue dropped 40% overnight. Google stopped bidding on your inventory. Your DSP partners flagged your traffic as non-compliant. The culprit? An outdated TCF 2.2 consent string after the February 2026 enforcement deadline.
- Legal & News
- Cookie Consent