Configurer les fichiers ads.txt et app-ads.txt

As a publisher and Triton Digital customer, you must create and host an ads.txt or app-ads.txt file on your website or mobile app domain. These files list the companies that you have authorized to sell your ad inventory:

• ads.txt is for web browser-based players that sell a publisher’s inventory for live streaming stations.

• app-ads.txt is for app-based players that sell a publisher’s inventory via mobile apps and similar devices such as smart speakers.

Voir également :

• Official documentation: Ads.txt - Authorized Digital Sellers

• Sellers.json

The "ads" in ads.txt and app-ads.txt stands for Authorized Digital Sellers (ADS), an initiative developed by the IAB Tech LAB. This specification brings important benefits to advertisers and to you, the publisher:

• Fraud prevention: Blocks unauthorized sellers and counterfeit inventory.

• Transparency: Advertisers can validate who is authorized to sell ad space.

• Revenue protection: Ensures publishers retain control over their ad sales.

Understand the File Contents

Un ads.txt or app-ads.txt file must be a plain-text file with the filename extension .txt . You place these files at the root of your web site. Exemple : https://example.com/ads.txt.

Owner Domain

Le OWNERDOMAIN directive declares ownership of your inventory across the supply chain. This directive must appear once per app-ads.txt or ads.txt file and must represent the business domain of the site owner, you.

Le OWNERDOMAIN is part of the version 1.1 standard that was introduced in 2022. If your ads.txt or app-ads.txt files follow an older standard it is important that you update them to include OWNERDOMAIN.

• Pour les éditeurs : OWNERDOMAIN in the app-ads.txt or ads.txt file must match the domain field in your sellers.json entry. A mismatch might be flagged by demand-side platforms (DSP) and advertisers as a mis-configuration or risk, potentially affecting trust and monetization.

• For resellers who also operate their own inventory and maintain an app-ads.txt or ads.txt file: OWNERDOMAIN may differ from the intermediary's domain in sellers.json. This mismatch is expected, as the domain in sellers.json reflects the intermediary, not the original publisher.

Authorized Advertising System Records

Each record in an ads.txt or app-ads.txt file contains four comma-separated fields to specify an authorized supply-side platform (SSP).

Par exemple :

example.com, 99999, RESELLER, 1234567890abcdef

• Domain name of the authorized supply-side platform (SSP): example.com.

• Publisher’s ID: The publisher’s account ID with the SSP is 99999.

• Type of relationship: The SSP is a RESELLER for the publisher.

• Certification authority ID: 1234567890abcdef.

Relationship Type: DIRECT or RESELLER

The type of relationship in a record specifies what the publisher allows the SSP to do:

• DIRECT: The publisher works directly with the SSP to create and manage deals and sell inventory. As a Triton Digital customer, you have a direct relationship with Triton Digital.

• RESELLER: The publisher authorizes a third party to resell its inventory, either partially or in full. For example, ad network and third-party sales houses are resellers.

Mis-categorizing a reseller as DIRECT may mislead DSPs or advertisers into treating that entity as the primary sales channel, potentially bypassing the publisher and reducing direct revenue opportunities.

Create ads.txt and app-ads.txt

Here is an example of the mandatory lines to include in your ads.txt and app-ads.txt files. In your actual files, you will have to change lines 1 to 3 for your organization.

OWNERDOMAIN=example.com
tritondigital.com, example-pub-id, DIRECT, 19b4454d0b87b58b
adswizz.com, example-pub-id, RESELLER
appnexus.com, 1577, RESELLER, f5ab79cb980f11d1
rubiconproject.com , 9755, RESELLER, 0bfd66d529a55807
smartyads.com, 100152, RESELLER, fd2bde0ff2e62c5d
smartadserver.com, 4831, RESELLER, 060d053dcf45cbf3

1. Open any plain text editor, such as Notepad (Windows) or TextEdit (macOS).

2. Create a file and name it ads.txt ou app-ads.txt, depending on how you will use it.

3. Line 1: Type OWNERDOMAIN=example.com , replacing example.com with your actual business web domain name.

4. Line 2: Copy your Triton Digital authorized advertising system record and paste it into the file. See Get Your Authorized Advertising System Record.

5. Line 3: Replace example-pub-id with your Triton Digital Account ID, which is the second field in line 2.

6. Lines 4-7: Copy and paste these lines into your file.

7. If you are working with other resellers, add records for them at the end of the file.

8. Save the file.

Place ads.txt

The ads.txt file must be placed at the root level of your station or show's web site. It must be publicly accessible and not geo-blocked.

1. Upload the ads.txt file to your station or show's web site's root directory. You might need to ask your web developer team to do this for you.

