Consent Mode lets you connect your consent management platform (CMP) to Brij once, and Brij enforces your consent configuration in every Brij experience and registration form you run. Registrations keep flowing into Brij and your CRM; what changes is whether a given event is forwarded on to your ad platforms.
This article explains how Consent Mode works, what your CMP needs to support, what happens in each consent scenario, and how to control Consent Mode per ad platform integration.
Use Cases
- You operate in regions that require a cookie banner. Consent Mode makes sure a shopper's rejection is respected on every downstream Signal transmission — without you configuring anything campaign by campaign.
- You want retail signal in some ad accounts but not others. Consent Mode is toggled per ad platform integration, so you can apply it exactly where your policy requires it, and nowhere it doesn't.
- You still want the customer, even when you can't share the signal. A rejected event is still saved in Brij as first-party data and still flows to your connected CRM or lifecycle tools. You keep the customer; the ad platforms just don't get that event.
What Your CMP Needs to Support
Consent Mode works with any consent management platform, as long as it meets two requirements.
1. It can be installed on external sites via a header code snippet
Your CMP must be able to be installed on a domain other than your primary website — specifically, on your Brij experiences — by way of a header script snippet. Most CMPs support this, but some gate multi-domain or external-site installation behind a specific pricing tier. If your CMP does not appear to allow it, check your plan level before assuming it isn't possible. Also consider if you have a custom subdomain setup in Brij, like qr.brand.com, then this is the same root domain as your website and your CMP may or may not count this as a second website.
2. It must be configured to set Google Consent Mode in the browser
Brij reads consent preferences from Google Consent Mode signals in the browser. Your CMP must be configured to set those signals — if it doesn't, Brij has no consent state to read and cannot enforce your configuration. This allows us to automatically be compatible with every CMP instead of building each integration one by one.
Most CMPs do this by default, because the same configuration is needed on your own website for Google Ads and Google Analytics. In practice this is usually already switched on, but it is worth confirming with whoever manages your CMP before go-live.
Note: If either requirement isn't met, Consent Mode cannot function as described in this article. Confirm both with your CMP administrator during setup.
How Consent Mode Works
Step 1: Connect your consent management tool
- Go to your Brij Settings > Custom Code page and paste your consent management tools code snippet into the "Head" text area. Your CMP can provide this code snippet.
- That's the whole setup. Once connected, Consent Mode runs inside every Brij experience and registration form automatically.
There is no per-campaign or per-experience work, and nothing to rebuild when you launch something new.
Step 2: You decide where banners appear
You control which regions and pages show a consent banner from inside your own CMP, following your own legal team's guidance. Brij enforces the configuration you set — Brij does not advise on where banners should appear.
Step 3: Brij enforces consent on every event
From that point on, every registration saves the shopper's consent state before Brij forwards anything to an ad platform.
What Happens in Each Scenario
| Scenario | Saved in Brij (first-party data) | Forwarded to ad platforms |
|---|---|---|
| No banner required — there is no consent to decline | Yes | Yes — normal Signal behavior |
| Banner shown, shopper accepts | Yes | Yes — normal Signal behavior |
| Banner shown, shopper rejects (and Consent Mode is enabled for that integration) | Yes | No — the event is held back |
Note: A rejected event is not a lost registration. The purchase and profile are still captured in Brij and still available in your dashboard, exports, API, and connected CRM. Consent Mode only governs onward transmission to the ad platforms.
What the Shopper Sees
|
The banner appears inside the Brij experience, driven by your connected CMP. What the shopper chooses determines where their submission goes:
- Accept All — the submission flows to all of your connected integrations, including Signal (Meta, Google, TikTok) and your CRM or lifecycle tools.
- Reject (any category) — the submission is not sent to Signal, so no event is forwarded to the ad platforms. It still flows to your CRM or lifecycle tools if you have one connected, and it is still saved in Brij.
Turning Consent Mode On or Off Per Platform
Consent Mode is configured per ad platform integration, at your direction. You can enable it for one platform and leave it off for another, depending on what your policy and legal guidance require. If Consent Mode is not enabled for a given integration, that integration is not subject to the consent hold described above.
Tips & Notes
Note: Brij enforces the consent configuration you set. Decisions about where banners are required, which categories map to ad platform sharing, and whether Consent Mode should be enabled for a given platform are yours to make with your own legal counsel.
Note: Consent Mode applies to Brij experiences and registration forms. It does not change how your own website tags or your CMP behave outside of Brij.
FAQ
Which consent management platforms are supported?
Any CMP will work, provided it can be installed on external sites through a header code snippet (sometimes this requires a particular plan tier) and is configured to set Google Consent Mode in the browser, which is where Brij pulls consent preferences from.
Do I need to configure Consent Mode for each campaign or experience?
No. Setup is a single step in Brij settings. Once your CMP is connected, Consent Mode runs inside every Brij experience and registration form automatically.
If a shopper rejects consent, do we lose the registration?
No. The event is still saved in Brij as first-party data and still forwarded to your CRM or lifecycle tool if one is connected. Only the transmission to the ad platform is held back.
Can I enable Consent Mode for Meta but not for Google or TikTok?
Yes. Consent Mode is toggled independently per ad platform integration, at your direction.
Where do banners appear? Can Brij tell us where we need them?
You configure where banners appear inside your own CMP, following your own legal guidance. Brij enforces what you set but does not advise on consent requirements. Please direct any legal interpretation questions to your own counsel.
Which consent scenarios typically trigger a banner?
Banner requirements vary by jurisdiction — commonly some US states and the EU under GDPR. Because requirements change and depend on your specific operations, confirm the applicable rules with your legal team rather than relying on a general list.
What is Brij's compliance posture?
Brij is SOC 2 Type 1 compliant, supports GDPR and CCPA workflows, and hashes consumer identifiers with SHA-256 before transmission. Your data stays customer-owned — your customer, your signal, your CAPI, your CRM.