Skip to main content

Can't get ads.txt recognised. Have exhausted troubleshooting options

Comments

2 comments

  • Sarah Trivuncic

    Ads.txt is publicly accessible at both www and non-www, serves as text/plain, and is confirmed via web header inspection. Please confirm your onboarding bot is not being blocked and manually trigger a rescan?

    0
  • Support
    • Journey Support Team

    Sarah Trivuncic - thanks for reaching out! It looks like we're seeing some small differences in spacing when compairing the version of the file on your site with the one we're hosting for your site.

    Could I have you replace the file you currently have on the site with a 301 redirect to the version of this file we're hosting for you?  I recommend connecting with your host if you're unsure how to accomplish this. 

    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