Mitigating Google Tag Manager and consent

Installing our tag using the Google Tag Manager template means that GTM will write configuration settings to localstorage before consent. This is a feature of GTM and not our marketing script. To mitigate this action, we have compiled a list of known approaches that you may choose to use.

Google Consent Mode

For Google Consent Mode to work you must be sure that your Consent Management Platform (CMP) is compatible with Google Consent Mode and is capable of applying the required ad_storage consent flag.

Google Tag Manager includes features that help you manage how tags behave in response to consent settings, these are available via Consent Mode.

To use Consent Mode, we advise you to enable Consent Overview on your GTM container as follows:

1. In Tag Manager, click Admin > Container Settings.

2. Under Additional Settings, select Enable consent overview.

To ensure that the Anonymised GTM template tag does not fire without consent, please add the consent flag using the following steps:

1. Under Tags, locate and open the Anonymised marketing tag.

2. Expand the option Advanced Settings under Required settings.

3. Expand the option Consent Settings (Beta) under Advanced Settings.

4. Choose the option Require additional consent for tag to fire under Consent Settings (Beta).

5. Click the button + Add required consent.

6. Select the option ad_storage.

7. Click the Save button to save the changes.
   

Custom trigger using CMP event

If you are not using Google Consent Mode in Google Tag Manager, it is possible to use a custom trigger and the functionality of your CMP. The success will depend on the CMP being used and your development resources.

For the most common CMP, here is a list of their guidance or recommendations:

This list is not exhaustive and we recommend you refer to either Google’s guidance or that from your CMP. We will attempt to update this list from time to time, in line with our awareness.

Custom tag instead of GTM template

Our marketing tag in native form listens for consent before taking any action, so deploying it as a custom tag is also a recommended approach.

To deploy Anonymised as a GTM custom tag follow these steps:

1. Receive your client ID from your Customer Success Manager or Support.

2. Open Google Tag Manager and navigate to and open the relevant container.

3. Select Tags and click on New.

4. Select Custom HTML under Choose tag type.

5. Add the following code to the HTML box:

   CODE

   <script async
          src="https://static.anonymised.io/light/loader.js"
          id="idward-plugin-js"
          idw_client_id="{Your Client ID}"       
          idw_hide_button="true"
   ></script>

   ^{Note: replace {Your Client ID} with the client ID your Client Success Manager has given you, or contact support if you have not yet received it. For example: client ID XCPe would appear as: idw_client_id=”XCPe”. Client IDs are case-sensitive, please type as instructed.}

6. Name the tag using a suitable nomenclature, for example, CT - Anonymised tag.

7. For the Trigger, whether you are using Google’s Consent Mode or a Custom CMP Event, you will need to follow the guidance provided by your Consent Management Platform.

8. Click Save.

9. Publish the GTM container.

10. Advise your Client Success Manager or support of the domain(s) on which the tag has been deployed.