Usercentrics (Termageddon)

The Usercentrics integration allows Conversion Bridge to respect user consent choices from the Usercentrics consent management platform. Usercentrics is a JavaScript-based consent solution that displays a cookie banner on your website and collects consent from your visitors before tracking scripts are allowed to run.

If you use Termageddon for your privacy policy and cookie consent, this is the integration you need. Termageddon uses Usercentrics under the hood to power its consent banner, so the same integration covers both.

This integration ensures that:

• Analytics tracking only runs when users consent to analytics/statistics cookiesA small piece of data stored in a user’s browser that helps websites remember user activity, preferences, or sessions across visits.
• Marketing/advertising tracking only runs when users consent to marketing cookies
• Tracking scripts are blocked until consent is given
• Consent changes are handled in real-time as users update their preferences

Setup Instructions

Step 1: Set Up Usercentrics

1. Create a Usercentrics account at usercentrics.com (or set up consent through Termageddon)
2. Install the Usercentrics CMP WordPress plugin from the WordPress plugin directory. This is the easiest way to add the Usercentrics consent banner to your site. The plugin handles loading the Usercentrics script automatically.
3. In your Usercentrics dashboard, add the services (platforms) you want to manage consent for, such as Google Analytics, Meta Pixel, Google Ads, etc.
4. Make sure your consent categories are set up. Usercentrics typically uses categories like:

• Analytics or Statistics or Functional (for analytics platforms)
• Marketing or Advertising (for advertising platforms)

Step 2: Enable the Integration in Conversion Bridge

1. Go to Settings > Conversion Bridge > Consent in your WordPress admin
2. Select Usercentrics (Termageddon) as your cookie consent plugin
3. Save your settings

Since the Usercentrics consent banner runs entirely in JavaScript, Conversion Bridge detects it automatically on the page. The Usercentrics option is always available to select in your consent settings.

Step 3: Configure Service Names (If Needed)

Conversion Bridge automatically maps the most common Usercentrics service names to the correct tracking platforms. In most cases, this works without any extra setup.

However, the service names in your Usercentrics dashboard must match what Conversion Bridge expects. If you have renamed a service in Usercentrics (for example, calling it "GA4" instead of "Google Analytics"), the automatic mapping may not work.

To fix this, either:

• Rename the service in your Usercentrics dashboard to match one of the recognized names listed in the Supported Platforms section below
• Or keep your custom name and rely on category-level consent (analytics or marketing) instead of per-platform consent

How It Works

Consent Flow

Here is what happens when a visitor lands on your site:

1. Page loads: Conversion Bridge checks if the Usercentrics API (UC_UI) is available
2. Banner appears: Your visitor sees the Usercentrics consent banner
3. Visitor makes a choice: They can accept all, deny all, or choose specific categories/services
4. Consent is communicated: Usercentrics fires JavaScript events that Conversion Bridge listens for
5. Tracking starts or stays blocked: Conversion Bridge enables or disables tracking based on the visitor's choices

Consent Detection

Because Usercentrics is a JavaScript-only solution, there are no server-side cookies for Conversion Bridge to read on page load. All consent detection happens in the browser through the Usercentrics API.

Conversion Bridge listens for three Usercentrics events:

• UC_UI_INITIALIZED: Fires when the consent banner first loads. Conversion Bridge checks the current consent state at this point.
• UC_CONSENT: Fires whenever consent changes. Conversion Bridge reads the updated consent details from this event.
• UC_UI_CMP_EVENT: Fires when a visitor clicks Accept All, Deny All, or Save. Conversion Bridge responds to each action accordingly.

Two Levels of Consent

Conversion Bridge checks consent at two levels:

1. Category-level consent: Checks broad categories like "Analytics" or "Marketing." This determines whether analytics or marketing tracking is allowed overall.
2. Service-level (platform-specific) consent: Checks individual services like "Google Analytics" or "Meta Pixel." This allows Conversion Bridge to enable or disable tracking for each platform separately.

Both levels work together. If a visitor grants consent for the "Analytics" category, all analytics platforms are enabled. If they grant consent for only "Google Analytics" as a specific service, only that platform is enabled.

Supported Platforms

Conversion Bridge automatically recognizes the following Usercentrics service names and maps them to the correct tracking platform. The service name matching is not case-sensitive.

Analytics Platforms

Marketing Platforms

