Skip to main content

Persistent CORS Errors with tlx.3lift.com & Ad Placeholders Appearing

Eula Videl
Edited

Hi,

 

I'm hoping for some assistance with an issue I'm seeing on my site: https://littlepandatranslations.com

 

I've noticed that some ad units are displaying placeholders instead of actual ads. When I check my browser's developer console, I consistently see CORS errors related to tlx.3lift.com.

 

The specific error message is: Access to fetch at 'https://tlx.3lift.com/header/auction?lib=prebid&v=9.33.0&referrer=https%3A%2F%2Flittlepandatranslations.com%2F[page-slug]' from origin 'https://littlepandatranslations.com' has been blocked by CORS policy: No 'Access-Control-Allow-Origin' header is present on the requested resource.

 

This is followed by: Failed to load resource: net::ERR_FAILED (or sometimes net::ERR_FAILED 200 (OK) for POST requests, which I understand still means the response was blocked by CORS).

 

Troubleshooting steps I've taken:

  • Confirmed my browser adblocker is completely turned OFF for my site.
  • Tested in an incognito/private browsing window (with extensions disabled).
  • The issue persists across different pages on my site.

 

I'm concerned this might be preventing bids from TripleLift from being processed correctly, leading to the placeholders and potentially impacting ad performance.

 

Could you please help investigate if there's a configuration issue or something else that might be causing these CORS errors with tlx.3lift.com?


I've attached a screenshot of the console errors for your reference.

 

Thank you for your time and help!
 

0

Comments

2 comments

Date Votes
  • Support
    • Journey Support Team

    Hey Eula Videl - I'm having our team take a closer look. As soon as we have an update, we'll be in touch! 

     

    0
  • Eula Videl

    Thank you! I'll be patiently waiting.

    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