DTM Parser Blocking | Community
Skip to main content
C
carolinam648034
October 25, 2017
Solved

DTM Parser Blocking

  • October 25, 2017
  • 1 reply
  • 4172 views

I was wondering if anyone knew any strategies to debug this type of error. And what are the limitations on using document.write in DTM.

This is the error I'm getting on this page:

Wiley Efficient Learning: Smarter Test Prep

satelliteLib-71a8714270b83332e125616807c2e6c5aa14c08b.js:10 A Parser-blocking, cross site (i.e. different eTLD+1) script, https://assets.adobedtm.com/6e626c9ec247e474f6b98eb15a79a185cf7e26a5/scripts/satellite-5769804464746d687e001a0d.js, is invoked via document.write. The network request for this script MAY be blocked by the browser in this or a future page load due to poor network connectivity. If blocked in this page load, it will be confirmed in a subsequent console message.See https://www.chromestatus.com/feature/5718547946799104 for more details.

This post is no longer active and is closed to new replies. Need help? Start a new post to ask your question.
Best answer by Kaushalendra

Hi carolinamedellin​,

The console messages you see are warning messages. These are triggered for the Third Party tags which are hosted through DTM. As DTM hosts these tags using the document.write, browser issues a warning on slow networks that the script might be blocked. Unless you see actual blocking error message, it doesn't have any impact.

This is isolated to Chrome browser as they have this feature in place to issue warnings and flag such scenarios. However, seeing the architecture of DTM, there is not much that can be changed to avoid such warnings. In case you see actual errors being triggered which blocks the script, we would need an action plan which would include steps to minimize the script and optimize the load times.

1 reply

Kaushalendra
Adobe Employee
KaushalendraAdobe EmployeeAccepted solution
Adobe Employee
October 25, 2017

Hi carolinamedellin​,

The console messages you see are warning messages. These are triggered for the Third Party tags which are hosted through DTM. As DTM hosts these tags using the document.write, browser issues a warning on slow networks that the script might be blocked. Unless you see actual blocking error message, it doesn't have any impact.

This is isolated to Chrome browser as they have this feature in place to issue warnings and flag such scenarios. However, seeing the architecture of DTM, there is not much that can be changed to avoid such warnings. In case you see actual errors being triggered which blocks the script, we would need an action plan which would include steps to minimize the script and optimize the load times.

Terms & ConditionsAccessibility statement

Loading footer...