Google Tag Manager Setup

Follow this setup if you are using Google Tag Manager to manage your third-party scripts.

Prerequisites

Before starting this setup, ensure you have:

• A Google Tag Manager account
• Administrative access to your website
• Consent Pro installed and configured on your website

1. Remove the <noscript> Tag from Google Tag Manager

Go to Site Settings > Custom Code and remove the Google Tag Manager <noscript> tag from the Footer code.

2. Import the Consent Pro Template to Google Tag Manager

1. Download the Consent Pro GTM template: Download GTM Template
2. Open your Google Tag Manager container.
3. Navigate to ’Templates’ in the left sidebar.
4. In the ’Templates’ tab, click ’New’.

5. Click the three dots icon (⋮) in the top-right corner and select ’Import’.

6. Select the Consent Pro - GTM Template.tpl file you just downloaded. The Template Editor will load with the Consent Pro configuration.

7. Agree to the Community Template Gallery Terms of Service, then click ’Save’ to add the template to your workspace.

8. Close the Template Editor.

Done ✅

3. Create the Consent Initialization Tag

1. In the ’Tags’ section, click on ’New’.

2. Click on ’Tag Configuration’

3. Select ’Consent Pro - GTM Template’ from the list in the Custom section.

4. Click on “Triggering”.

5. Select ’Consent Initialization - All Pages’. This is crucial as it ensures Consent Pro loads before any collection tags.

6. Name your tag (e.g., "Consent Pro Init") and click ’Save’.

You have successfully added the Consent Init tag ✅

4. Configure Region-Specific Consent Settings

Region-specific consent settings allow you to define default consent states based on the user's geographic location. This is particularly useful for complying with regional privacy regulations such as GDPR in the European Union or CCPA in California.

By configuring these settings, you can ensure that users from specific regions have their consent preferences initialized appropriately before any tags fire, providing a compliant and seamless experience across different jurisdictions.

1. In the ‘Tags’ tab, select the ‘Consent Pro Init’ tag you just added.

2. Click on ‘Tag Configuration’.

3. Click on the ’Region-Specific Consent Settings’ accordion to expand it.

4. Click ‘Add Region Setting’ to create a new region configuration.

5. Select the storage fields based on the examples below.

If you have an ‘Opt-in banner’ added to Consent Pro,

Select ’Denied’ in all fields.

If you have an ‘Opt-out’, ‘Do Not Sell’ or ‘Informational Banner’ added to Consent Pro,

Select ’Granted’ in all fields.

	Opt In	Opt Out	Don't Sell	Informational
Analytics Storage	Denied	Granted	Granted	Granted
Ad Storage	Denied	Granted	Granted	Granted
Functionality Storage	Denied	Granted	Granted	Granted
Personalization Storage	Denied	Granted	Granted	Granted
Ad User Data	Denied	Granted	Granted	Granted
Ad Personalization	Denied	Granted	Granted	Granted

Why this matters

• Opt In (e.g., GDPR): Users must explicitly consent before any tracking. GTM defaults must be Denied so tags don't fire until consent is given.
• Opt Out / Don't Sell / Informational: Tracking is allowed by default. GTM defaults should be Granted since users can opt out later if they choose.

6. Fill in ‘Regions’ with the region you selected when you created the banner.

Go to ‘Banners’ and click the copy button to copy the regions in the ‘Regions’ column.

Paste them into the ‘Regions’ field in Google Tag Manager.

7. Click ‘Add’ to finish the region settings.

Note: If you have more than one banner created in Consent Pro, feel free to add more region settings. Here is an example of a setup with multiple banners.

8. Optional: Review whether you need advanced settings.

• Wait for consent update: Default is 1000ms. This defines the time to wait for a consent update before firing tags. Prevents tags from firing before user consent is processed. Recommended: 500-2000ms.
• URL passthrough: Enable if you want to pass advertising click information (gclid, dclid, etc.) through URLs while waiting for consent. Helps preserve attribution data during consent flow.
• Ads data redaction: Enable if you want to remove advertising identifiers from requests when consent is denied. Routes traffic through cookieless domains for privacy compliance.

9. Click 'Save' to finish the Regions setup.

5. Create triggers for the consent categories

To ensure proper detection and blocking, the triggers must be changed to use custom events from our solution. This allows us to detect the scripts and block them before they load.

