Tealium Learning Center

Hi @BretCamble2, Thank you very much for that explanation of your experiences! That was exactly what I was hoping to get from this post. As you might already have read here, our solution ended up being using the "beta non-public" Target approach in Tealium iQ. This consists of one extension and one tag, and then the tag order Visitor API - Target - Analytics. We tried this out, because it seemed to cumbersome to do all, or some, of it manually from outside Tealium iQ. And your experiences tell me, that we took the right decision. For us this is running nicely, and since it's also using Adobe Target new asynchronous way of working, it isn't stalling stuff, as we were very worried about, when looking at the old-school syncronous approach. Once again, thank you for sharing! Best regards Peter Meyer ... View more

Hi @adrian_browning Nice! At Nordea, we are very much looking forward to that :-) Please let me know, when that happens. Best regards Peter ... View more

Hi @leejon, We are actually using the beta version on several production site now, and haven't experienced any problems. But we are looking forward to the release anyways, to get it sorted properly, and have manual fixed to the code "included" automatically. Best regards, Peter Meyer ... View more

Ah... Sorry, now I know what's wrong ; -) Because I had some trouble with the code added by the extension it self, your colleague Kevin Faurholt fixed it for me, but did this directly in the template. Afterwards he of course forwarded information about this, to the persons working on the "real" tag and extension. Sorry to bother you with this. I will take this in account, and test properly ;-) Best regards, Peter ... View more

Hi @adrian_browning, I just tested the following, on an iQ profile with the new Adobe Target approach setup, using both tag and extension. Disable tag, and publish Code still present in utag.sync.js Disable extension, which adds code to utag.sync.js Code still present in utag.sync.js Shouldn't at least step two remove the code from utag.sync.js? I am testing in DEV only, but the site I am testing on, is then also hardcoded to use DEV. Could that be a problem in this regards? Generally, I was trying to test, that if I disabled as mentioned above, that the code would be removed from utag.sync.js as well, so I was certain it was completely gone from the setup. Sorry to be double-spammy, but I also wrote Customer Support to ask about this. Best regards, Peter ... View more

Hi @adrian_browning,   Kevin Faurholdt have dound the cause of the error, and writes to me, that he will get the fix in the upcoming version of the tag. He also "hardcoded" the change into the tag, in the profile I am testing it in.   Best regards, Peter   ... View more

Hi both, I setup this new Adobe Target approach on one of our test sites, which I won't share the URL of here.   It seems to runs as supposed to, except one thing: On the one page I added a test, I am experiencing flicker. More precisely, I can see the original content switch to the changes made using a Target A/B test. I might have done something incorrectly, and have an open support case with Nathan Fleming regarding this. Just so you, @adrian_browning, at least know it :-) Best regards, Peter ... View more

Hi @adrian_browning,   But if I then delete the extension and/or the Adobe Target tag, will the code in utag.sync.js also be removed automatically, together with the code I guess will be removed from utag.js? And if I only disable the extension and/or the Adobe Target tag, can I then be sure, that none of the code added together with the tag and extension will run?   Best regards, Peter   ... View more

Hi @adrian_browning,   Thanks! I guess I have been miss-reading the flow illustration :-/ I actually had a very thorough talk, a couple of hours, with Kevin Faurholt about the upcoming new Target tag. And your name was mentioned often in that conversation ;-) I want to go for the new approach, but the label "beta", is holding that back a bit, in regards to which tags and extensions I will be allowed to use.   A bigger issue is, that we are a bit afraid of the utag.sync.js file being synchronous, as it should, since that makes us more vulnerable to non-answering scripts, blocking other stuff from loading and/or displaying. So what we best do about that, we will have to find the solution for. This I of course also discussed with Kevin.   It is now clearer to me, that if we don't use the new approach, I would have big work ahead, if I want to do something regarding the Visitor ID myself. This part would be nice, to not have to do myself ;-) Best regards Peter   ... View more

Hi @zhaque,   I haven't solved it yet, but was wondering if it shouldn't just work as is.   I have been looking at this document: https://marketing.adobe.com/resources/help/en_US/target/target.pdf   On page 69 it mentions: On to me, it seems like the Adobe Target process flow handles visitor identification.   I will have to test further, since I haven't tested this thoroughly.   But fellow community members, please share your input and experiences :-) It isn't very easy to find the information, so any feedback would be much appreciated!   Best regards, Peter   ... View more

Hi @adrian_browning, Thank you :-) I will write a support request to get the beta tag access.   Best regards, Peter ... View more

Hi @BradHenderson,   If you want to use Fiddler for this purpose, you can use the FiddlerScript I am including here. The point of this particular script, is to make it a bit easier for non-coders, to paste the script and modify as little as possible to make it work. You will therefore see, that the Tealium iQ account is supposed be "hardcoded", since it would wouldn't need to be changed often, compared to what you really need to change, e.g. hostname, existing - and changed profile and environment. Using a proxy tool like Fiddler, will also activate the prod -> dev environment change for all browsers and programs on your computer, not just one single browser. I generally like to use tools like Fiddler or Charles because of this, compared to the use of different extensions in different browsers.   Insert, and modify, the following FiddlerScript in the "OnBeforeResponse" section of the menu item "Rules / Customize Rules ...".   //--------------------------------------------------------------- // START - Tealium iQ - Change Environment for specific site //--------------------------------------------------------------- var tiqChange_Hostname = "www.mydomain.com"; var tiqChange_EnvironmentExisting = "default/prod"; var tiqChange_EnvironmentNew = "sandbox/dev"; if (oSession.HostnameIs(tiqChange_Hostname) && oSession.oResponse.headers.ExistsAndContains("Content-Type","text/html")){ oSession["ui-backcolor"] = "orange"; oSession["ui-color"] = "black"; oSession["ui-bold"] = "true"; oSession.utilDecodeResponse(); oSession.utilReplaceInResponse("//tags.tiqcdn.com/utag/MYACCOUNT/" + tiqChange_EnvironmentExisting + "/utag.js", "//tags.tiqcdn.com/utag/MYACCOUNT/" + tiqChange_EnvironmentNew + "/utag.js"); } //--------------------------------------------------------------- // END - Tealium iQ - Change Environment for specific site //--------------------------------------------------------------- In the code, change the two words "MYACCOUNT" to the name of your own the Tealium iQ account, and save the code snippet for later use.     After that, your only supposed to change the three top-most variables to their relevant values.   tiqChange_Hostname = The entire hostname you want to change Tealium iQ environment for tiqChange_EnvironmentExisting = The Tealium iQ profile and environment you want to change from tiqChange_EnvironmentNew =  The Tealium iQ profile and environment you want to change to The two later variables are to be defined in the format: [PROFILE]/[ENVIRONMENT]. This allows you to also change to another profile, for instance a "sandbox" profile created for test purposes only.   Best regards, Peter   ... View more