Chance Query Parameter Value with Load Rule

[feb]

hey guys,

first of all excuse me if I have done something wrong becauce i post the first time something in this forum.

Now my Problem.

I set up a Converto Pixel with a Tealium Generic Tag (see Screenshot)

And somehow something strange happens.

If i publish this tag with the Load Rule "All Pages". 
The Query String Value for "a" is 182.

If i publish this tah with any other Load Rule the Query String Value for "a" is 184.

how is that possible?

I hope you can help me. Thanks in advance  & sorry for any vagueness 

Ferhat

[Paul]

@feb maybe you have method some where that is incrementing it? That would be my guess.

[feb]

Hey @PaulWhat exactly do you mean?

I dont specify anything in the mapping.

I have just put this Query String in the tag "n=3365&g=20&a=182&s=1&l=1&t=i&f=1"

Every Query String Parameter is the same except the a Parameter.

Now i have build for every Query String Parameter a Variable and set ther Data Values in a Extension.

But this is not the best way because the Query String is normaly static.

[Paul]

@feb Ah ok. I thought there might be a method that you have scoped to that parameter to make it increment that way. I've got nothing else. Anyone else have any ideas?

[robert_sabec]

@feb

Ferhat

I was not able to re-create the bug you described!  

Is it possible you were reviewing a previously published version before the CDN updated with an old value?   incorrect environment with a = '184' value,   or possibly multiple versions of this pixel in that same profile? ( look for additional tags that load the same bh.gif pixel but with the 184 value?

Robert

[feb]

@robert_sabec

Hey Robert,

I am actually sure that I review the right version.

But even if not, i never specified the value 184.

It surprises me that the value is changes depending on whether a loading rule has been set or not.

I do not change the configuration and the mapping of the Tag just aktivate the load rule and then i have an other value.

Thanks,

Ferhat

[dave_milsom]

@feb Are you sure the pixel is not resulting in a redirect, with perhaps an updated value? Can you provide a screen shot of the network call?

[feb]

@dave_milsom I have found in the meantime a solution with the mapping.

I mapped each query parameter separately

I just tried to make it without the mapping, however, the problem no longer appeared.

I do not know why that happened then.

Nevertheless, thank you for your help.

Best,

Ferhat