T
Tora
Delta
¡Usuario con pocos negocios! ¡Utiliza siempre saldo de Forobeta!
All Audience Network publishers are required to make implementation updates by November 1 to ensure uninterrupted ad delivery. Learn more:
Today, we're announcing a series of implementation upgrades we're requiring all publishers and developers using Audience Network to make by November 1, 2017 to ensure uninterrupted ad delivery. These upgrades are designed to help maximize performance and improve stability for all publishers on the Audience Network. For new apps, these requirements will be the default starting line to ensure publishers properly implement Audience Network at launch.
Required Implementation Upgrades:
Upgrade to SDK 4.23 or Above: Every bundle sending ad requests to Audience Network needs to be using at least SDK version 4.23 for iOS and Android. This SDK version contains a number of bug fixes, stability improvements, and performance upgrades. Please update to SDK 4.23 for iOS, Android, and 4.22 for Unity.
Only Include 1 iOS and 1 Android Bundle per Audience Network App ID: Each Publisher can have a maximum of 1 iOS and 1 Android bundle package per App ID. Please ensure that the same bundle is not in more than 1 App ID. If you have multiple bundles on a single App ID, you will need to move one of the bundles to a new App ID. Full instructions on how to do this will be provided in the Audience Network dashboard beginning June 22nd.
Cache Ads for 60 Minutes or Less: You should request an ad right before showing it to the user. This will help ensure delivery of the highest performing ad for the user. Any ads shown after 60 minutes will not be considered for revenue generation purposes.
a. Also, if you want to log a new impression and/or user engagement event (i.e. click, view, install, etc), please make a new request each time. While the initial ad can be shown to the user multiple times, revenue will only be earned for the initial impression and/or user engagement event. For example, if a user clicks on the same ad twice, only the first click will generate revenue.
Organize Placement IDs Into Ad Spaces: Ad Spaces are a new way for publishers to arrange and group their placements into specific ad experiences to enable better reporting, analytics, and understanding of their business. This new feature will be released to all publishers starting June 22nd via the Audience Network dashboard.
Use a Single Placement ID to Request Ads For a Single Format Type: Only request ads for the single format type that corresponds to the placement ID. For example, if you have a placement that is used for “Interstitial,” do not also use that placement ID to request ads for “Native” or “Banner” ads.
Timeline to Make Changes:
We understand that it takes time to migrate people to a new version of your app, so we want to provide plenty of time to make the upgrades. All publishers have until November 1st to make the changes, and move people to your new version of the app.
Effective November 1st, we will stop delivery to old versions of apps that are not up to date with our minimum implementation requirements.
When to Start The Upgrade Process:
All the required upgrades will be available to implement starting June 22nd. We highly suggest shipping a single updated build of your app with all required elements included shortly after this date to start the migration process.
Today, we're announcing a series of implementation upgrades we're requiring all publishers and developers using Audience Network to make by November 1, 2017 to ensure uninterrupted ad delivery. These upgrades are designed to help maximize performance and improve stability for all publishers on the Audience Network. For new apps, these requirements will be the default starting line to ensure publishers properly implement Audience Network at launch.
Required Implementation Upgrades:
Upgrade to SDK 4.23 or Above: Every bundle sending ad requests to Audience Network needs to be using at least SDK version 4.23 for iOS and Android. This SDK version contains a number of bug fixes, stability improvements, and performance upgrades. Please update to SDK 4.23 for iOS, Android, and 4.22 for Unity.
Only Include 1 iOS and 1 Android Bundle per Audience Network App ID: Each Publisher can have a maximum of 1 iOS and 1 Android bundle package per App ID. Please ensure that the same bundle is not in more than 1 App ID. If you have multiple bundles on a single App ID, you will need to move one of the bundles to a new App ID. Full instructions on how to do this will be provided in the Audience Network dashboard beginning June 22nd.
Cache Ads for 60 Minutes or Less: You should request an ad right before showing it to the user. This will help ensure delivery of the highest performing ad for the user. Any ads shown after 60 minutes will not be considered for revenue generation purposes.
a. Also, if you want to log a new impression and/or user engagement event (i.e. click, view, install, etc), please make a new request each time. While the initial ad can be shown to the user multiple times, revenue will only be earned for the initial impression and/or user engagement event. For example, if a user clicks on the same ad twice, only the first click will generate revenue.
Organize Placement IDs Into Ad Spaces: Ad Spaces are a new way for publishers to arrange and group their placements into specific ad experiences to enable better reporting, analytics, and understanding of their business. This new feature will be released to all publishers starting June 22nd via the Audience Network dashboard.
Use a Single Placement ID to Request Ads For a Single Format Type: Only request ads for the single format type that corresponds to the placement ID. For example, if you have a placement that is used for “Interstitial,” do not also use that placement ID to request ads for “Native” or “Banner” ads.
Timeline to Make Changes:
We understand that it takes time to migrate people to a new version of your app, so we want to provide plenty of time to make the upgrades. All publishers have until November 1st to make the changes, and move people to your new version of the app.
Effective November 1st, we will stop delivery to old versions of apps that are not up to date with our minimum implementation requirements.
When to Start The Upgrade Process:
All the required upgrades will be available to implement starting June 22nd. We highly suggest shipping a single updated build of your app with all required elements included shortly after this date to start the migration process.
