內容簡介
廣告合作夥伴經常向其已授權銷售人員的 Ads.txt 和 App-ads.txt 列表添加新的需求來源。
使用同一工具創建 Ads.txt 和 App-ads.txt 文件
添加“即用”代碼片段的手動項目（複製-粘貼）
根據需求編輯和管理您的文件
在發布之前/之後查看 WordPress Ads.txt 和 App-ads.txt 文件
注意：Google Ad Manager 和 AdMob（Google 的移動廣告網絡）現在支持 app-ads.txt，這是面向應用程序發行商的反欺詐協議。我們為什麼要關心？Google 在2019年4月表示，其 DSP Display＆Video 360 將從2019年8月開始停止購買未經授權的應用內庫存（Centro 也是如此）。考慮到其市場領導地位，Google 從購買和銷售雙方對 app-ads.txt 的支持將有助於推動應用程序發行商采用這一標準。
WordPress Ads.txt & App-ads.txt 管理器如何實現 app-ads.txt：
在您的應用商店列表中提供開發人員網站。確保在應用商店的開發人員網站部分中可以訪問適當的開發人員網站 URL（廣告平台將使用此網站驗證 ads.txt 或 app-ads.txt 文件）。
在 WordPress Ads.txt & App-ads.txt 管理器中，轉到設置頁面。
廣告來源域
- SSP、Exchange、連接競標人的規範域名（它們會發布一份詳細說明使用哪個域名的文檔）。
發行人 ID
- 此必須包含交易中使用的相同值（即 OpenRTB 招標請求中 SSP/Exchange 指定的領域 | OpenDirect 中的發行方組織 ID）。
關係類型：（直接，轉售商）
- 您的直接需求夥伴應列為“直接”。如果您的合作夥伴使用第三方轉售商出售您的庫存，則應將此類供應商列為“轉售商”。在任何情況下，除非您或您的合作夥伴與他們有直接關係，否則不應向您的 app-ads.txt 文件添加任何提供者。
廣告來源 ID
- 識別認證機構內的广告系統的 ID。
對於所有授權您的數字銷售人員或庫存轉售商都進行操作。
單擊“保存更改”，WordPress Ads.txt & App-ads.txt 管理器插件將在您的網站根目錄下創建一個虛擬的 .txt 文件，例如 www.mysite.com/ads.txt 或 www.mysite.com/app-ads.txt。您可以隨時編輯內容。
請務必清除緩存
注意1：使用 app-ads.txt 不是強制性的，但強烈建議使用，尤其是如果您擔心其他人可能正在欺騙您的應用程序。
注意2：爬行和驗證 app-ads.txt 文件可能需要最多24小時。請等待至少24小時以更新 app-ads.txt 狀態。
注意3：由於 ads.txt 文件應位於域名的根目錄中，因此此插件目前僅適用於 root level domain，例如 example.com。它不適用於安裝在子域、子目錄或多站點網絡中的 WordPress。
什麼是 app-ads.txt？
2017年6月，IAB（The Interactive Advertising Bureau Tech Lab）推出了 ads.txt，該文件使 Web 發布商能夠指定其庫存的授權數字銷售人員。Ads.txt 幫助該行業區分真正的供應源和偽造的供應源。在其即期成功和采用之後，將 ads.txt 的範圍擴展到移動應用環境是下一個合乎邏輯的步驟。App-ads.txt 是此規範的移動應用內相當部分，移動發布商可以使用它。
外掛標籤
開發者團隊
② 後台搜尋「Ads.txt & App-ads.txt Manager for WordPress」→ 直接安裝（推薦）
原文外掛簡介
Ad partners are frequently adding new demand sources to their Ads.txt & App-ads.txt lists of authorized sellers.
Create your Ads.txt & App-Ads.txt files with the same tool (all-in-one)
Add manual entries (copy-paste) for « ready-to-use » code snippets.
Edit & manage your files on demand
View WordPress Ads.txt & App-ads.txt files before/after publishing
Note : Google Ad Manager and AdMob, Google’s mobile ad network, now support app-ads.txt, the anti-ad fraud protocol for app publishers. Why we should care? Google said in April 2019 that its DSP Display & Video 360 would stop buying unauthorized in-app inventory starting in August 2019 (same with Centro). Given its market leadership position, Google’s support for app-ads.txt from both the buy and sell sides will help propel adoption of the standard by app publishers.
How does WordPress Ads.txt & App-ads.txt Manager work to implement app-ads.txt:
Provide a developer website in your app store listings. Ensure that the proper developer website URL is accessible in the developer website section of the app store (advertising platforms will use this website to verify ads.txt or app-ads.txt files).
In WordPress Ads.txt & App-ads.txt Manager, go to setting page.
Ad Source Domain
— The canonical domain name of the SSP, Exchange, system that bidders connect to (they publishes a document detailing what domain name to use).
Publisher ID
— This must contain the same value used in transactions (i.e. OpenRTB bid requests) in the field specified by the SSP/exchange (For OpenRTB = publisher ID | For OpenDirect = publisher’s organization ID).
Type of Relationship: (Direct, reseller)
— Your direct demand partners should be listed as “direct.” If your partners are using third-party resellers to sell your inventory, such providers should be listed as “reseller.” In any case, you should not add any provider to your app-ads.txt file unless you or your partner have a direct relationship with them.
Ad Source ID
— An ID that uniquely identifies the advertising system within a certification authority.
Do it for all your authorized digital sellers or resellers of your ad inventory.
Click « Save changes » and WordPress Ads.txt & App-ads.txt Manager plugin will create a virtual .txt file in the root of your website; for example, www.mysite.com/ads.txt OR www.mysite.com/app-ads.txt. You can edit the content whenever you need.
Make sure to clear your cache
Note 1 : Use of app-ads.txt is not mandatory, but is highly recommended, especially if you are concerned that others may be spoofing your app.
Note 2 : It can take up to 24 hours to crawl and verify your app-ads.txt files. Please wait at least 24 hours for the app-ads.txt status to update.
Note 3 : Since ads.txt file is supposed to be in the root directory of a domain name, this plugin currently only works for root level domain like example.com. It does not work for WordPress installed in subdomain, subdirectory, or a single site in a multi-site network.
What’s app-ads.txt?
In June 2017, the IAB (The Interactive Advertising Bureau Tech Lab) launched ads.txt, a file enabling web publishers to designate authorized digital sellers of their ad inventory. Ads.txt helped the industry distinguish real supply sources from fake ones, and after its immediate success and adoption, the next logical step was to extend the reach of ads.txt into the mobile app ecosystem. App-ads.txt is the mobile in-app equivalent of this specification, which mobile publishers can implement.
The app-ads.txt file is the version of ads.txt for mobile in-app and OTT advertising, to combat bad actors that disguise themselves as another company’s app in order to siphon the money that advertisers are spending on mobile and OTT advertising. App-ads.txt files are formatted the same as ads.txt files (view IAB FAQ for ads.txt and app-ads.txt).
Thanks to app-ads.txt file, Mobile and OTT app publishers can list the ad tech vendors that are authorized to sell or resell their ad inventory, and programmatic ad buyers can check these lists to make sure that a company claiming to offer an app’s inventory is actually able to sell the app’s inventory.
This file opens the door for a new level of transparency.
