Your achievements

Level 1

0% to

Level 2

Tip /
Sign in

Sign in to Community

to gain points, level up, and earn exciting badges like the new
Bedrock Mission!

Learn more

View all

Sign in to view all badges

Coffee Break: Join us on Wednesday, April 5th at 10am PT to chat with Ben Gaines, Director of Product Management for Adobe Analytics. Ben will be online to answer your Analytics and Adobe Summit questions.

Query Parameter Override for Analytics and Data Protection


Level 1


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.







Level 8


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.


Level 2


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.