Skip to main content

Console errors question

Completed

Comments

5 comments

  • Official comment
    Support
    • Journey Support Team

    Hi Annette Jones ! Of the console errors we typically see associated with programmatic ads, CORS, 404 errors, and scripts failing to execute/load are very common and no cause for any alarm. They just mean that an ad that's loaded is requesting a resource that it's unable to get it from its origin. There isn't much we can do about these errors because they are coming from third party scripts by our ad partners, but they're to be expected and nothing to worry about.

    Thanks!

  • Ryan Kretch

    I get these console errors too! Thanks for the clarification Support .

    0
  • Annette Jones

    Hi Support 

    How long does this last, as it still hasn't changed? Will ads always be displayed this way?

    Thanks

     

    0
  • John
    • Journey Support Team

    Hi Annette,

    Having some chatter like this in the console is a normal part of programmatic advertising. What actually shows will vary based on a number of factors like the reader, location, etc… But it's normal for some logging like this to be present in the console, and it can be safely ignored.

    0
  • Annette Jones

    Hi John

     

    Thank you, that's good to know!

    0

Journey is Self Supported

Our support staff is monitoring this forum everyday for bugs related to ad delivery, the display and functionality of the Journey dashboard, and any bugs related to the onboarding process. We are typically unable to assist with non-bug related issues like RPM performance expectations, issues setting up the ads.txt file, and questions already answered by our existing help docs. Read here for a more detailed breakdown of how Journey is self-supported and our recommendations for how to find answers to common issues.

Please sign in to leave a comment.

Powered by Zendesk