How does DTM send tracking to GA account? | Community
Skip to main content
cathyw49544988
cathyw49544988
Level 5
January 12, 2018
Solved

How does DTM send tracking to GA account?

  • January 12, 2018
  • 1 reply
  • 1977 views

I added the GUA tool as one of the installed tools. But I didn't do anything on the rule level yet. I thought we only have a empty container for GUA. All the rules won't send data to GA account. But actually we saw data from DTM. I am wandering in this case, what kind of data DTM is sending to GA? Any good document / video on how to setup GUA in DTM?

Thanks,

This post is no longer active and is closed to new replies. Need help? Start a new post to ask your question.
Best answer by jdonley

When you add UA on a Tool level, by default DTM outputs the UA library and page view tracking on every page load, even when no Page Load Rules (PLR) are in place.

If you do not want UA to load on certain pages, you can create a PLR with condition(s) to identify the pages (e.g. a URL path) and then within Google Universal Analytics tool section of the PLR, there is a checkbox labeled "Don't load Google Universal Analytics on these pages" that you can check.

So in other words, by default everything is whitelisted and you can create PLR(s) to blacklist pages.

If you want the reverse, where by default every page is blacklisted and you specify pages for it to trigger on (whitelist), then you must implement UA as a Javascript / Third Party Tag within a PLR instead of on a Tool level.

1 reply

J
jdonleyAccepted solution
Level 8
January 12, 2018

When you add UA on a Tool level, by default DTM outputs the UA library and page view tracking on every page load, even when no Page Load Rules (PLR) are in place.

If you do not want UA to load on certain pages, you can create a PLR with condition(s) to identify the pages (e.g. a URL path) and then within Google Universal Analytics tool section of the PLR, there is a checkbox labeled "Don't load Google Universal Analytics on these pages" that you can check.

So in other words, by default everything is whitelisted and you can create PLR(s) to blacklist pages.

If you want the reverse, where by default every page is blacklisted and you specify pages for it to trigger on (whitelist), then you must implement UA as a Javascript / Third Party Tag within a PLR instead of on a Tool level.

Terms & ConditionsAccessibility statement

Loading footer...