SOLVED
DTM Page Load Rule Firing Twice?
Hi there,
I'm trying to troubleshoot why I'm seeing my page load rules and SiteCatalyst code is appearing twice in my debugger tool. I've attached a screenshot that shows the SiteCatalyst account showing up twice and that shows "event10, event11, event10, event11" appearing to fire twice. The site I'm working on is: https://www.tysonfoods.com/
Is anyone out there able to help me troubleshoot this?
Thanks in advance!
1 Accepted Solution
Correct answer by
Here's what I'm seeing:
I'm only seeing one GA tag and one AA tag fire.
The reason we are seeing different things has to do with timing:
Normal loading:
- DTM JS library is loaded
- Page body loads
- if _satellite.pageBottom is in the <body>, it fires the AA tag.
3b. if _satellite.pageBottom is not in the <body>, then DTM automatically calls pageBottom at DOM Ready.
However, with the defer html attribute:
- DTM JS library is deferred
- Page body begins to load
- DTM JS library beings to load
- If DOM Ready occurs before the _satellite.pageBottom in the body fires, DTM calls it automatically, and fires the AA tag.
- Then the _satellite.pageBottom in the body is called, firing a second AA tag.
I also noticed some timeout logic around the _satellite.pageBottom call. This isn't necessary instead, consider:
if(typeof _satellite == 'object') _satellite.pageBottom()
That should be the maximum amount of customization to that method necessary, since DTM will fire pageBottom automatically if it the _satellite object doesn't exist when that code is called.
Hope that helps!
Hi there,
I just checked https://www.tysonfoods.com/who-we-are and am not seeing this issue, however, I may have the solution to the problem:
It looks like the satellite library is getting loaded with a defer html tag.
This is a very big no-no when it comes to DTM, as it highly affects the timing of the DTM JS loading - essentially making DTM unsupported. Per this document, HTML script defer Attribute , causes the JS file to not execute until the page has finished parsing. And this will very largely affect DTM's ability to serve tags properly.
I couldn't recommend that this defer attribute be remove more highly.
Correct answer by
Here's what I'm seeing:
I'm only seeing one GA tag and one AA tag fire.
The reason we are seeing different things has to do with timing:
Normal loading:
- DTM JS library is loaded
- Page body loads
- if _satellite.pageBottom is in the <body>, it fires the AA tag.
3b. if _satellite.pageBottom is not in the <body>, then DTM automatically calls pageBottom at DOM Ready.
However, with the defer html attribute:
- DTM JS library is deferred
- Page body begins to load
- DTM JS library beings to load
- If DOM Ready occurs before the _satellite.pageBottom in the body fires, DTM calls it automatically, and fires the AA tag.
- Then the _satellite.pageBottom in the body is called, firing a second AA tag.
I also noticed some timeout logic around the _satellite.pageBottom call. This isn't necessary instead, consider:
if(typeof _satellite == 'object') _satellite.pageBottom()
That should be the maximum amount of customization to that method necessary, since DTM will fire pageBottom automatically if it the _satellite object doesn't exist when that code is called.
Hope that helps!
