- TLC Home Home
- Discussions Discussions
- Documentation Documentation
- Knowledge Base Knowledge Base
- Education Education
- Blog Blog
- Support Desk Support Desk
I am experiencing a flicker problem when implementing Adobe Target via the Tealium Custom Container. Is there a way to alleviate this issue without modify the code base to include the utag.sync.js file? Or is the only way to alleviate this flicker issue to include the utag.sync.js file header in the code and then place the adobe target at.js code within the utag.sync.js file?
Side Note: The reason I am using a custom container is due to the fact the built in Target Tag does not seem to work. It looks like it loads target but when going into Adobe Target itself it says that Target related libraries are not found.
Any help would be great
Hello @zbenchley ,
We faced the same issue and finally settled with utag.sync.js in head section. That's the best way and easiest way I believe.
Target recently said that the new version is compatable with async load. But not yet tried, we are planning to do it later this month, will update in this post when we get the test results
Thanks! I was just about to give up but I think I just came up with an approach that works for the async and solves the flicker. I upgraded to at.js 2.0.0 in a Tealium Custom Container. However, this still caused the flicker. Within the at.js 2.0.0 code I was able to change a setting for 'bodyHidingEnabled'. This was set to true. I change this to 'bodyHidingEnabled': target.css.status === "hidden". Once I changed this the flicker was alleviated. I hope this helps when you begin your migration in the next month.
Copyright All Rights Reserved © 2008-2023