Tealium Learning Center

steve_crawford · ‎11-21-2017

Ocassionally we'll use the Web Companion to load our dev utag.js file and test it in production. Historically it's worked, although we had to update the hostname in the utag_env_<account>_<profile> cookie from our prod hostname to our dev hostname. In a new profile we recently published, that's not working anymore. It looks like utag.js expected the cookie path to contain Tealiums CDN. If it doesn't, the value of the cookie is ignored. Can we get this functionality back?

steve_crawford · ‎04-28-2015

We've been trying to come up with ways to implement automated testing for our tags -- specifically those made with utag.view calls. Utag.view seems to accept a callback function, but it doesn't return any result about the status of the tag. I was hoping if there would be any way to leverage this to verify that a tag has fired. Are there any plans for enhancements to this function? Alternatively, does anyone have any tips/tricks for testing their tags on an automated basis?

steve_crawford · ‎02-10-2015

Will do. Quick question... Is there anyway to control the order of tag specific extensions? i.e. Always have extension a fire before extension b, where both a and b are scoped to the same tag.

steve_crawford · ‎02-10-2015

That is good to know. I was curious which order they would be applied in. But in my case the extension isn't firing at all. I put a debug point at the start of my code in the extension to verify.

steve_crawford · ‎02-10-2015

It runs - but only for tags that do not have another extension scoped.

steve_crawford · ‎02-10-2015

I have a tag which has a scoped extension that sets a few values. I also have an extension which is scoped to all tags that I would like to run, but it doesn't appear to do so. Any tags without a scoped extension run without issue. Is this expected behavior?

steve_crawford · ‎12-17-2014

I needed this functionality again, so I dove in and found that the cookie the companion sets to tell the loader which version to load is actually a path to the utag.js. So you can set the environment like this (replacing the account and profile in the cookie name): document.cookie="utag_env_{{account}}_{{profile}}=//server-dev.example.com/tags/profile/dev/utag.js";

steve_crawford · ‎10-17-2014

Right you are about the try catch. Not sure how I missed that. So errors wouldn't cause any issue. In that case this isn't nearly as big of a deal :) The benefit to having separate functions would be that return false is a natural way to prevent the rest of the code in a block from executing. It's easy to write around and not use return false, but having that extra layer of protection may help save a few careless mistakes.

steve_crawford · ‎10-17-2014

I understand that. For DOM ready extensions, however, since they aren't really scoped to the tag but to the DOM, I feel like it should only affect what's inside that extension.

steve_crawford · ‎10-17-2014

This isn't so much of a question as it is an observation, work around, and suggestion. Let's say I have two extensions. Extension A: A contains a condition which returns false. Extension B: This extension isn't executing at all. Extension B is error free and properly scoped, so why isn't it executing?! The answer is because A & B are really in the same function, so returning false exists from the function, before B is ever executed. You could argue, correctly, that I shouldn't return false from the extension. And I rewrote my code so that I didn't. But it still seems like extensions should be a little more isolated. Extension B should run regardless of what happens in Extension A - be it return false or a JavaScript error. So I guess my suggestion would be to do just that. Find a way to isolate the extensions from one another. Has anyone seen anything similar or have any other feedback.

steve_crawford · ‎09-24-2014

It seems like the target selection for the web companion only respects the path of the deployment location, not the hostname. We have our publishing url's set up for dev & qa to go to server-dev.example.com/tags/profile/dev/, while prod goes to server.example.com/tags/profile/prod/. When I change the target environment from prod to dev -- using the web companion -- the version of utag.js requested is server.example.com/tags/profile/dev instead of server-dev.example.com/tags/profile/dev.

steve_crawford · ‎08-25-2014

Hi, My colleague and I are having an interesting error when publishing. When we go to download distro.zip (We self host our tag code), the code returned is actually the old code from the previous version. If we wait (sometimes up to 30 minutes), and download again, then we will get the correct version. This isn't a browser caching issue, as we've opened up the actual JavaScript to verify it is the old version. Has anyone run into this. Any solutions?

steve_crawford · ‎03-17-2014

Okay. Thanks Craig.

steve_crawford · ‎03-17-2014

Yes, we will be self hosting Tealium. By large custom tags I'm referring to a tag we are creating which points to our web beacon (i.e. It's not a SiteCatalyst or GA tag). If we send all of the data as query strings, I think it could easily reach the 2083 character limit for the URL. By using POST, we could transmit those query strings instead as header values. So even if we had 2083+ characters of name/value pairs, the limit would not affect us.

steve_crawford · ‎03-17-2014

Thanks for the response Craig, Our use case is that we are wanting to make sure that we do not reach the 2083 character limit in IE with GET requests. We will have some pretty large custom tags which could come close to that limit. We are actually going to be hosting that javascript files on our server. We are using Tealium to generate and manage the scripts for us. So I'm not sure if we will still run into any issues with cross site scripting. -Steve

steve_crawford · ‎03-17-2014

Can the Tealium Generic Tag use HTTP POST instead of GET? If not is there any way to create a custom POST based tag?

Date Registered	‎09-22-2015 07:28 PM
Date Last Visited	‎06-04-2020 09:40 AM
Total Messages Posted	17
Total Kudos Received	1

Tealium Learning Center

Overriding Environment on Self Hosted Profiles.

Automated Testing w/ utag.Views

Will do. Quick question... Is there anyway to cont...

That is good to know. I was curious which order th...

It runs - but only for tags that do not have anoth...

Tag with Scoped & All Tags Extension

I needed this functionality again, so I dove in an...

Right you are about the try catch. Not sure how I ...

I understand that. For DOM ready extensions, howev...

DOM Ready JavaScript Extensions & Isolation

Found bug with target environment selection in Web...

Publish Delay

Okay. Thanks Craig.

Yes, we will be self hosting Tealium. By large cus...

Thanks for the response Craig, Our use case is tha...

Can the Tealium Generic Tag use HTTP POST instead ...

Products

Company