How to track "Do not track" setting

[sebastian_koeni]

We would like to apply to the users wish not to be tracked. Before doing so, we would like to know to how many users this applies. Is the information which the new extension uses available as a variable, which I can build rules on?

[jasmine_liu]

Hi Sebastian, Do Not Track is turned on by the end user. The number of how many people who has turned it on is probably not tracked anywhere. You can configure an out of the box solution to disable ALL tags and ALL Tealium code if a user has Do Not Track on. This can be done by adding a code snippet in a javascript extension scoped to pre-loader. You can also selectively disable tags if a user has Do Not Track on, but this is a bit different than the out of the box solution. Please reach out to your account manager for detailed instructions and code snippets on how to implement both solutions. They can also address any further questions you might have. I hope this helps. -Jasmine

[holger_krause]

Hello Jasmine, with the new Do not track extension I would have expected it is very easy to build loadrules on the do_not_track data source? The comment in the extension gives this impression. Sebastians's questions is interesting though - if the extension reads the client side setting of do not track and pushes it in the utag data layer - what would be the smartest way to count the number of users with "do not track" set? Maybe sending a dimension or custom var to Google Analytics? Cheers Holger

[craig_rouse]

Hi Holger, If you use the DNT extension, you can easily create the do_not_track data source in your Data Layer tab in Tealium IQ and map this to your preferred analytics tool. Make sure the data source is defined as "UDO Variable" type and ensure that the name is "do_not_track". Since the DNT extension was only released last night, I expect there will be a follow-up community post from the education team which will fully explain the different use cases and how you can make the most of the extension. Hope this helps! Craig.

[Clint]

The post is already available here: https://community.tealiumiq.com/posts/785004. It discusses how to implement the extension but does not detail pulling internal data out of the extension for reporting.