Tealium Learning Center

I looked at the documentation too, and even with the admin setting that would set manual params as primary, the real challenge with allowing both UTM and GCLID to pass on the same string would be that our doubleclick data, with this admin setting, would be knocked out entirely. Also, I don't want them to be exclusive and kick out if only a UTM or GCLID comes through. Something like this might work: if ((utmParam&&gclidParam = defined)&&(uaCode=ua-xxx-1)) {knock out gclidParam }elseif{ if ((utmParam&&gclidParam = defined)&&(uaCode=ua-xxx-2)) {knock out all utmParams } n'est pas? I just don't know where to apply that logic. I've contacted my account rep and we may have to have your team develop a solution for us. ... View more

It appears that Track Screen Views was turned on for my GUA tag --------------------------------- Also, I found out that I needed to CLEAR MY CACHE to see the other utags. ... View more

Not to be flippant, but I just need an solution... not vagueness.   My Problem Is:   I do not have a proper variable that the Google ecommerce plugin will like on my pages so...   My Proposed Solution Is:   1) Define a new DATA LAYER var called "OSP_Checkout_Step1" (this won't be included in the on-page UDO) - also what type should I use (UDO var (or) JavaScript var?).   2) Create a new 'SET DATA VALUES' extention using "OSP_Checkout_Step1" and transform it to "JS Code" using: ga('ec:setAction','checkout', {'step': 1})   3) Use a CONDITION based on dom.url (or some other UNIQUE ELEMENT to that 'step one' page) to load the extension.   ---------------------- Will this work? If not, why? Is there a better solution? ----------------------   PS, we also use Webtrends and I would like to do the same with this code:   <meta name="WT.si_n" content="OSP_Sponsorship;SponsorshipCheckoutFunnel" /> <meta name="WT.si_x" content="1;1" /> <meta name="WT.si_p" content="ChildSelection;ChildSelection" />   Normally this is supposed to be on page but I'm guessing I can probably define a data object called "WT.si_n" and pass along as text "OSP_Sponsorship;SponsorshipCheckoutFunnel" ... View more

I have unique objects to define, but what you're saying is that have to have something with numbers in it like if I defined a new UDO variable (something else to include in onboarding???):   First Step - 'var1': '1' Second Step - 'var1': '2' Third Step - 'var1': '3' etc....   and map it out to (enh_checkout_step), which will fire the below for me on each step?   First Step - ga('ec:setAction','checkout', {'step': 1}) Second Step - ga('ec:setAction','checkout', {'step': 2}) Third Step - ga('ec:setAction','checkout', {'step': 3})   Please clarify if I've got this wrong or is there another way? ... View more

I'm still unsure how to have it fire using tealium. I know I need these to define the enhanced ecommerce funnel but I'm completely in the dark on what I need to do to make it fire using an extension or something??? If so, which?   ----------------   ga('ec:setAction','checkout', {'step': 1})   and   ga('ec:setAction','checkout', {'step': 2})   etc.... ... View more