2. Test the web site to ensure the file is correctly placed. See Validating Your ads.txt/app-ads.txt File.

Place app-ads.txt

The app-ads.txt file must go to your app site's root directory for the URL that is associated with your app's publisher, not the company that developed the app. If you have multiple developer URLs for different apps, ensure that each app's app-ads.txt file is implemented on its respective developer URL. Also, you must ensure that the Google Play or Apple App Store's listing for your app uses the same developer URL as the one where you placed the app-ads.txt file.

1. Upload the app-ads.txt file to your app publisher's root directory. You might need to ask your app developer team to do this for you.

2. For Android apps on Google Play:

   1. Sign in to your Play Console.

   2. Select the app.

   3. Navigate to Store Presence, then Store Listing.

   4. Add your developer’s website URL (where you have placed the app-ads.txt file) to the Contact Details section.

3. For Apple iOS apps on Apple App Store:

   1. Sign in to your Apple Developer account.

   2. Go to the listing for the app.

   3. Add your developer website in the marketing URL field of your store listing.

4. For other app stores, if your app is listed on other app distribution systems, go to each one and ensure the developer URL is listed correctly.

5. Test the web site to ensure the file is correctly placed. See Validating Your ads.txt/app-ads.txt File.

Validate Your ads.txt or app-ads.txt File

Simple Placement Test

First you should conduct this easy test to ensure your file is correctly placed and can be read:

1. Using your web browser, go to your station or show’s home page.

2. In your browser, enter the URL for your ads.txt or app-ads.txt file. Exemple : https://example.com/ads.txt ou https://example.com/app-ads.txt .
   The contents of your ads.txt or app-ads.txt should appear in your browser. If it does not, it usually means the file is not correctly placed in the root folder of your site's web server.

3. For app-ads.txt, you should also verify if your app-ads.txt file has been well implemented on the developer URL as listed on Google Play, App Store, or any other app associated with your inventory.

4. Repeat the above for every station, show, and app that uses an ads.txt or app-ads.txt file.

Use the Validator

You can optionally use the ads.txt validator on the TAP Programmatic Settings ads.txt page to see if your ads.txt or app-ads.txt file is properly set up for Triton Digital.

This tool only validates the Triton Digital entry, it does not validate the entries for other partners.

1. Go to TAP Settings > Programmatic > app-ads.txt/ads.txt.

2. Expand ads.txt or app-ads.txt.

3. Select Validate ads.txt on my inventory or Validate app-ads.txt on my inventory.

4. Review the report that appears after a few moments.

You might receive this message: "Not able to retrieve the ads.txt file from the station url". This happens if our validation scripts were not able to retrieve the ads.txt/app-ads.txt file due to an unknown exception. Cela ne signifie pas nécessairement que votre mise en place est incorrecte ou que la livraison publicitaire est touchée. Au lieu de cela, il peut y avoir un problème avec les liens vers le serveur. If our scripts fail to retrieve the ads.txt or app-ads.txt  file that could also happen with the demand partner. Nous vous conseillons de vérifier votre chemin d'accès.

Understand Your Validator Report

La génération du rapport peut prendre quelques instants. Plus vous possédez de stations, plus le procédé est long.

Lorsque le rapport s'affiche, il comprend deux colonnes : Résultats et Nombre de stations. Stations count refers to how many of your stations returned that result.

Export Validator Results

Click Export all stations detailed results at the bottom of the validator results to download a CSV file with a detailed station-by-station breakdown of the validator results. If you are not prompted for a download location, check that your browser is not blocking popups or downloads.

If you continue to have ads.txt app-ads.txt problems, please contact Triton Digital Customer Support.

Best Practices for Managing ads.txt and app-ads.txt

Following these best practices will help you maximize the effectiveness of your ads.txt or app-ads.txt file.

Regularly Update the File

• Frequently audit your ads.txt and app-ads.txt files to ensure it reflects current authorized sellers.

• Remove outdated entries for sellers you no longer work with. Outdated entries generate no revenue, and files with excessive dormant entries can potentially lead to other problems.

• SSPs in your file should only represent active partnerships that generate revenue.

Use a Primary Publisher Website

• For app-ads.txt, host the file on your official publisher domain linked in app store listings. This ensures that advertisers can verify the authenticity of your app's inventory.

Ensure it is Accessible

• Do not geo-block access to ads.txt and app-ads.txt! DSPs operate in many countries and may see it as missing if there is any geo-blocking on the files or server, which can affect revenue.

• Ensure the ads.txt abnd app-ads.txt files are accessible using both http:// et https:// protocols.