Tealium Learning Center

As of yet, no response. But I'm still very confused as to WHERE s.pageName is being set. Pre-Tealium, there was the s_code and it was very customized before I showed up and it was clearly in there. However, now, with Tealium, it's not present in the template at all. There are a few places that reference pageName but none that actually set it.   I was thinking it wasn't set until Adobe got its hands on it, but now I think that it's set while still in Tealium, but I can't find where. ... View more

Nope. Nothing's worked so far. I think this is an Adobe issue. I've contacted them. ... View more

It's auto-mapping.   But I'm in the middle of trying something else right now. I'll keep you posted!   Thanks! ... View more

Ok, so I found that the version is, in fact what I posted above. Which is lower than 4.4.   I also notice that it seems that the lowercasing the URL isn't working. I say that because, the way we're using s.pageName in Adobe (Pages report) is to let it be the default which, if I'm reading it right, is the URL. However, despite this extension, it's still showing up mixed case in the report. This makes me suspect that the URL isn't actually getting lowercased.   My problem is also that I'm not sure which suite (Tealium or Adobe) is the one dropping the ball here so I'm trying to troubleshoot from both sides.   So far you guys have been much more responsive than Adobe, so that's why I'm asking more here. :)   Thoughts as to what might be happening? ... View more

@adrian_browning So, I tried it, and I thought it was working at first, but, as of this morning, it seems like it isn't actually taking and I was somehow seeing some false positives yesterday.    One thing I notice is that it says the Execution part only works post utag version 4.38. I'm not 100% sure which version we're on. When I go to the Versions tab, and click on "View utag.js" the top of the file says:   utag.loader ut4.0.201604201558   Does that mean this whole thing won't work for me? ... View more

@adrian_browning   Thanks! I'll give it a go. But, how is it that I have access to the query string in a preloader when I run the script to lowercase the entire query string, but I don't have access to the URL to lowercase that? ... View more

Thanks @adrian_browning! But why would I do it after load rules? Wouldn't I want that to be a preloader, like the lowercasing of the query string? And I'm assuming that the url in the first field is the DOM url, not a separate UDO of the same name? ... View more

Thanks, @kathleen_jo. We are using that extension as well, but it only deals with the variable contents. ... View more

Out of curiosity, and I apologize if I'm straying too far from the topic, but is there a similar way of lowercasing the entire URL as well? ... View more

I found this since I'm trying to do the same thing. I want to capture query string parameters regardless of case. In other words, I don't want to have (like I currently do) two separate extensions to capture "Promo" and "promo", etc.   I clicked on the link above but got an error message saying I don't have sufficient permissions to view it. ... View more

Thanks! ... View more

I'm actually okay with that since it was a small extension. How do I discard all changes, @davidcreason?   Thanks! ... View more