Google Ad Manager, AdMob Include Support For App-ads.txt, To Begin Blocking Unapproved Promotion Serving For Publishers This Month. 

Application publishers will likewise observe notification of mistakes in their document usage. 

New app-ads.txt tabs in the Google Ad Manager and AdMob interfaces will indicate mistakes and issues to address in publishers’ files. 

Google Ad Manager and AdMob, Google’s mobile advertisement network, presently support app-ads.txt, the counter promotion misrepresentation protocol for application publishers. The organization reported Tuesday that starting August 27, Google Ad Manager and AdMob will block advertisement serving of unauthorized in-application ad inventory in both platforms when publishers have app-ads.txt documents practised.

An augmentation of IAB Tech Lab’s ads.txt standard, app-ads.txt is intended to address the particular needs of applications conveyed through mobile and associated TV application stores. Publishers publish the content record posting the open exchanges that are approved to sell their stock to the root directory of their sites and link their application store postings to their sites. Programmatic purchasers would then be able to investigate the records to guarantee they are purchasing from approved dealers and not domains or applications set up to spoof publishers and take their promotion income.

Why we should mind

Google said in April that its DSP Display and Video 360 would quit purchasing unapproved in-application stock beginning in August. Given its market leadership position, Google’s help for app-ads.txt from both the purchase and sell sides will help propel the adoption of the standard by application publishers.

A week ago, Centro declared its DSP Basis would purchase stock from approved dealers recorded in app-ads.txt documents. In April, Tappx started offering free app-ads.txt record facilitating for application publishers that don’t have their sites. Around then, Tappx said less than 1% of applications had application-ads.txt set up accurately.

“We firmly urge you to make an application-ads.txt document and distribute it to the developer domain you have recorded in your App Store or Google Play store posting,” Google said in the announcement.” It will help avert unapproved, and domain spoofed application stock from harming your brand image and income. Publishers who don’t execute an app-ads.txt document will see no progressions to their advertisement serving, yet they won’t profit by these additional spoofing protections.

More on the news

  • Another app-ads.txt tab in the Google Ad Manager interface will demonstrate publishers the level of inquiries that have application-ads.txt posted and approved dealers recorded.
  • The dashboards in AdMob and Google Ad Manager additionally show blunders when the publisher ID or approved dealers are missing., with links to fix the issues. 
  • The application-ads.txt document incorporates the name of the advertisement network as the domain name, the publisher’s ID or property code.
About Martech Leader

You can get updated on the things going around Martech ecosystem with Martechleader. Find any sort of news on Martech,Martech events,Martech Conferences at your finger tips now.

Leave a Comment