Expand my Community achievements bar.

Join us for the Adobe Journey Optimizer Community Q&A Coffee Break on 28th February at 8 am PT with Ariel Sultan, Daniel Wright, Josee Haeley and Rohit Basuri.
SOLVED

Avoid tracking for saved web pages or bookmarked pages

Avatar

Community Advisor

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 

 

Topics

Topics help categorize Community content and increase your ability to discover relevant content.

1 Accepted Solution

Avatar

Correct answer by
Level 8

@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.

View solution in original post

2 Replies

Avatar

Correct answer by
Level 8

@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.

Avatar

Community Advisor
Thank you brian @Brian_Johnson_. yes I'm using Launch tag manager and I think 3rd options seems better