Prior blocking & script control — found from sitemap — Didomi

Cited by

Facts read from this source

• Gtm integration purpose Report an error

  “This article will guide you through Didomi's integration with Google Tag Manager (GTM) to configure the loading of tags on your website when there is consent from the user.”

• Gtm events Report an error

  “didomi-consent: when page has loaded, and when there is a change in consent didomi-ready: when the page is loaded didomi-consent-changed: when there is a change in consent”

• Gtm variables Report an error

  “Vendors (subset variables: consent given/ consent denied/ consent unknown) Purposes (subset variables: consent given/ consent denied/ consent unknown) Vendors and purposes (subset variables: consent given/ consent denied/ consent unknown) IAB TCF Consent string / GDPR (if GPDR applies)”

• Gtm most used variable Report an error

  “The most used variable is "didomiVendorsEnabled", which holds the list of all vendors with user consent.”

• Gtm integration activation Report an error

  “Go to Consent notices (1) and click to edit your notice. Go to step 2. Customization (2) and the Integrations tab (3). Make sure you are in the Tag Managers section (4). Scroll down to select the Google Tag Manager integration.”

• Gtm datalayer name config Report an error

  “In the Data Layer Name field, write the name of your data layer. The standard name "dataLayer" is used by default.”

• Gtm didomiconfig snippet Report an error

  “If you didn't use the Console to create your consent notice, add this in the object didomiConfig: tagManager: { provider: 'gtm' }”

• Gtm trigger per vendor Report an error

  “You will need to create a trigger for each non-IAB vendor that you wish to block.”

• Gtm trigger condition Report an error

  “"Fire this trigger when an event occurs and all of these conditions are true": Didomi Vendors Enabled contains {ID vendor}”

• Gtm trigger groups and usage Report an error

  “👉If your existing trigger is a personalised trigger, you need to "create a group of triggers" so that the tag is activated when condition 1 (the existing one) and condition 2 (the one linked to consent) both meet.”

• Gtm or condition warning Report an error

  “👉If you add both the existing trigger linked to consent AND the existing trigger to the tag, the latter will be launched when the condition 1 OR 2 is valid. Do not use both at the same time, as this causes cookies to be dropped before/without consent (non-compliant).”

• Gtm spa limitation Report an error

  “Trigger groups are triggered once per page only. This can be problematic when using dynamic websites. In such case, you can use Didomi functions and events. Specifically for SPA, please refer to our dedicated GitHub page.”

• Gtm vendor id location Report an error

  “To find the vendor ID, go to step 1. Regulations, then the Regulations tab and Edit Vendors and Purposes under each regulation. You can select and copy the API ID .”

• Gtm container and new tag requirements Report an error

  “Remember to set up the tags for all your containers. From now on, each time you add a new tag for a non-IAB vendor requiring GDPR- compliant consent, you need to go through the setup and tick this new vendor in the list displayed in the console.”

• Gtm scope Report an error

  “You will now create triggers and connect these triggers to one of the Didomi events (we recommend using didomi-consent) and to the "Didomi Vendors Enabled" variable (created in the previous step).”

Scores citing this record

• The Agency Developer Prior blocking & script control
• The Data Protection Officer Prior blocking & script control
• The In-House Lawyer Prior blocking & script control
• The Publisher Marketing Lead Prior blocking & script control
• The Skeptic Prior blocking & script control
• The WordPress Webmaster Prior blocking & script control