Query Parameter Override for Analytics and Data Protection | Community
Skip to main content
K
Kevin8152
New Participant
January 25, 2017
New

Query Parameter Override for Analytics and Data Protection

  • January 25, 2017
  • 4 replies
  • 2952 views

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

    4 replies

    L
    lakshays
    Community Manager
    October 5, 2022
    No text available
    jantzen_b
    jantzen_b
    Employee
    October 27, 2020
    No text available
    B
    bkoth
    New Participant
    March 7, 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

    A
    Antti_Ko
    New Participant
    March 4, 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.

    Terms & ConditionsAccessibility statement

    Loading footer...