Announcements

What's Happening

  • @NagaSai  If you are adding the tag through utag.sync the script will be running . too early to rely on utag functions. However you can wrap the target tag within an if statement which checks for the cookie itsself - something like this.   var consent_cat = "c1"; function readCookie(name) { return (name = (document.cookie + ';').match(new RegExp(name + '=.*;'))) && name[0].split(/=|;/)[1]; } var consent = readCookie("CONSENTMGR"); if (typeof consent !== "undefined" && (consent.indexOf(consent_cat + ":1") > -1 || consent.indexOf("consent:true") > -1)) { // ADOBE TARGET SCRIPT } updating "conset_cat" to whichever category in the CONSENTMGR you want to checkIf you aren't using our built in consent manager, you can adapt the code accordingly to work with whatever cookie gets set.

    0

    1

    Tealium Employee

    Jan 24, 2020

  • Hello @fabb    You can use the following function in an extension to update the QP values utag.loader.RDqp(b); This is the same function which runs when utag.js loads for the first time, so the output should be the same!

    0

    1

    Tealium Employee

    Jan 24, 2020

  • Hello @MountainMaster  Thanks for pointing this out - this has been highlighted, and should be fixed in a future release for the tag. Be assured that the warning in the console should have no impact, and should not cause any problems with your tracking / cause no duplicate events. When initialising twice, The FB pixel recognises this and sends out the warning.

    0

    1

    Tealium Employee

    Jan 24, 2020

  • Hi @MountainMaster  Do you have any code explicitly calling utag.view()? Tealium will automatically call a utag.view when it detects the page has loaded, and you can force another page view by calling that function from the site code (or code within an extension). There is a configuration option to suppress the automatic page view call by setting  window.utag_cfg_ovrd.noview = true; in a preloader scoped JS extension.

    0

    5

    Tealium Expert

    Apr 4, 2019

  • Hello @tealium23 !Judging by your description, there is a syntax error in the custom template which is causing an issue with your other tags from running. Have a look at the template and correct any syntax errors you can find - if you are unable to find anything, you can reach out to support (or drop me a message) who will be happy to help out!

    0

    1

    Tealium Employee

    Jan 24, 2020

  • How to create multiple marketing tag in tealium "javascript code" extension.When i tried creating using 1 tag and then specifying the variables in the "javascript code" extension, the last passed value tag is only firing.

    0

    0

    By aswathi

    Rookie Contributor

    Jan 24, 2020

  • Hi @aswathi,It looks to me that the b object is out of "runtime" scope - i.e. b does not exist when the click handler fires. Try to change the reference to utag.data.prop53 instead - assuming that the variable prop53 is present there. If this does not get you on the right track, post a link to the page where you are trying to get it to work and I'll take a look for you.Kind regards,Kevin

    0

    2

    Tealium Employee

    Jan 13, 2020

  • Hi Christian,  Just updating the reply. All communication from the page to the Tool window happens via an Iframe postMessage, so all data has to be passed via the message object from the Tools corresponding js file. Simply read what you need from window in there, and pass it to the Tool via the provided send method.   Kind regards, Kevin

    0

    1

    Tealium Employee

    Jan 24, 2020

  • The community wants to shine its Expert Spotlight on @pmeyerdk, representing the EMEA region! We were delighted to see Peter recently published in the ConversionXL blog with a post about TiQ. Way to represent! Keep reading below to learn mo...

    1

    0

    Community Manager

    Jan 22, 2020

Top Solution Authors

Join the conversation

Find and follow interesting people, join groups for discussion and share files

23007

Members

140

Online

11244

Posts