If a service in your Usercentrics dashboard is not in this list, Conversion Bridge will try to determine its category based on the service name. Services with names that include words like "analytics," "statistics," or "performance" are treated as analytics. Services with names that include "marketing" or "advertising" are treated as marketing.

Script Blocking

When the Usercentrics integration is active, Conversion Bridge adds special attributes to all tracking scripts so that Usercentrics can block them until consent is given.

How Scripts Are Tagged

Each tracking script gets two attributes added to it:

• data-usercentrics="[Service Name]" -- tells Usercentrics which service the script belongs to
• type="text/plain" -- prevents the browser from running the script until Usercentrics changes the type back to text/javascript

Analytics Script Example

<script data-usercentrics="Google Analytics" type="text/plain" src="..."></script>

Marketing Script Example

<script data-usercentrics="Meta Pixel" type="text/plain" src="..."></script>

When a visitor grants consent for a service, Usercentrics unblocks the matching scripts and they begin running normally.

Platforms With Native Consent Handling

Some platforms have their own built-in consent handling (such as Google Analytics 4, Meta, and Google Ads). These platforms are not blocked by Usercentrics script blocking. Instead, they load normally and Conversion Bridge sends them consent signals directly through their own APIs. This is the recommended approach for these platforms because it gives the platform more accurate consent data.

Termageddon Users

If you use Termageddon for your website's privacy policy and cookie consent, you are already using Usercentrics. Termageddon partners with Usercentrics to power its consent banner functionality.

To set up the integration:

1. Make sure your Termageddon cookie consent banner is active on your site
2. Select Usercentrics (Termageddon) in Conversion Bridge's consent settings
3. Everything else works the same as described above

The service names and categories you configure in your Termageddon/Usercentrics dashboard will be used by Conversion Bridge to manage consent for your tracking platforms.

Debugging

Enable Console Logging

To debug the consent integration:

1. Add ?cb_console=1 to any page URL on your site
2. Open your browser's developer tools (usually F12 or right-click > Inspect)
3. Check the Console tab for consent-related messages:

• Usercentrics: Integration initialized
• Usercentrics: Consent via API: analytics=true, marketing=false
• Usercentrics: UC_CONSENT: analytics=true, marketing=true
• Usercentrics: ACCEPT_ALL
• Usercentrics: DENY_ALL

Verify Script Blocking

To confirm scripts are being blocked correctly:

1. Open your browser's developer tools
2. Go to the Elements or Inspector tab
3. Search for data-usercentrics in the page source
4. You should see your tracking scripts tagged with data-usercentrics="[Service Name]" and type="text/plain"
5. After granting consent, the script type should change to text/javascript

Common Issues

• Service name mismatch: If a platform is not responding to consent, check that the service name in your Usercentrics dashboard matches one of the names in the Supported Platforms table above.
• No consent events firing: Make sure the Usercentrics script is loading on your page. Check the browser console for any Usercentrics-related errors.
• Tracking fires without consent: Verify that you have selected Usercentrics as your consent plugin in Conversion Bridge settings. Also check that the Usercentrics script loads before the Conversion Bridge scripts.

Best Practices

1. Use standard service names: When adding services in your Usercentrics dashboard, use the default names (like "Google Analytics" instead of custom names) so that Conversion Bridge can automatically map them.
2. Test the full consent flow: Visit your site in a private/incognito window and test accepting, rejecting, and changing consent preferences.
3. Check all platforms: After setting up the integration, verify that each of your enabled tracking platforms respects consent by checking the browser console with ?cb_console=1.
4. Keep categories consistent: Make sure your Usercentrics categories use standard names like "Analytics," "Statistics," "Marketing," or "Advertising" so that Conversion Bridge can identify them correctly.
5. Review regularly: Periodically check that new tracking platforms you add to Conversion Bridge are also added as services in your Usercentrics dashboard.

Privacy Compliance

The Usercentrics integration helps you comply with:

• GDPR: General Data Protection Regulation (EU)
• CCPA: California Consumer Privacy Act (US)
• ePrivacy Directive: EU ePrivacy Directive
• LGPD: Brazil's General Data Protection Law
• Other Privacy Laws: Various regional privacy regulations

Important: This integration helps with the technical side of compliance by blocking tracking scripts until consent is given. However, you are also responsible for:

• Having a proper privacy policy
• Providing clear information about what data you collect
• Allowing users to withdraw consent at any time
• Complying with all privacy laws that apply in your jurisdiction