I think you can close this discussion. It's Adobe Analytics Debugger extension that's falsely throwing duplicate calls. When I see the duplicate call in Adobe Analytics Debugger, Fiddler is only showing a single call, and the pages report is reporting a single page view. As of now, I only have a single page name rule in DTM.
I would expect a single Analytics beacon from your page when DTM is deployed (assuming no other rules are firing other beacons).
When you see multiple beacons, are any rules firing? You can see which rules fire via the console with the DTM debugger being set to debug. I'm trying to narrow down where the duplicate beacon is being generated. If no rules are firing, we know it's coming from a tool. If rules are firing, we need to check those rules.
I removed the DTM header code, and got _satellite is not defined. Then, I removed the pageBottom code and got nothing. Our implementation is custom. I did verify that when I'm seeing duplicates in calls, I'm only seeing one page view in Adobe Analytics.
I guess the mystery still remains; why is the call still being made with pageBottom code?
If you are questioning the debugger, you can always just use the network tab in your browser's dev tools. I'd suggest filtering the requests for "b/ss/".
If you remove the DTM header code do you still see a beacon? If so, there is something outside of DTM causing the other beacon. If you remove the header and the beacons stop, we may need to dive deeper into your DTM implementation. Is you Analytics tool library managed by Adobe or is it custom?
We were using an old H.26 s_code, but it has been completely removed. I verified that there is only one pageBottom call in the code after everything has loaded. The pageBottom code is statically loaded.
So, here's the weird thing, it doesn't always make 2 calls when I reload the page; just sometimes. I'm starting to think that the Adobe Analytics Debugger Chrome extension may be messing with me.
Update: I just verified with Fiddler that only one call is being made when I see two calls on Adobe Analytics Debugger Chrome extension.
Do you have existing s_code or AppMeasurement code that remains on the site after you moved to DTM? Also, can you verify that there isn't two pageBottom calls in the code after everything has been loaded? Is the page bottom code being dynamically injected to the page or statically loaded?
Unfortunately I cannot. It's in a dev environment and can't deploy it until it's working properly. I'm using Chrome DevTools with Adobe Analytics Debugger to test my implementation. Working with Fiddler to verify multiple calls.