Google Tag Manager

introduction google tag manager (gtm) is a tag management system that lets you add and update website tags—like tracking pixels and analytics scripts—without changing the site’s code it simplifies tracking setup and improves marketing agility getting started this is a device mode destination you will need the relevant container id of your google tag manager workspace to connect this destination you can find this information by following the steps below log into your google tag manager workspace homepage navigate to the upper right hand corner of the page and locate the container id connecting to the google tag manager cdp destination log into the chord data platform navigate to the cdp click the "add" button next to destinations select google tag manager from the destination catalog enter in the destination name, the container id, and data layer name destination name the arbitrary name you give to the destination container id the gtm container id is found in your google tag manager account how to find it go to https //tagmanager google com select your account and container the container id is displayed at the top of the workspace it looks like gtm xxxxxxx data layer name the datalayername field specifies the name of the javascript array that gtm uses to receive data on the page how to find it go to https //tagmanager google com navigate to the variables settings in the left hand pane look for any configured data layer variables if there isn't an explicit variable configured, this value will default to datalayer click "create" to connect chord events relevant for destination not all chord tracking events are used downstream in your configured destinations the most relevant and important events in the chord tracking plan are mapped within the cdp destination, relayed and then ingested in the destination given this, google tag manager does not support any explicit event filtering and will accept all chord tracking events before connecting destinations in the chord cdp, please verify with all destination owners that all non chord cdp configured destinations are disabled running external destinations alongside configured chord cdp destinations can result in duplicate events downstream