Expand my Community achievements bar.

Announcement: Calling all learners and mentors! Applications are now open for the Adobe Analytics 2024 Mentorship Program! Come learn from the best to prepare for an official certification in Adobe Analytics.
SOLVED

Prefetching Online Ad & Email Links Inflating Website Visits - Adobe Analytics

Avatar

Level 1

The Problem

When comparing our digital advertising metrics from the ad agency adserver against our Adobe Analytics campaign reports – Adobe Analytics is significantly higher.  Ad clicks should be in line with visits within a reasonable degree – and trend similarly.  They are not even close in our comparisons - with Adobe out pacing Ad metrics by a wide margin.  In investigating possible technical reasons for this difference we uncovered Online Ad & Email systems “Prefetch” actions a possible culprit.  If these systems are generating a prefetch site visit in Adobe Analytics without the Adserver recording a click – that could be an issue for Adobe Analytics and all website trackers.  It’s similar to a bot without any other site engagement.  It would greatly inflate visits and bounce rates with the artificial visit.

 

Has anyone seen site prefetching as an issue or solutioned a way to mitigate the problem?

 

 

Prefetching is when content is downloaded in the background, this is based on the assumption that the content will likely be requested, enabling the content to load instantly if and when the user requests it. The content is downloaded and cached for anticipated future use without the user making an explicit request for it.

 

https://businesshelp.snapchat.com/s/article/mobile-optimization-playbook?language=en_US

 

https://www.mailmodo.com/guides/gmail-prefetching/#what-are-the-impacts-of-gmail-prefetching

1 Accepted Solution

Avatar

Correct answer by
Community Advisor

Just to clarify.. are you embedding Non-JS Adobe Tracking pixels on your emails? This could cause multiple concerns within your suite...

 

Gmail and AMPP prefetching images within emails could indeed be over counting...

 

First, without JS there is no user finger-printing, meaning that every time the user opens an email they would likely be treated like a new visitor and visit... (made worse by pre-fetching which again would count as a visit/visitor) and also, because this isn't using ECID service, any links that they open from those emails would be treated like a new user/visit once they reach your site.

 

The thing is, you can't use JS on emails.. most email readers will outright block JS because it used to be a common way to distribute malware and viruses to unsuspecting users.... 

 

What you could attempt to do, depending on your system.. is track your email opens (via non-JS tracking) into its own suite, so as to not inflate your main suite data; and on top of that, if the technology you are using to build and send your emails can use scripts (like Python) as part of the email build that could apply a unique user id (not ECID) into the tracking call so that at least the user (if not the visit) is at least identified consistently (maybe using the aid or vid params (https://experienceleague.adobe.com/docs/analytics/implementation/validate/query-parameters.html?lang...).

 

That is if you need Adobe to be embedded in your emails... this will take some testing to see what works...

 

I suggest you set up an isolated testing suite that you very carefully document all the expected hits from a few devices and attempts and correlate the data that makes it to the suite to see if it matches your expected values...

 

 

View solution in original post

1 Reply

Avatar

Correct answer by
Community Advisor

Just to clarify.. are you embedding Non-JS Adobe Tracking pixels on your emails? This could cause multiple concerns within your suite...

 

Gmail and AMPP prefetching images within emails could indeed be over counting...

 

First, without JS there is no user finger-printing, meaning that every time the user opens an email they would likely be treated like a new visitor and visit... (made worse by pre-fetching which again would count as a visit/visitor) and also, because this isn't using ECID service, any links that they open from those emails would be treated like a new user/visit once they reach your site.

 

The thing is, you can't use JS on emails.. most email readers will outright block JS because it used to be a common way to distribute malware and viruses to unsuspecting users.... 

 

What you could attempt to do, depending on your system.. is track your email opens (via non-JS tracking) into its own suite, so as to not inflate your main suite data; and on top of that, if the technology you are using to build and send your emails can use scripts (like Python) as part of the email build that could apply a unique user id (not ECID) into the tracking call so that at least the user (if not the visit) is at least identified consistently (maybe using the aid or vid params (https://experienceleague.adobe.com/docs/analytics/implementation/validate/query-parameters.html?lang...).

 

That is if you need Adobe to be embedded in your emails... this will take some testing to see what works...

 

I suggest you set up an isolated testing suite that you very carefully document all the expected hits from a few devices and attempts and correlate the data that makes it to the suite to see if it matches your expected values...