Highlighted

Question about Tnt Ext - flicker free

Silver Contributor
Silver Contributor

Tnt Ext - Flicker-Free will introduce certain content blocking. The timeout value 7s is for Tealium side wait for ATnt response. But if this is really timeout, may I know the default content blocked will be visible again or not? Because right now I found in some circumstance that the block was there, no default content shown and mbox was fired but no ATnt content shown however, in Chrome inspection mode, I do see them. Please advise. Thank you.

3 REPLIES 3
Highlighted

Question about Tnt Ext - flicker free

Tealium Employee

Hi Dave,

 

If you are using the Tealium Target extension to define your mbox, if there is a timeout (default 7 seconds), the publish engine logic injected into the utag.sync.js file should set the container ID to visible again if the requested mbox (content) is not returned in time (default 7 seconds).

Note, there is no content blocking involved.

 

There might be other challenges in your exact scenario. I'll help you with sorting your current issues.

Kind regards,
Kevin

Highlighted

Question about Tnt Ext - flicker free

Silver Contributor
Silver Contributor
Hi Kevin, nice to e-meet you right here :) Thanks a lot for your support!
Highlighted

Question about Tnt Ext - flicker free

Silver Contributor
Silver Contributor

Hi @kevin_faurholt, I tried to edit the hidden div id with another name via Chrome inspection mode, it appeared. Content management team wrapped the default banner (what we called safety banner) with a div (where Tnt Ext fires a mbox with matched div id - dom element) and its id is equal to the mbox div id. That why I think when ATnt timeout, the hidden style is effective to both default banner div and mbox div because their ids are the same. I will further prove the above by changing default banner div id not equal to corresponding mbox div id on Monday morning HKT. Meanwhile, please comment if you have any other findings as well. Thank you for your support again.