5.1. Create a trigger for Essential Cookies

1. Go to 'Triggers' and click 'New'.

2. Name it 'Essential Cookies' and click on 'Trigger Configuration'.

3. Choose 'Custom Event'.

4. Fill 'Event Name' with 'essential-activated', select 'Some custom Events’, select 'Event', choose 'equals', and enter 'essential-activated'.

5. Click 'Save'.

If you want more control over when to fire your tags, click on '+' button.

And select the conditions you want. They can be triggered when a user accesses a specific page or when another custom event occurs:

5.2. Create a trigger for Marketing Cookies

1. Go to 'Triggers' and click 'New'.

2. Name it 'Marketing Cookies' and click on 'Trigger Configuration'.

3. Choose 'Custom Event'.

4. Fill 'Event Name' with 'marketing-activated', select 'Some custom Events’, select 'Event', choose 'equals', and enter 'marketing-activated'.

5. Click 'Save'.

If you want more control over when to fire your tags, click on '+' button.

And select the conditions you want. They can be triggered when a user accesses a specific page or when another custom event occurs:

5.3. Create a trigger for Personalization Cookies

1. Go to 'Triggers' and click 'New'.

2. Name it 'Personalization Cookies' and click on 'Trigger Configuration'.

3. Choose 'Custom Event'.

4. Fill 'Event Name' with 'personalization-activated', select 'Some custom Events’, select 'Event', choose 'equals', and enter 'personalization-activated'.

5. Click 'Save'.

If you want more control over when to fire your tags, click on '+' button.

And select the conditions you want. They can be triggered when a user accesses a specific page or when another custom event occurs:

5.4. Create a trigger for Analytics Cookies

1. Go to 'Triggers' and click 'New'.

2. Name it 'Analytics Cookies' and click on 'Trigger Configuration'.

3. Choose 'Custom Event'.

4. Fill 'Event Name' with 'analytics-activated', select 'Some custom Events', select 'Event', choose 'equals', and enter 'analytics-activated'.

5. Click 'Save'.

6. If you want more control over when to fire your tags, click on '+' button.

7. And select the conditions you want. They can be triggered when a user accesses a specific page or when another custom event occurs:

6. Update how the scripts are triggered for Cookie compliance

1. Ensure the website was scanned recently, or scan the website again.

Our solution will detect the scripts added to Google Tag Manager and help you categorize them. This is an important step to make sure the categories match in the app and in Google Tag Manager.

And also to show users the tracker details in the preferences panel.

Note: Our solution only detects scripts from Google Tag Manager that are triggered on “All Pages” or with Consent Pro custom events such as “essential-activated”, “marketing-activated”, “analytics-activated”, and “personalization-activated”. If you use a different trigger or another consent tool, update the triggers to “All Pages” to continue the setup.

⚠️ If your script uses document.write, make sure to enable “Support document.write” in the tag settings. Otherwise, the script may not execute correctly and may not be detected by Consent Pro.

2. Select the tag in the ‘Tags’ tab. For this example, we are going to use the 'Facebook Pixel' tag:

3. Click on 'Edit icon'.

4. Remove the current trigger.

5. Click on 'Triggering'.
6. Select the category based on the category labeled in the app.

That means the Facebook Pixel script will only load when the user consents to the 'Marketing' category or clicks on 'Accept All'.

7. Do the same for all your tags added to Google Tag Manager.

7. Add additional consent checks for each tag to comply with Google Consent Mode V2

1. Select the tag you want to add the additional consent check. For this example, we are going to use the 'Facebook Pixel' tag again:

2. Click on ‘Tag Configuration’.
3. Go to 'Advanced Settings' > 'Consent Settings' and select 'Require additional consent for tag to fire'.

4. Choose the additional consents based on the previously selected trigger (check the visual reference below):

5. Visual reference for mapping the Consent Pro categories with additional consents:

Add the additional checks to every tag inside Google Tag Manager that requires user consent.

8. Submit and publish the changes in Google Tag Manager

1. Click on 'Submit'.

2. Click 'Publish'.

9. Confirm that the Google Tag Manager setup is completed in the Consent Pro app

In the ‘Actions’ tab, check the checkbox in the Google Tag Manager message within the Consent Pro app.