Step 6: Updating ads.txt

ads.txt (Authorized Digital Sellers) is how you publicly declare that AppLixir is allowed to sell your inventory. Without it, fill rates and CPMs drop significantly — and for a React Native WebView it is part of what makes the domain match at all.

Add it to your domain

1. Download the current AppLixir entries from cdn.applixir.com/ads.txt.
2. Merge those lines into the ads.txt file at the root of the domain you registered — e.g. https://yourgame.com/ads.txt. If you already have an ads.txt, append our lines; there is only one file per domain.
3. Deploy and confirm https://yourgame.com/ads.txt loads the entries publicly.

Your exact entries live in the dashboard

The dashboard shows the precise ads.txt lines for your account (including your seller ID). Copy from there if the CDN file and your dashboard differ.

React web

The ads.txt goes on the domain that serves your React app — the same domain you registered in the dashboard. If you host the app on a subdomain (play.yourgame.com), the ads.txt must be on that subdomain's root, or use a subdomain redirect record per the IAB spec.

React Native

This is the step React Native integrations most often miss. The WebView loads a real https:// domain (see Step 4) — that domain needs the ads.txt, because the ad request is matched to it by referrer. A WebView pointed at a domain with no ads.txt will under-fill even when everything else is correct.

For mobile games distributed through an app store, you may also need an app-ads.txt file with the same entries, referenced from your store listing.

Next: Testing & troubleshooting.