target global mbox extensible JS error from Adobe Visitor API Library | Community
Skip to main content
ajaxdinesh
ajaxdinesh
Level 2
September 5, 2024
Solved

target global mbox extensible JS error from Adobe Visitor API Library

  • September 5, 2024
  • 1 reply
  • 1254 views

Hello Team,

I've observed that a "target global mbox extensible error" is being triggered, but only on certain pages, and notably, when those pages are fully loaded. As a result of this error, we are not seeing any Target delivery on those pages, and the associated Analytics metrics are not being triggered either. Upon investigation, it appears that this error is originating from Adobe Visitor API library. This could be contributing to the failure in both the Target delivery and the Analytics calls. Is there any one facing this issue and identify the root cause and suggest a solution?

 

I have attached the error details in the png format.

 

Thanks,

Dinesh

    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 RiteshY18

    @ajaxdinesh it could be due to incorrect target-global-mbox script/ AT.js implementation or script placement on the page where it is been call or configuration because script run could not able to execute activity/experience on the page 

    1 reply

    RiteshY18
    Community Advisor
    RiteshY18Community AdvisorAccepted solution
    Community Advisor
    September 11, 2024

    @ajaxdinesh it could be due to incorrect target-global-mbox script/ AT.js implementation or script placement on the page where it is been call or configuration because script run could not able to execute activity/experience on the page 

      ajaxdinesh
      ajaxdineshAuthor
      Level 2
      September 12, 2024

      Thank you for your response. However, I still need some clarification on what you mean by "incorrect target-global-mbox script/AT.js implementation or script placement on the page." Since we are using the same configurations globally across all pages, I find it puzzling that this issue only occurs on certain CMS pages and not others. Could you elaborate on what specific factors in the script implementation or placement might be causing this issue on a subset of pages, even though the same setup is used site-wide?

      RiteshY18
      Community Advisor
      RiteshY18Community Advisor
      Community Advisor
      September 13, 2024

       the script is implemented at the template level or page level? 

      Terms & ConditionsAccessibility statement

      Loading footer...