Avoid tracking for saved web pages or bookmarked pages | Community
Skip to main content
Gokul_Agiwal
Community Advisor
Community Advisor
December 30, 2020
Solved

Avoid tracking for saved web pages or bookmarked pages

  • December 30, 2020
  • 1 reply
  • 1240 views

If someone saves a web page on their computer and accesses at a later date, all of the tagging will fire.

 

This includes URL which reflects the drive path of the user's computer. In a large number of cases we can see PII data in reports.

 

Do we have any resolution that prevents Adobe collecting URL in these cases 

 

Help is appreciated. 

 

Thanks,

 

@andrew_wathen_ @andrey_osadchuk @stewart_schilling 

 

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 Brian_Johnson_

@gokul_agiwal - There are probably a number of ways to address this...

  • Use a VISTA rule to drop any requests where the URL indicates it's a local file (file:) rather than a hosted web page (http:, https:). Note that there is a cost associated with this approach.
  • If you're using Launch, place conditions on your Analytics rule(s) that prevent the call(s) from firing if document.location.protocol is NOT "file:".
  • If adding conditions to rules is too much work (lots of rules!), or you're not using a tag manager, check the document.location.protocol value in s.doPlugins. If it is "file:", abort the call using s.abort.

1 reply

Brian_Johnson_
Brian_Johnson_Accepted solution
Level 8
December 30, 2020

@gokul_agiwal - There are probably a number of ways to address this...

  • Use a VISTA rule to drop any requests where the URL indicates it's a local file (file:) rather than a hosted web page (http:, https:). Note that there is a cost associated with this approach.
  • If you're using Launch, place conditions on your Analytics rule(s) that prevent the call(s) from firing if document.location.protocol is NOT "file:".
  • If adding conditions to rules is too much work (lots of rules!), or you're not using a tag manager, check the document.location.protocol value in s.doPlugins. If it is "file:", abort the call using s.abort.
Gokul_Agiwal
Community Advisor
Community Advisor
December 30, 2020
Thank you brian @brian_johnson_. yes I'm using Launch tag manager and I think 3rd options seems better