Highlighted

Issues when using "Bundle Flag = No" and "Tag Timing = DOM Ready"

Silver Contributor
Silver Contributor

Hi all, 

I'm having some issues to trigger a tag programatically using ".link()" function.

After some debugging I found the issue is caused because I have an Adobe Eloqua and Ghostery tags configured as "Bundle Flag = No" and "Tag Timing = DOM Ready". I tried creating a new Tealium Custom Container tag using that configuration and I got not issue.

I found ".link()" function doesn't work because "this.iflag" is false (value 0) so "[tag].send" is not called. The reason why "this.iflag == 0" is "utag.loader.END()" is never called because "[tag].load == 1" for Eloqua and Ghostery tags.1.png

 

 

If I bundle the tags or set them up as "Tag Timing = Prioritized" ".link()" function works as expected.

Thanks, 

6 REPLIES 6
Highlighted

Issues when using "Bundle Flag = No" and "Tag Timing = DOM Ready"

Tealium Employee

Hi @oscarmartinezm 

The iflag property still being set to 0, would indicate that there was an error when loading a tag.
I would enable the utag debug mode, https://docs.tealium.com/platforms/javascript/debugging/ and see what is happening.

Most likely, a particular tag is not calling the utag.LOAD function.

Adrian

Ask me anything Tealium related or Javascript, or NodeJS.
Please remember to mark solutions as accepted for future searchers.
Highlighted

Issues when using "Bundle Flag = No" and "Tag Timing = DOM Ready"

Silver Contributor
Silver Contributor

Hi @adrian_browning  thanks for response.

If I debug it, it looks is not sent. But if I add a breakpoint to last tag line of code, I get there with no issues. Also, catch sentence is not executed, so I assume everything fine.

One more thing. If there is an issue into the code I assume we should get same error even if tag is bundled or tag timing is prioritizaded. But on those config everything works as expect.

Screen Shot 2020-06-22 at 07.50.09.pngScreen Shot 2020-06-22 at 07.55.07.png

Highlighted

Issues when using "Bundle Flag = No" and "Tag Timing = DOM Ready"

Tealium Employee

Hi @oscarmartinezm 

I see in your first screenshot, it shows that 1926 hasn't loaded, most likely this is the cause, unless there is any other tags showing this.

So a tag not loading, will cause other tags not to send, depending on the scope of when they are to fire.

I would raise a support ticket so someone can look at the page in question, and direct you to what is happening. (Unless you want to message here, or DM me).

With regards to working when bundled/ change of timing, that would indicate a timing issue, with something the tag is trying to do.

Adrian

Ask me anything Tealium related or Javascript, or NodeJS.
Please remember to mark solutions as accepted for future searchers.
Highlighted

Issues when using "Bundle Flag = No" and "Tag Timing = DOM Ready"

Silver Contributor
Silver Contributor

@adrian_browning  I sent you DM.

Thanks!

Highlighted

Issues when using "Bundle Flag = No" and "Tag Timing = DOM Ready"

Silver Contributor
Silver Contributor

I found something else. It looks like the issue is because I'm calling utag.link() before tags complete. Look this. I'm printing the tag where b.load greater than 0. I'm getting the print before the tag complete.

1.png2.png

 

Highlighted

Issues when using "Bundle Flag = No" and "Tag Timing = DOM Ready"

Silver Contributor
Silver Contributor

Forget everything. I think I have found the issue. There was a tag containing "only code". It was a tag not following Tealium template.