{"id":739,"date":"2019-10-11T03:29:47","date_gmt":"2019-10-11T03:29:47","guid":{"rendered":"https:\/\/gammassp.com\/web\/?page_id=739"},"modified":"2019-10-11T03:57:08","modified_gmt":"2019-10-11T03:57:08","slug":"app-ads-txt","status":"publish","type":"page","link":"https:\/\/gammassp.com\/web\/app-ads-txt\/","title":{"rendered":"app-ads.txt"},"content":{"rendered":"

[et_pb_section fb_built=”1″ fullwidth=”on” _builder_version=”3.29.3″][et_pb_fullwidth_header _builder_version=”3.29.3″ title=”app-ads.txt – Implementation Guide” background_color=”#0c71c3″ hover_enabled=”0″][\/et_pb_fullwidth_header][\/et_pb_section][et_pb_section fb_built=”1″ _builder_version=”3.22″ _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″ width=”78.9%”][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″]<\/p>\n

Introduction<\/strong><\/span><\/p>\n

<\/p>\n

App-ads.txt<\/strong>\u00a0extends ads.txt functionality to include inventory from mobile apps and over-the-top (OTT) video. The new app-ads.txt specification relies on the publisher URL, available on app store HTML pages, as the centrally located, crawler-friendly, trusted source.<\/p>\n

<\/p>\n

Ads.txt<\/strong>\u00a0is an open standard and technical specification defining how a publisher can publicly declare their list of \u201cA<\/strong>uthorized\u00a0D<\/strong>igital\u00a0S<\/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.<\/p>\n

<\/p>\n

How app-ads.txt Works<\/strong><\/span><\/p>\n

<\/p>\n

The specification identifies four entities that play a vital role in enabling authorized digital seller validation on in-app inventory:<\/p>\n

<\/p>\n

\u2022 App stores
\u2022 App publishers
<\/span>\u2022 Sell-side platforms
<\/span>\u2022 Authorized seller verifiers<\/p>\n

<\/p>\n

App stores<\/strong>\u00a0enable mobile authorized seller specifications. They connect the app with its publisher\u2019s URL that hosts seller information. Specification requires the app stores to publish the app publisher\u2019s URL, bundle_id, and store_id as HTML <meta> tags within the <head> tag at the beginning of the HTML doc.<\/p>\n

<\/p>\n

App publishers<\/strong>\u00a0complete the following steps to enable seller authorization on their app inventory:<\/p>\n

<\/p>\n

1. Register the URL that hosts app-ads.txt file on the app store
2. Publish an app-ads.txt file with authorized seller information.<\/span><\/p>\n

<\/p>\n

The file format for mobile authorized seller information will be identical to that of web ads.txt. Each record will have an ad tech domain, publisher account ID, relationship\\account type and optional TAG ID.<\/p>\n

<\/p>\n

Please note that app inventory seller information must be published in a separate file entitled \u201capp- ads.txt.\u201d Therefore, the web seller information will be available in \u201cads.txt\u201d but independent of app seller information.<\/p>\n

<\/p>\n

Sell-side platforms<\/strong>\u00a0are required to include a store URL parameter on all bid requests. Only requests with valid store URL parameters are eligible for authorization.<\/p>\n

<\/p>\n

Authorized seller<\/strong>\u00a0verifiers must follow the below steps to verify authorization:<\/p>\n

<\/p>\n

\u2022 Identify the app store URL in the bid request
\u2022 Crawl the app store URL page for the publisher\u2019s URL, bundle_id and store_id
<\/span>\u2022 Translate the publisher URL to an app-ads.txt path
<\/span>\u2022 Crawl and interpret the app-ads.txt file for enforcement<\/span><\/p>\n

<\/p>\n

Mobile app-ads.txt specification ignores sub-domain directives, unlike web ads.txt file. Under web ads.txt specification, verifiers are expected to crawl the root domain and parse sub-domain directives to track sub-domains to specific authorized sellers.<\/p>\n

<\/p>\n

In-app environment verifiers must start at second level domains and then fall back to root domains only when there is a missing file. This special provision is made to handle app-specific authorized seller information.<\/p>\n

<\/p>\n

How to Implement app-ads.txt<\/strong><\/p>\n

<\/p>\n

App developers should follow these steps to adopt app-ads.txt for their apps.<\/p>\n

<\/p>\n

1. Create the app-ads.txt file. (The filename must be\u00a0app-ads.txt.<\/strong>)
2. Add entries too capture authorized seller information in the following file format:<\/span><\/p>\n

<\/p>\n\n\n\n\n\n\n\n
FIELD NO.\u00a0<\/strong><\/td>\nFIELD\u00a0<\/strong><\/td>\nDESCRIPTION\u00a0<\/strong><\/td>\nEXAMPLE\u00a0<\/strong><\/td>\n\u00a0STATUS\u00a0<\/strong><\/td>\n<\/tr>\n
1\u00a0<\/td>\nDomain name of the advertising system\u00a0<\/td>\nThe domain of the system\u00a0<\/td>\ngammassp.com\u00a0<\/td>\nMandatory\u00a0<\/td>\n<\/tr>\n
2\u00a0<\/td>\nPublisher Account ID\u00a0<\/td>\n1508400942\u00a0<\/td>\n1508400942\u00a0<\/td>\nMandatory\u00a0<\/td>\n<\/tr>\n
3\u00a0<\/td>\nType of Account Relationship\u00a0<\/td>\nCan be either DIRECT or RESELLER relationship\u00a0<\/td>\nDIRECT\u00a0<\/td>\nMandatory\u00a0<\/td>\n<\/tr>\n
4\u00a0<\/td>\nCertification Authority ID\u00a0<\/td>\nID that identifies the advertising system within a certification authority (mapped to entity in field #1)\u00a0<\/td>\n31ac53fec2772a83\u00a0<\/td>\nOptional\u00a0<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n

<\/p>\n

Example: ‘gammassp.com, 1508400942, DIRECT, 31ac53fec2772a83’<\/strong><\/p>\n

<\/p>\n

4. Post the “\/app-ads.txt” file on your root domain or subdomain as needed.
5. Provide the app-ads.txt page path in the developer URL attribute of the app store page.<\/span><\/p>\n

<\/p>\n

Only apps with eligible app-ads.txt path in the app store are eligible to participate in the authorized seller scheme.<\/em><\/p>\n

<\/p>\n

<\/p>\n

<\/strong><\/p>\n

<\/strong><\/p>\n

FAQ<\/strong><\/span><\/p>\n

<\/p>\n

Introduction<\/span>\u00a0<\/strong><\/p>\n

<\/p>\n

Last year saw massive growth in the adoption of the IAB Tech Lab\u2019s ads.txt standard. Designed to decrease the amount of premium desktop ad inventory that was either spoofed or otherwise heavily arbitraged, ads.txt was successfully embraced by buyers and suppliers, alike.\u00a0<\/p>\n

<\/p>\n

Today, the industry faces a similar challenge with in-app ad inventory; in-app inventory has an even higher risk for spoofing than desktop inventory due to the lack of visibility into how code is executed within an app. On March 13th, 2019, the IAB Tech Lab released the app-ads.txt standard to battle this rapidly growing threat to the integrity of the ecosystem.\u00a0<\/p>\n

<\/p>\n

What is app-ads.txt?\u00a0<\/strong><\/span><\/p>\n

<\/p>\n

Authorized Sellers for Apps (app-ads.txt) is the IAB Tech Lab\u2019s extension to the Authorized Digital Sellers (ads.txt) standard, originally designed for protecting web ad inventory from domain spoofing, arbitrage, and to provide buyers transparency into authorized ad selling. App-ads.txt extends the ads.txt functionality to meet the requirements for applications distributed through mobile app\u00a0<\/p>\n

<\/p>\n

stores, connected television app stores, or other application distribution channels. The specification establishes global standard for validating authorized app inventory sellers.\u00a0<\/p>\n

<\/p>\n

How is it different from ads.txt?\u00a0<\/strong><\/span><\/p>\n

<\/p>\n

The main difference between app-ads.txt and ads.txt is how the data crawlers find the file. With ads.txt files, the standard file location is the URL for the website offering up ad inventory for sale (e.g.\u00a0cnn.com\/ads.txt). However, given that apps are downloaded onto devices, there is no obvious location for the app-ads.txt file. The solution adopted by the IAB Tech Lab is for app developers to post their appads.txt file on their company website (e.g.\u00a0AppDeveloper.com\/app-ads.txt). Since app store URLs are an anchor reference for every app, an additional step is required. Crawlers first scrape the app-store page to retrieve the publisher domain URL, and then go to the publisher domain to access the app-ads.txt file.\u00a0<\/p>\n

<\/p>\n

What do I need to provide to my app developers?\u00a0<\/strong><\/span><\/p>\n

<\/p>\n

The IAB Tech Lab standard for app-ads.txt entries is the same for ads.txt, consisting of four components:<\/p>\n

<\/p>\n

    \n
  1. Exchange URL:\u00a0<\/strong>gammassp.com\u00a0<\/li>\n
  2. AccountID:\u00a0<\/strong>This is the Gamma Account ID for your account(s) which will monetize any ad inventory from the app.\u00a0<\/li>\n
  3. Seller Type:\u00a0<\/strong>Either DIRECT (single hop to DSP: app -> Gamma -> DSP) or RESELLER (two hops to DSP: app -> publisher -> Gamma -> DSP)\u00a0<\/li>\n<\/ol>\n

    <\/p>\n

    \u2022\u00a0Note: unless the app in question is owned and operated by the Gamma account holder(e.g. Turner Broadcasting would list DIRECT if selling CNN app inventory), RESELLER should be used.\u00a0<\/p>\n

    <\/p>\n

    4.\u00a0Gamma TAG ID:\u00a0<\/strong>31ac53fec2772a83<\/p>\n

    <\/p>\n

      \n
    1. Each part must be included on one line, with each part separated by a comma and a space. All you need to do is substitute the fictional Account ID below with your own Account ID.\u00a0<\/li>\n
    2. Direct Example:\u00a0gammassp.com, 1508400942, DIRECT, 5d62403b186f2ace\u00a0<\/li>\n
    3. Reseller Example:\u00a0gammassp.com, 1508400942, RESELLER, 5d62403b186f2ace\u00a0<\/li>\n<\/ol>\n

      <\/p>\n

      What is Gamma\u2019s policy on app-ads.txt?\u00a0<\/strong><\/span><\/p>\n

      <\/p>\n

      Gamma will allow monetization only of authorized or undeclared inventory.\u00a0<\/p>\n

      <\/p>\n\n\n\n\n
      \u2022\u00a0Authorized:\u00a0<\/strong>In the case an app has published an app-ads.txt file, you must have the appropriately\u00a0<\/td>\n<\/tr>\n
      configured entry included on the file to monetize.
      \u2022\u00a0Undeclared:\u00a0<\/strong>For apps with no app-ads.txt file posted, monetization will continue.\u00a0<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n

      <\/p>\n

      My App Developer has multiple apps, and wants to post app- ads.txt files for each, but only has a single developer URL. How is this managed?\u00a0<\/strong><\/p>\n

      <\/p>\n

      Developers that want to authorize different sellers for each app must rely on sub-domains.
      App dedicated sub-domains should be made available in developer URL section of app store page. As an example, gameloft can set up different sellers for Ice Age Adventures and Brothers in Arms\u00ae 3 by updating their app store publisher pages to have subdomain structure. The Ice Age Adventures app can have \u2018iceageadventures.gameloft.com\u2019 and Brothers in Arms\u00ae 3 app can have \u2018brothersinarms3.gameloft.com\u2019.\u00a0<\/p>\n

      <\/p>\n

      Verifier will go to\u00a0iceageadventures.gameloft.com\/app-ads.txt\u00a0to retrieve authorized seller information for Ice Age Adventures inventory and will go to\u00a0brothersinarms3.gameloft.com\/app- ads.txt\u00a0to do the same for Brothers in Arms\u00ae 3 inventory\u00a0<\/p>\n

      <\/p>\n

      Many of the apps I monetize don\u2019t see the value in adding app-ads.txt or don\u2019t understand
      it. Gamma is in the early stages of planning education and evangelism activities targeting app developers to help them in the following ways:\u00a0<\/p>\n

      <\/p>\n

        \n
      • Educate app developers why it\u2019s to their advantage to participate in app-ads.txt\u00a0<\/li>\n
      • Provide resources to help them set up and manage their app-ads.txt file\u00a0<\/li>\n
      • Give app developers tips to avoid the scams and schemes with ads.txt\u00a0<\/li>\n<\/ul>\n

        <\/p>\n\n\n\n
        Still have questions? Please reach out to your Gamma Account Manager.\u00a0<\/strong><\/td>\n<\/tr>\n<\/tbody>\n<\/table>\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″ title=”app-ads.txt – Implementation Guide” background_color=”#0c71c3″ hover_enabled=”0″][\/et_pb_fullwidth_header][\/et_pb_section][et_pb_section fb_built=”1″ _builder_version=”3.22″ _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″ width=”78.9%”][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 App-ads.txt\u00a0extends ads.txt functionality to include inventory from mobile apps and over-the-top (OTT) video. The new app-ads.txt specification relies on the […]<\/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

        Introduction<\/strong><\/p>\n\n\n\n

        App-ads.txt<\/strong> extends ads.txt functionality to include inventory from mobile apps and over-the-top (OTT) video. The new app-ads.txt specification relies on the publisher URL, available on app store HTML pages, as the centrally located, crawler-friendly, trusted source.<\/p>\n\n\n\n

        Ads.txt<\/strong> 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.<\/p>\n\n\n\n

        How app-ads.txt Works<\/strong><\/p>\n\n\n\n

        The specification identifies four entities that play a vital role in enabling authorized digital seller validation on in-app inventory:<\/p>\n\n\n\n

        \u2022 App stores<\/p>\n\n\n\n

        \u2022 App publishers<\/p>\n\n\n\n

        \u2022 Sell-side platforms<\/p>\n\n\n\n

        \u2022 Authorized seller verifiers<\/p>\n\n\n\n

        App stores<\/strong> enable mobile authorized seller specifications. They connect the app with its publisher\u2019s URL that hosts seller information. Specification requires the app stores to publish the app publisher\u2019s URL, bundle_id, and store_id as HTML <meta> tags within the <head> tag at the beginning of the HTML doc.<\/p>\n\n\n\n

        App publishers<\/strong> complete the following steps to enable seller authorization on their app inventory:<\/p>\n\n\n\n

        1. Register the URL that hosts app-ads.txt file on the app store<\/p>\n\n\n\n

        2. Publish an app-ads.txt file with authorized seller information.<\/p>\n\n\n\n

        The file format for mobile authorized seller information will be identical to that of web ads.txt. Each record will have an ad tech domain, publisher account ID, relationship\\account type and optional TAG ID.<\/p>\n\n\n\n

        Please note that app inventory seller information must be published in a separate file entitled \u201capp- ads.txt.\u201d Therefore, the web seller information will be available in \u201cads.txt\u201d but independent of app seller information.<\/p>\n\n\n\n

        Sell-side platforms<\/strong> are required to include a store URL parameter on all bid requests. Only requests with valid store URL parameters are eligible for authorization.<\/p>\n\n\n\n

        Authorized seller<\/strong> verifiers must follow the below steps to verify authorization:<\/p>\n\n\n\n

        \u2022 Identify the app store URL in the bid request<\/p>\n\n\n\n

        \u2022 Crawl the app store URL page for the publisher\u2019s URL, bundle_id and store_id<\/p>\n\n\n\n

        \u2022 Translate the publisher URL to an app-ads.txt path<\/p>\n\n\n\n

        \u2022 Crawl and interpret the app-ads.txt file for enforcement<\/p>\n\n\n\n

        Mobile app-ads.txt specification ignores sub-domain directives, unlike web ads.txt file. Under web ads.txt specification, verifiers are expected to crawl the root domain and parse sub-domain directives to track sub-domains to specific authorized sellers.<\/p>\n\n\n\n

        In-app environment verifiers must start at second level domains and then fall back to root domains only when there is a missing file. This special provision is made to handle app-specific authorized seller information.<\/p>\n\n\n\n

        How to Implement app-ads.txt<\/strong><\/p>\n\n\n\n

        App developers should follow these steps to adopt app-ads.txt for their apps.<\/p>\n\n\n\n

        1. Create the app-ads.txt file. (The filename must be app-ads.txt.<\/strong>)<\/p>\n\n\n\n

        2. Add entries too capture authorized seller information in the following file format:<\/p>\n\n\n\n
        FIELD NO. <\/strong><\/td>FIELD <\/strong><\/td>DESCRIPTION <\/strong><\/td>EXAMPLE <\/strong><\/td> STATUS <\/strong><\/td><\/tr>
        1 <\/td>Domain name of the advertising system <\/td>The domain of the system <\/td>gammassp.com <\/td>Mandatory <\/td><\/tr>
        2 <\/td>Publisher Account ID <\/td>1508400942 <\/td>1508400942 <\/td>Mandatory <\/td><\/tr>
        3 <\/td>Type of Account Relationship <\/td>Can be either DIRECT or RESELLER relationship <\/td>DIRECT <\/td>Mandatory <\/td><\/tr>
        4 <\/td>Certification Authority ID <\/td>ID that identifies the advertising system within a certification authority (mapped to entity in field #1) <\/td>31ac53fec2772a83 <\/td>Optional <\/td><\/tr><\/tbody><\/table>\n\n\n\n

        Example: 'gammassp.com, 1508400942, DIRECT, 31ac53fec2772a83'<\/strong><\/p>\n\n\n\n

        4. Post the \"\/app-ads.txt\" file on your root domain or subdomain as needed.<\/p>\n\n\n\n

        5. Provide the app-ads.txt page path in the developer URL attribute of the app store page.<\/p>\n\n\n\n

        Only apps with eligible app-ads.txt path in the app store are eligible to participate in the authorized seller scheme.<\/p>\n\n\n\n

        \n\n\n\n

        FAQ<\/strong><\/p>\n\n\n\n

        Introduction <\/strong><\/p>\n\n\n\n

        Last year saw massive growth in the adoption of the IAB Tech Lab\u2019s ads.txt standard. Designed to decrease the amount of premium desktop ad inventory that was either spoofed or otherwise heavily arbitraged, ads.txt was successfully embraced by buyers and suppliers, alike. <\/p>\n\n\n\n

        Today, the industry faces a similar challenge with in-app ad inventory; in-app inventory has an even higher risk for spoofing than desktop inventory due to the lack of visibility into how code is executed within an app. On March 13th, 2019, the IAB Tech Lab released the app-ads.txt standard to battle this rapidly growing threat to the integrity of the ecosystem. <\/p>\n\n\n\n

        What is app-ads.txt? <\/strong><\/p>\n\n\n\n

        Authorized Sellers for Apps (app-ads.txt) is the IAB Tech Lab\u2019s extension to the Authorized Digital Sellers (ads.txt) standard, originally designed for protecting web ad inventory from domain spoofing, arbitrage, and to provide buyers transparency into authorized ad selling. App-ads.txt extends the ads.txt functionality to meet the requirements for applications distributed through mobile app <\/p>\n\n\n\n

        stores, connected television app stores, or other application distribution channels. The specification establishes global standard for validating authorized app inventory sellers. <\/p>\n\n\n\n

        How is it different from ads.txt? <\/strong><\/p>\n\n\n\n

        The main difference between app-ads.txt and ads.txt is how the data crawlers find the file. With ads.txt files, the standard file location is the URL for the website offering up ad inventory for sale (e.g. cnn.com\/ads.txt). However, given that apps are downloaded onto devices, there is no obvious location for the app-ads.txt file. The solution adopted by the IAB Tech Lab is for app developers to post their appads.txt file on their company website (e.g. AppDeveloper.com\/app-ads.txt). Since app store URLs are an anchor reference for every app, an additional step is required. Crawlers first scrape the app-store page to retrieve the publisher domain URL, and then go to the publisher domain to access the app-ads.txt file. <\/p>\n\n\n\n

        What do I need to provide to my app developers? <\/strong><\/p>\n\n\n\n

        The IAB Tech Lab standard for app-ads.txt entries is the same for ads.txt, consisting of four components:<\/p>\n\n\n\n

        1. Exchange URL: <\/strong>gammassp.com <\/li>
        2. AccountID: <\/strong>This is the Gamma Account ID for your account(s) which will monetize any ad inventory from the app. <\/li>
        3. Seller Type: <\/strong>Either DIRECT (single hop to DSP: app -> Gamma -> DSP) or RESELLER (two hops to DSP: app -> publisher -> Gamma -> DSP) <\/li><\/ol>\n\n\n\n

          \u2022 Note: unless the app in question is owned and operated by the Gamma account holder(e.g. Turner Broadcasting would list DIRECT if selling CNN app inventory), RESELLER should be used. <\/p>\n\n\n\n

          4. Gamma TAG ID: <\/strong>31ac53fec2772a83<\/p>\n\n\n\n

          1. Each part must be included on one line, with each part separated by a comma and a space. All you need to do is substitute the fictional Account ID below with your own Account ID. <\/li>
          2. Direct Example: gammassp.com, 1508400942, DIRECT, 5d62403b186f2ace <\/li>
          3. Reseller Example: gammassp.com, 1508400942, RESELLER, 5d62403b186f2ace <\/li><\/ol>\n\n\n\n

            What is Gamma\u2019s policy on app-ads.txt? <\/strong><\/p>\n\n\n\n

            Gamma will allow monetization only of authorized or undeclared inventory. <\/p>\n\n\n\n
            \u2022 Authorized: <\/strong>In the case an app has published an app-ads.txt file, you must have the appropriately <\/td><\/tr>
            configured entry included on the file to monetize.
            \u2022 Undeclared: <\/strong>For apps with no app-ads.txt file posted, monetization will continue. <\/td><\/tr><\/tbody><\/table>\n\n\n\n

            My App Developer has multiple apps, and wants to post app- ads.txt files for each, but only has a single developer URL. How is this managed? <\/strong><\/p>\n\n\n\n

            Developers that want to authorize different sellers for each app must rely on sub-domains.
            App dedicated sub-domains should be made available in developer URL section of app store page. As an example, gameloft can set up different sellers for Ice Age Adventures and Brothers in Arms\u00ae 3 by updating their app store publisher pages to have subdomain structure. The Ice Age Adventures app can have \u2018iceageadventures.gameloft.com\u2019 and Brothers in Arms\u00ae 3 app can have \u2018brothersinarms3.gameloft.com\u2019. <\/p>\n\n\n\n

            Verifier will go to iceageadventures.gameloft.com\/app-ads.txt to retrieve authorized seller information for Ice Age Adventures inventory and will go to brothersinarms3.gameloft.com\/app- ads.txt to do the same for Brothers in Arms\u00ae 3 inventory <\/p>\n\n\n\n

            Many of the apps I monetize don\u2019t see the value in adding app-ads.txt or don\u2019t understand
            it. Gamma is in the early stages of planning education and evangelism activities targeting app developers to help them in the following ways: <\/p>\n\n\n\n

            • Educate app developers why it\u2019s to their advantage to participate in app-ads.txt <\/li>
            • Provide resources to help them set up and manage their app-ads.txt file <\/li>
            • Give app developers tips to avoid the scams and schemes with ads.txt <\/li><\/ul>\n\n\n\n
              Still have questions? Please reach out to your Gamma Account Manager. <\/strong><\/td><\/tr><\/tbody><\/table>\n","_et_gb_content_width":""},"_links":{"self":[{"href":"https:\/\/gammassp.com\/web\/wp-json\/wp\/v2\/pages\/739"}],"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=739"}],"version-history":[{"count":10,"href":"https:\/\/gammassp.com\/web\/wp-json\/wp\/v2\/pages\/739\/revisions"}],"predecessor-version":[{"id":752,"href":"https:\/\/gammassp.com\/web\/wp-json\/wp\/v2\/pages\/739\/revisions\/752"}],"wp:attachment":[{"href":"https:\/\/gammassp.com\/web\/wp-json\/wp\/v2\/media?parent=739"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}