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
BedrockMission!

Learn More

View all

Sign in to view all badges

Query Parameter Override for Analytics and Data Protection

Avatar

Avatar
Boost 3
Level 1
kevina31517033
Level 1

Likes

3 likes

Total Posts

2 posts

Correct Reply

0 solutions
Top badges earned
Boost 3
Boost 1
View profile

Avatar
Boost 3
Level 1
kevina31517033
Level 1

Likes

3 likes

Total Posts

2 posts

Correct Reply

0 solutions
Top badges earned
Boost 3
Boost 1
View profile
kevina31517033
Level 1

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

Avatar

Avatar
Contributor
Level 8
Antti_Ko
Level 8

Likes

270 likes

Total Posts

151 posts

Correct Reply

1 solution
Top badges earned
Contributor
Validate 10
Validate 1
Shape 25
Shape 1
View profile

Avatar
Contributor
Level 8
Antti_Ko
Level 8

Likes

270 likes

Total Posts

151 posts

Correct Reply

1 solution
Top badges earned
Contributor
Validate 10
Validate 1
Shape 25
Shape 1
View profile
Antti_Ko
Level 8

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
Validate 1
Level 1
bjoernkoth
Level 1

Likes

2 likes

Total Posts

18 posts

Correct Reply

0 solutions
Top badges earned
Validate 1
Boost 1
View profile

Avatar
Validate 1
Level 1
bjoernkoth
Level 1

Likes

2 likes

Total Posts

18 posts

Correct Reply

0 solutions
Top badges earned
Validate 1
Boost 1
View profile
bjoernkoth
Level 1

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
Validate 1000
Community Manager
jantzen_belliston-Adobe
Community Manager

Likes

337 likes

Total Posts

2,286 posts

Correct Reply

815 solutions
Top badges earned
Validate 1000
Springboard
Validate 500
Validate 250
Validate 100
View profile

Avatar
Validate 1000
Community Manager
jantzen_belliston-Adobe
Community Manager

Likes

337 likes

Total Posts

2,286 posts

Correct Reply

815 solutions
Top badges earned
Validate 1000
Springboard
Validate 500
Validate 250
Validate 100
View profile
jantzen_belliston-Adobe
Community Manager

27-10-2020

 
Status changed to: Archived