(Click to enlarge example of console warning message.)
Due to the limited usage of 2G network, we expect the current 2G Google intervention to a minimal impact on enterprise customers at this time. We are proactively addressing future issues that may develop if Google continues to promote practices that contradict Internet community standards.
DTM’s goal has always been to create and support the most powerful and flexible features in the space. We believe that must include allowing our users to leverage both synchronous and asynchronous technologies.
Customers who are significantly concerned about 2G Chrome users can use a more asynchronous deployment of DTM and continue to use the robust set of asynchronous specific features of DTM.
If you are seeing this warning and want to use DTM with a more asynchronous deployment, and remove all “document.write” calls (and remove the warning), please do the following.
3rd Party Tag
Review the code within the editors to ensure it isn’t using “document.write". If the code you are deploying through DTM uses “document.write” it may be affected.
Our engineering department is actively working with Google to understand the full impact of the changes. We are also looking into the Adobe libraries that utilize the document.write functionality. As you pointed out, at.js does not use document.write and thus is not impacted. We always suggest our customers update their implementations to the latest code libraries for all solutions. With that being said, we will be updating DTM to support at.js in the near future.
what about Adobe's own tools which throw the document.write warning namely mbox.js and target.js. Will these be updated or will users be forced to move on to at.js? If the latter then when will at.js be supported by DTM?