http:\/\/example.com\/ads.txt:<\/a><\/p>\n <\/p>\n
#<SSP\/Exchange Domain>, <SellerAccountID>, <PaymentsType>, <TAGID>\u00a0
greenadexchange.com, 12345, DIRECT, AEC242
blueadexchange.com, 4536, DIRECT
silverssp.com, 9675, RESELLER<\/p>\n
<\/p>\n
greenadexchange.com, 23456, RESELLER, AEC242<\/p>\n
<\/p>\n
A buyer receiving a bid request claiming to be\u00a0example.com\u00a0can verify if the exchange and SellerAccountID matches the authorized sellers listed in\u00a0example.com\/ads.txt\u00a0file.<\/p>\n
<\/p>\n
Refer to\u00a0IAB\u2019s How to Ads.txt\u00a0and\u00a0IAB Ads.txt Specification\u00a0documentation for more details.\u00a0<\/p>\n
How to Use Ads.txt<\/strong><\/span><\/p>\n <\/p>\n
Buying platforms (DSPs, Networks, etc.)\u00a0<\/strong>can crawl the ads.txt files to acquire the Authorized Digital Sellers list for every domain. This list informs the platform of the \u2018tuple\u2019 (a finite sequential list of elements) of information that provides an authorized way to buy a content owners true inventory. Additionally, ads.txt will tell the buyer if the PubID that they are buying the domain from is owned and operated by the publisher, or if it is an authorized seller.<\/p>\n <\/p>\n
Advertisers\u00a0<\/strong>that work with buying platforms that support ads.txt and that allow them to target Authorized Digital Sellers can be secure in their digital media expenditure, and can eliminate the problems associated with buying inventory from unauthorized and unknown counter-parties.<\/p>\n <\/p>\n
While the IAB Tech Lab is actively thinking about solutions to the below, ads.txt does not currently solve for:<\/p>\n
<\/p>\n
\n- Mobile Apps<\/li>\n
- Video Syndication\u00a0\u2022\u00a0Subdomains<\/li>\n<\/ul>\n
<\/p>\n
\u2022\u00a0Blind\/anonymous Inventory<\/p>\n
<\/p>\n
How to implement Ads.txt for Gamma<\/strong><\/span><\/p>\n <\/p>\n
Publishers can take the following steps in order to get assistance from Gamma in implementing their ads.txt files.<\/p>\n
<\/p>\n
\n\n\n| 1. Contact your Gamma account manager for a list of domains, Publisher Ids, and Types of Account<\/td>\n<\/tr>\n |
\n| relationship.Gamma is a TAG member and requiring implementation of our TAG ID also, although it is anoptional parameter. Gamma TAG ID is 31ac53fec2772a83.Publishers who own their inventory should have their engineering teams update \/ install ads.txt filefor all domains using the content provided.Authorized resellers will need to contact upstream publishers to have them update their ads.txt files.Ensure there are multiple lines in the ads.txt file in case of multiple types of relationship. Examplebelow.<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n <\/p>\n 6. Once updated publisher will send confirmation email to Gamma account manager. Example:<\/p>\n <\/p>\n gammassp.com, 1508400942, DIRECT, 31ac53fec2772a83\u00a0
gammassp.com, 1234567890, RESELLER, 31ac53fec2772a83<\/p>\n [\/et_pb_text][\/et_pb_column][\/et_pb_row][\/et_pb_section]<\/p>\n","protected":false},"excerpt":{"rendered":" [et_pb_section fb_built=”1″ fullwidth=”on” _builder_version=”3.29.3″][et_pb_fullwidth_header _builder_version=”3.29.3″ hover_enabled=”0″ admin_label=”Fullwidth Header” title=”ads.txt \u2013 Implementation Guide” background_color=”#0c71c3″][\/et_pb_fullwidth_header][\/et_pb_section][et_pb_section fb_built=”1″ _builder_version=”3.22″ fb_built=”1″ _i=”0″ _address=”0″][et_pb_row _builder_version=”3.25″ background_size=”initial” background_position=”top_left” background_repeat=”repeat” _i=”0″ _address=”0.0″][et_pb_column type=”4_4″ _builder_version=”3.25″ custom_padding=”|||” _i=”0″ _address=”0.0.0″ custom_padding__hover=”|||”][et_pb_text _builder_version=”3.27.4″ background_size=”initial” background_position=”top_left” background_repeat=”repeat” _i=”0″ _address=”0.0.0.0″] Introduction This document provides the details on\u00a0Authorized\u00a0Digital\u00a0Sellers transparency to restrict fraud by IAB Tech Lab and guidelines for updating […]<\/p>\n","protected":false},"author":1,"featured_media":0,"parent":0,"menu_order":0,"comment_status":"closed","ping_status":"closed","template":"","meta":{"_et_pb_use_builder":"on","_et_pb_old_content":"\n ads.txt \u2013 Implementation Guide<\/strong><\/p>\n\n\n\nIntroduction
<\/strong>This document provides the details on A<\/strong>uthorized D<\/strong>igital S<\/strong>ellers transparency to restrict fraud by<\/p>\n\n\n\nIAB Tech Lab and guidelines for updating the ads.txt file.<\/p>\n\n\n\n Ads.txt is an open standard and technical specification defining how a publisher can publicly declare their list of \u201cA<\/strong>uthorized D<\/strong>igital S<\/strong>ellers,\u201d in an \u201cads.txt\u201d on their site. It is a simple, flexible, and secure way for content owners and distributors to declare who is authorized to sell their inventory, improving transparency for programmatic buyers. The data required to populate the file is readily available in the OpenRTB protocol, making it simple to populate and target. Because publishers sell their inventory through a variety of sales channels, ads.txt supports the following types of supplier relationships:<\/p>\n\n\n\n- Domain owners who sell on exchanges through their own accounts.<\/li>
- Networks and sales houses who programmatically sell on behalf of domain owners.<\/li>
- Content syndication partnerships where multiple authorized sellers represent the same inventory.<\/li><\/ul>\n\n\n\n
How to Update Ads.txt<\/strong><\/p>\n\n\n\nAds.txt is a simple text file that publishers can host on the root domain of their website that includes information about approved seller relationships for their inventory. (It is similar in concept and hosting to a robots.txt file.)<\/p>\n\n\n\n The standard file format per IAB standard includes:<\/p>\n\n\n\n - Field #1 = Domain name of the advertising system<\/li>
- Field #2 = Publisher\u2019s Account ID<\/li>
- Field #3 = Type of Account Relationship<\/li>
- Field #4 = Certification Authority ID<\/li><\/ul>\n\n\n\n
Example: <\/strong>Example.com publishes ads.txt on their web server listing three exchanges as authorized to sell their inventory, including Example.com\u2019s seller account IDs within each of those exchanges.<\/p>\n\n\n\nhttp:\/\/example.com\/ads.txt:<\/a><\/p>\n\n\n\n#<SSP\/Exchange Domain>, <SellerAccountID>, <PaymentsType>, <TAGID> greenadexchange.com, 12345, DIRECT, AEC242
blueadexchange.com, 4536, DIRECT
silverssp.com, 9675, RESELLER<\/p>\n\n\n\n greenadexchange.com, 23456, RESELLER, AEC242<\/p>\n\n\n\n A buyer receiving a bid request claiming to be example.com can verify if the exchange and SellerAccountID matches the authorized sellers listed in example.com\/ads.txt file.<\/p>\n\n\n\n Refer to IAB\u2019s How to Ads.txt and IAB Ads.txt Specification documentation for more details. How to Use Ads.txt<\/strong><\/p>\n\n\n\nBuying platforms (DSPs, Networks, etc.) <\/strong>can crawl the ads.txt files to acquire the Authorized Digital Sellers list for every domain. This list informs the platform of the \u2018tuple\u2019 (a finite sequential list of elements) of information that provides an authorized way to buy a content owners true inventory. Additionally, ads.txt will tell the buyer if the PubID that they are buying the domain from is owned and operated by the publisher, or if it is an authorized seller.<\/p>\n\n\n\nAdvertisers <\/strong>that work with buying platforms that support ads.txt and that allow them to target Authorized Digital Sellers can be secure in their digital media expenditure, and can eliminate the problems associated with buying inventory from unauthorized and unknown counter-parties.<\/p>\n\n\n\nWhile the IAB Tech Lab is actively thinking about solutions to the below, ads.txt does not currently solve for:<\/p>\n\n\n\n - Mobile Apps<\/li>
- Video Syndication \u2022 Subdomains<\/li><\/ul>\n\n\n\n
\u2022 Blind\/anonymous Inventory<\/p>\n\n\n\n How to implement Ads.txt for Gamma<\/strong><\/p>\n\n\n\nPublishers can take the following steps in order to get assistance from Gamma in implementing their ads.txt files.<\/p>\n\n\n\n | 1. Contact your Gamma account manager for a list of domains, Publisher Ids, and Types of Account<\/td><\/tr> | | relationship.Gamma is a TAG member and requiring implementation of our TAG ID also, although it is anoptional parameter. Gamma TAG ID is 31ac53fec2772a83.Publishers who own their inventory should have their engineering teams update \/ install ads.txt filefor all domains using the content provided.Authorized resellers will need to contact upstream publishers to have them update their ads.txt files.Ensure there are multiple lines in the ads.txt file in case of multiple types of relationship. Examplebelow.<\/td><\/tr><\/tbody><\/table>\n\n\n\n 6. Once updated publisher will send confirmation email to Gamma account manager. Example:<\/p>\n\n\n\n gammassp.com, 1508400942, DIRECT, 31ac53fec2772a83
gammassp.com, 1234567890, RESELLER, 31ac53fec2772a83<\/p>\n","_et_gb_content_width":""},"_links":{"self":[{"href":"https:\/\/gammassp.com\/web\/wp-json\/wp\/v2\/pages\/732"}],"collection":[{"href":"https:\/\/gammassp.com\/web\/wp-json\/wp\/v2\/pages"}],"about":[{"href":"https:\/\/gammassp.com\/web\/wp-json\/wp\/v2\/types\/page"}],"author":[{"embeddable":true,"href":"https:\/\/gammassp.com\/web\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/gammassp.com\/web\/wp-json\/wp\/v2\/comments?post=732"}],"version-history":[{"count":4,"href":"https:\/\/gammassp.com\/web\/wp-json\/wp\/v2\/pages\/732\/revisions"}],"predecessor-version":[{"id":737,"href":"https:\/\/gammassp.com\/web\/wp-json\/wp\/v2\/pages\/732\/revisions\/737"}],"wp:attachment":[{"href":"https:\/\/gammassp.com\/web\/wp-json\/wp\/v2\/media?parent=732"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}} |
|