Yep, the difference was much bigger than I assumed. I know, every time there is a detour, there is also new thing to pay attention.ĥ8,000 hits with default tracking and with our “local storage” method we got 69,000 hits. However, if you look pages where this hit has been populated then you might get some strange pages that are not including the link itself. This way we get all the hits counted! Note: Information is saved for long period of times and if user terminates browser after the link hit and page is not loaded then this hit is populated next time user comes to the site, so we surely will get the hit if user returns. This way hit isn’t terminated when browser is moved to another page, because hit is populated after page Y is loaded. What is causing this link tracking problem? Maybe slow internet connection or is it a browser issue? We wanted to test this and that’s why we hardcoded two different tracking methods for custom link tracking.ġ) Default link tracking by Adobe, populated asap when link is clicked.Ģ) Default link tracking by Adobe, but hit information is saved to browser’s local storage and populated on the next page view. I know, data is never 100% accurate, we all have to deal with it. I’m sure you get the idea? Of course if user clicks on a link and then immediately closes browser or clicks back button etc then you might get link click but that wouldn’t be counted on the segment because page Y never loaded.
ADOBE ANALYTICS CLICK MAP HOW TO
How to investigate the data loss and/or get a detour for this problem? You can make a segment where visits goes from page X to page Y and that way you can compare the results with that segment using page views vs link clicks with default link tracking. I assumed this data loss would be very minimum and also I wasn’t really concerned because all of these hits were “nice to know” metrics. I knew already that there have been some discussions around this topic for many years that sometimes the analytics hit doesn’t have enough time to populate because browser moves user to another page on the same tab. Originally this idea came from coder who wasn’t too happy what he saw when debugging some custom link tracking. We wanted to investigate is every single hit sent to Adobe’s server when visitors click on a link that forwards to another page on the same browser tab. First of all, I know you hardcore users already know this old issue, but there might be new Analysts and since we did a little experiment, I want to share the results by writing a small blog post about this.
0 kommentar(er)
