- TLC Home Home
- Discussions Discussions
- Documentation Documentation
- Knowledge Base Knowledge Base
- Education Education
- Blog Blog
- Support Desk Support Desk
07-10-2017 01:37 AM
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
07-10-2017 07:43 PM
07-10-2017 11:24 PM
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.
07-11-2017 09:42 AM
07-11-2017 09:47 AM
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?
07-11-2017 11:37 PM
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.
07-17-2017 02:35 PM
@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?
07-18-2017 04:47 AM
@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.
Copyright All Rights Reserved © 2008-2023