Of course it's an asynchrounous issue since the necessary calls to Target to retrieve information about the running A/B tests while the rest of the page continuing to load / render.Īdobe is having it's own documentation on this, providing a body-hide script that needs to be implemented on the page (I placed it in the for testing). Problem is: the page flickers when displaying Target A/B tests which was never the case when we synchronously played out the old at.js library via and it blocked the rendering of other page parts. The target library is played out using the visitor ID service is used, all good so far. After using Adobe Target synchronously (through ) my company wants to jump on the asynchronous train using Adobe Experience Cloud Visitor ID as tag in conjunction with the latest Adobe Target tag (2.3.0), both bundled into the utag.js.
0 Comments
Leave a Reply. |