Query Parameter Override for Analytics and Data Protection

Avatar

Avatar

kevina31517033

Avatar

kevina31517033

kevina31517033

25-01-2017

It would be nice if there were configuration variables in the library, something like

 

s.queryParamOverrides = firstName, first_name, fname, address ....

s.queryParamOverrideValue = foo

 

wherein a list of query parameters can be overwritten with the value contained in s.queryParamOverriveValue.

 

Many of us face data protection issues and adding the option to strip or override these values would be a great help in helping/simplifying things.

 

Cheers

 

Kevin

3 Comments (3 New)
3 Comments

Avatar

Avatar

Antti_Ko

Avatar

Antti_Ko

Antti_Ko

03-03-2017

Like the idea.

 

Nowadays, we have to do own javascript coding for this one. Something like this:

s.eVar1 = window.location.href;

s.eVar1 = s.eVar1.replace(/(\?|&)(firstName=)[^&]*(&|$)/i,"$1$2$3");

Would be of course easier if there would be default function just for this.

Avatar

Avatar

bjoernkoth

Avatar

bjoernkoth

bjoernkoth

06-03-2017

Absolutely right! We do have a list of 20+ potentially harmful GET query params that are transmitted both in the pageURL and referrer. Well aware that using GET params is actually not encouraged these days and it may have some other implications as well. But we are in a huge company and many of the systems we track (using a tag manager) cannot easily switch to POST instead.

 

Would be nice to either obfuscate the values as you suggested or just remove them from any automatically gathered information.

 

Cheers,

Bjoern

Avatar

Avatar

jantzen_belliston-Adobe

Community Manager

Total Posts

1.9K

Likes

312

Correct Answer

570

Avatar

jantzen_belliston-Adobe

Community Manager

Total Posts

1.9K

Likes

312

Correct Answer

570
jantzen_belliston-Adobe
Community Manager

27-10-2020

 
Status changed to: Archived