Strange (possibility encoded) values in the tracking code report

[brianb60338381]

Hi,

We are seeing a too high to be ignored number of tracking codes in our reports. 

They look like this

cgc_fzbvy_A6G5EVadvefagEbvffeDbaavezbgvba_bayvafufyc

cgc_fzbvy_DbclBaCvyyEfdhffg_ivfjbhecvyyfkcybvafeufef

cgc_fzbvy_DhfgbzfeZvfffeBccbvagzfagEfzvaefe_yvifdubg

cgc_fzbvy_BeefeDbaavezbgvba_ivfjbhecvyyfkcybvafeufef

They follow the same format and structure (pattern of characters groups) as our correct tracking codes send via an internal email server. But appear to have a very simple character substitution applied b=a, t=g, e=f, m=z etc

All instances are from desktops and versions of chrome browsers. 

Does anybody know of a Chrome extension which can encode querystring values in this way? or any other possible  cause of this?

[David_Jerome]

This is interesting. I believe that Ghostery does something like this.

[David_Jerome]

This is interesting. I believe that Ghostery does something like this. Are you using standard campaign query strings CID=?

[brianb60338381]

Yes standard cid= query sting implementation.

[David_Jerome]

You might be able to trick it in a couple of ways - one change CID to some random. I suspect it has a list of known campaign query strings. The other thing - which might only work for the short term - would be to have logic in your tag manager to change b=a etc if the query string starts with "cgc". Not great for performance though and could stop working at any time if if the logic is changed.

[brianb60338381]

I have just looked the tracking code reports for one of our sister brands (so different implementation and site) and am seeing similar tracking codes there as well. which is good news for me. I am sure you will see the same in your reports. I will keep looking to find the extension causing it. Thanks for the help.

[jantzen_b · Accepted solution]

Answer provided in the comments to the original post.