Consent Signal Ownership

This guide explains how consent signals work in Conversion Bridge and how to configure them without conflicts.

Why This Setting Exists

Consent signals must be managed in one place.

If both your cookie banner and Conversion Bridge send consent updates to the same platform, you can get:

• conflicting consent states
• duplicate updates
• missed or unreliable conversion tracking

Recommended Setup

Use Conversion Bridge as the signal owner for supported platforms.

Why:

• Conversion Bridge listens to banner consent choices
• Conversion Bridge then maps those choices to each platform correctly
• most banners mainly handle Google consent mode, but not every ad/analytics platform equally

What To Disable In Your Banner

If a platform is set to Conversion Bridge ownership, disable that platform's built-in consent mode in your banner.

Example:

• if GA4 or Google Ads ownership is set to Conversion Bridge, disable Google Consent Mode in the banner plugin

When To Use "Consent Banner" Ownership

Use Consent Banner ownership only when your banner has a strong, native consent integration for that exact platform and you want the banner to control it directly.

If you are unsure, use Conversion Bridge.

How Runtime Consent Works (High Level)

1. Page loads with consent denied defaults for platforms that require it.
2. Banner provides current consent state to Conversion Bridge.
3. Conversion Bridge updates category/platform consent state.
4. Platform listeners receive consent updates and activate/send tracking when allowed.
5. Conversion events run once per event guard and respect current consent state.