- TLC Home Home
- Discussions Discussions
- Documentation Documentation
- Knowledge Base Knowledge Base
- Education Education
- Blog Blog
- Support Desk Support Desk
06-02-2016 09:19 AM
I've got a really odd one on my hands right now and I may not be seeing the obvious here.
Two different DoubleClick Floodlights have been implemented in a way that there is only a generic tag implementation and the required parameters (cat=, type=, src=) are being taken care of via Set data extensions
Lookup value in pathname
Destination: dc_type (UDO variable)
Match type = exact
Tag 1 Extension setup
path = /global/zh-cn
Output = xyz
This one works fine.
Tag 2 Extension setup
path = /zh-cn
Output = xyz
The latter doesn't seem to work.
Although another extension using the same logic but populating a different parameter works just fine for Tag 2.
Any ideas what could be the reason?
Solved! Go to Solution.
06-03-2016 03:04 AM
I have found the issue.
A friendly word of advice ladies and gents that always check if you have accidentally pasted in an extra space into the pathname lookup/condition.
Because I've set the match type to exact, that space prevented the extension to work.
I have found this by checking the DoubleClick tag's call and see what the conditions were for the extension in developer tools
06-03-2016 08:49 AM
LOL I usually find that I miss semicolons somewhere.
Great catch @brutalben and thank you for keeping up posted!
Copyright All Rights Reserved © 2008-2023