What is an Ad Space?
- Project Setup
- AATKit Initialisation
- Banner Integration
- Fullscreen Integration
- APP Open Integration
- Native Ads Integration
- Native Ads Integration - special ad network characteristics
- Promo Screen
- Disable App Transport Security (ATS)
- Advanced Features
- Rewarded Video
- Frequency Capping
- Header documentation
- Important Remarks
- AATKit's Size within your app
- What is an AdSpace?
- Network-specific Information
- Statistics Delegate
- Reports Delegate
- Listen to impression level information
- AATKit AdMob custom events adapter (>= 2.77.x)
- What is an Ad Space?
- Fullscreen Ads/Interstitials
- Native Ads
- What is the difference between an ad space and an impression?
- What is the difference between ad space and the request to an advertising network?
- What's the difference between an impression and an ad response from an advertising network?
- What's the difference between displaying an ad and in impression?
- Is it possible to see ad spaces per ad network?
An ad space represents the intention to display a new ad within an application. You can also call it an opportunity to show a new ad, since an intention requires an opportunity to show an ad. AddApptr is counting ad spaces for banner, interstitials, and native ads differently. Differently in the sense of technically capturing a developer's intention to show an ad. However, an ad space for banners, interstitials, and native ads has the same meaning.
The following describes what an ad space is, for each ad format. It includes a more technical description, as well as a non-technical description.
For banner we have to distinguish between using manual reloading and auto reloading. Since AddApptr has to adhere to ad network guidelines, loading a banner ad also requires displaying a banner ad. This means that there is no (technical) distinction between loading and displaying, since once a banner is successfully loaded it is has to be displayed right away. For comparison, this is different to interstitials, which can be loaded and then be displayed at a later point in time. Telling the AATKit to request (or load) a banner creates an ad space. This is due to the fact, that a banner is supposed to be displayed directly after it is received.
By using autoreload, the AATKit is told to create an ad space after a fixed time period. By default this period is 30 seconds, but can be longer, dependent on the client's setting. Choosing autoreload creates an ad space every 30 seconds. in the default scenario.
Once a developer calls the method
an ad space is created.
Since fullscreen ads can be (pre-)loaded and stored, they don’t need to be displayed right away, like banner ads. This allows for counting an ad space right when the fullscreen ad is supposed to be displayed. In order to display a fullscreen ad, a developer needs tell the AATKit to show an ad. As soon as a developer instructs the AATKit to display an interstitial, an ad space is counted. You can also say, by telling the AATKit to display an interstitial, a developer indicates that an opportunity to show an ad within his application is available.
When the method
Loading an interstitial does not contribute to counting an ad space for fullscreen ads.
For native ads, the scenario of ad space counting is very different to the other formats. It is possible to load multiple native ads without displaying them. This refers to storing them for a later display, also called caching. A developer also has full control over when native ads are displayed.
A native ad is a collection of assets. This collection is handed to a developer to assemble, in order to make the native ad look similar to the app itself. AddApptr does not keep control over this collection, and thus gives up control over detecting when the native ad (an amount of assets) is displayed. This means that AddApptr cannot automatically detect weather an ad space is created or not. Since loading does not imply displaying the native ad, telling the AATKit to show the native ad is also not required, ad space counting needs to be different. In order to count ad spaces correctly for native ads, a developer is required to actively communicate the intention to display a new native ad to the AATKit. Telling the AATKit that a new native ad is supposed to be displayed on influence the statistics of ad spaces, no behaviour is influenced.
Technically, an ad space is communicated to the AATKit by calling the following method:
Misc: If a developer does not communicate an ad space, AddApptr is not able to count ad spaces correctly. However since an ad space amount of zero doesn't really work in the AddApptr dashboard, unless no ads have ever been displayed, the AddApptr backend automatically sets the amount of ad spaces equal to the amount of impressions.
What is the difference between an ad space and an impression?
An impression follows and ad space. In other words, an intention to display and ad needs to precede it's actual display. An ad space can lead to an impression, in which case this is called a filled ad space. An ad space can also not lead to displaying an ad. In that case no advertising network was able to fulfill and ad request. This is called an unfilled ad space or a no-fill.
What is the difference between ad space and the request to an advertising network?
The intention to display an ad leads to one or more requests to one or more ad networks. These requests contain different information, like the network key which is used to request ad material. Such a request may or may not be filled successfully. The mediation makes sure that on an unsuccessful ad request another ad request is sent to a different (or the same) advertising network, in order to fill the preceding ad space. This sequence ensures that the number of ad spaces is always less then the number of requests.
What's the difference between an impression and an ad response from an advertising network?
An impression of an ad, can only happen if an ad network has responded with ad material. As an analogy, a letter being received would be a response, but opening it and folding it out is an impression. For some ad networks, a response is equal to an impression. However, if you consider that there is no guarantee that a received ad material can be displayed, mostly due to user interaction, this consideration is inaccurate.
What's the difference between displaying an ad and in impression?
They are the same thing.
Is it possible to see ad spaces per ad network?
No this is not possible. Ad spaces are not specific to ad networks. They are related to the AddApptr Mediation, which can lead to any ad network being displayed or even none. An ad space describes a relationship between the app and the AATKit itself.