Skip to main content

Comments

2 comments

  • Yi Xuan Chin

    More info: Upon checking ‘Console’ under ‘Inspect’, I noticed the error below:

    Access to fetch at 'https://tlx.3lift.com/header/auction?lib=prebid&v=9.8.0&referrer=https%3A%2…2F10%2F30%2Fdividend-withholding-tax-malaysia%2F&tmax=2801&us_privacy=1---' from origin 'https://nomoneylah.com' has been blocked by CORS policy: No 'Access-Control-Allow-Origin' header is present on the requested resource. If an opaque response serves your needs, set the request's mode to 'no-cors' to fetch the resource with CORS disabled.

    The above CORS error (or issue?) is not found on posts where I use the HTML code below to disable ads:

    <div id="ad-management-config-settings" data-blocklist-all="1"> </div>

     

    0
  • John
    • Journey Support Team

    Hi Yi Xuan Chin! The issue you were encountering is unrelated to the console chatter. It's totally normal to have a good bit of logging in the console with programmatic advertising, and you can safely disregard it.

    Rather, there was a style conflict with the site that was causing the issue with scrolling. We went ahead and made an adjustment on our end, and you should be all set. Thanks!

    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