This guide walks through installing the RB2B tracking script using Google Tag Manager (GTM). Proper installation ensures RB2B can identify visitors and deliver company-level and person-level insights consistently across your site.
Google Tag Manager is one supported installation method. Depending on your site architecture and consent setup, a direct script installation may be more appropriate.
Before You Begin
Before installing RB2B via GTM, review the following:
Consent Management Tools (CMPs):
If your site uses a cookie consent tool (Cookiebot, CookieYes, OneTrust, Termly, etc.), additional configuration is required. Most CMPs block GTM tags until consent is granted.Content Security Policy (CSP):
GTM does not modify CSP rules. Required RB2B domains must be explicitly allowed.Framework limitations:
GTM is not supported in certain environments (e.g. Next.js). In those cases, RB2B must be installed directly in your application.
Skipping these checks is the most common cause of incomplete or inconsistent identification.
Step 1: Copy the RB2B Script
Log in to your RB2B dashboard.
Navigate to Script.
Copy the entire RB2B tracking script.
This script enables visitor identification and powers all RB2B functionality across your site.
Step 2: Log in to Google Tag Manager
Sign in to your Google account.
Select the correct Account and Container for your website.
Step 3: Create a New Tag
In the GTM dashboard, click Tags.
Click New.
Name the tag something descriptive, such as RB2B Tracking Script.
Click Tag Configuration.
Select Custom HTML.
Google Tag Manager allows centralized script management, which can be useful for large or frequently updated sites.
Step 4: Paste the Script
Paste the RB2B script into the HTML field.
Do not modify the script unless explicitly instructed by RB2B support.
Step 5: Configure the Trigger
Option 1: Standard Setup (No Consent Tool)
Select All Pages as the trigger.
This ensures RB2B loads on every page of your site.
Option 1: Sites Using a Cookie Consent Tool (Important)
If your site uses a consent management platform, do not rely on “All Pages” alone.
Most CMPs prevent GTM tags from firing until consent is granted.
You must do one of the following:
Configure the RB2B tag to fire only after consent is granted, or
Explicitly allow the RB2B tag within your CMP’s GTM integration settings
How this is done varies by provider.
Common consent categories include:
Analytics
Marketing
Functional
RB2B does not enforce consent logic and does not bypass your CMP. If consent is denied, RB2B will not run for that visitor.
Step 6: Save and Publish
Click Save to store the tag.
Return to the GTM workspace.
Click Submit.
Name the version (e.g. Add RB2B Tracking Script).
Click Publish.
Changes do not go live until the container is published.
How RB2B Tracking Behaves After Installation
Company-level identification is enabled by default for all accounts.
Global company-level tracking is enabled by default and applies to international traffic.
Person-level identification only occurs for U.S.-based visitors and requires available credits on paid plans.
If the RB2B script does not load due to consent restrictions or CSP issues, identification will not occur.
Common Issues to Check
Consent Tool Blocking
RB2B tag never fires until cookies are accepted.
Identification appears lower than expected.
GTM preview shows the tag as blocked.
CSP Errors
Console errors referencing blocked scripts.
Script loads locally but fails in production.
Framework Limitations
GTM not supported in Next.js or similar environments.
Script must be installed directly using framework-specific instructions.
Important Notes
RB2B does not manage consent on your behalf.
You are responsible for complying with regional privacy regulations.
Ensure your privacy policy reflects company-level tracking.
GTM is not recommended for every environment.
When GTM Is Not Recommended
You should not use Google Tag Manager if:
Your site is built on Next.js or another unsupported framework.
You require precise script execution timing.
Your CMP heavily restricts GTM execution.
In these cases, a direct installation in your site’s global header is preferred.