|
Feature |
Manual |
Single Tag |
WebView |
|---|---|---|---|
|
Integrated CMP. |
|
|
|
|
Custom auctions in R89 Servers. |
|
|
|
|
All Formats supported. |
|
|
|
|
Remote Unit Configs. |
|
|
|
|
Remote Ad Places. |
|
|
|
|
Local Testing without R89 DB or Servers. |
|
|
|
When to use Single Tag Initialization
This Initialization provides a way that with minimal code you can remotely control where and how to show the inventory. You will have full remote control over App and Inventory configurations and also, with the addition of tags to your views, you will have full remote control over where you show the inventory.
This option is recommended under the following circumstances:
-
Easiest monetization setup, because all configurations for the Units are done in the Remote Server. No need for handling the display of the ads.
-
Disable and enable Inventory slots without updating the application.
-
Control the inventory configurations remotely over the web without updating the application.
-
Target your ads without updating the app.
-
And much more options: styles, positioning, change formats, etc.
Configurations that can be modified without requiring app updates:
-
App Targeting.
-
Inventory Targeting.
-
Inventory Size.
-
Inventory Content.
-
Where to show the ads, relative to the views tagged.
Go to Single Tag Implementation page.
When to use Manual Initialization
TL;DR This SDK configuration is designed for situations where the Single tag might not align with your ad presentation requirements, but you can still leverage the benefits of remote inventory configuration.
You can see an example in Demo apps.
Manual configuration means that you have remote control over General App and Inventory Configurations over the web or our tech support.
While you will still need to code for those units to be displayed, there is no requirement to set them up in the app code beforehand. This is because you have already accomplished this on the web or we have taken care of it on your behalf.
So you have control over where, when e a how ads appear in the application. This control extends to configuring, testing and targeting your ads without necessitating app updates.
This option is recommended under the following circumstances:
-
Still control manually the logic of showing the Inventory.
-
Easier Monetization setup, because all configurations for the Units are done in the Remote Server. You still need to handle the display of the ads.
-
Control the inventory configurations remotely over the web without updating the app.
-
Target your ads without Updating the app.
Configurations that can be modified without requiring app updates:
-
App Targeting.
-
Inventory Targeting.
-
Inventory Size.
-
Inventory Content.
Go to Manual Config Implementation page.
When to use WebView Initialization
If your application is a web-application you can use this method of initialization. We will create a channel linking our SDK to your current in-web monetization solutions (as long as it is either AdSense or our Header Tag). Also the SDK will handle CMP implementation and send the information to the webview so you get the same consent in both side complying with privacy policies.
With a web-apps we expect our users to already be monetizing the web part of the app, so you need to own the web and the app contents, but this does not stop you from placing other formats around the webview, or in other places of the app.
This option is recommended under the following circumstances:
- Web-app using Androids or iOS native Web Views.
- Web-app using Androids or iOS native javascript interfaces.
- Wanting to use Manual Configuration in a web-app
