Ad Scenes
1. Functions#
TradPlus supports the creation of multiple Ad Scenarios under one unit, which is used to differentiate the impression and click data under different Ad Scenarios, and helps developers to understand the Ad Scenario dimensions of the impression, click, and Ad Ready rate when arriving at the Ad Scenario.
2. Usage scenes#
If you want to analyze whether Ad impressions are maximized or not by using TradPlus funnel analysis reports, you need to call the “Enter Ad Scene” method exactly. Once the call is made, the TradPlus VisiM will automatically count two important metrics:
User's Ad Scene Reach Rate, i.e., number of users reaching the Ad Scene / number of users launching the app.
Ad Ready rate when reaching the ad scene.
If a unit contains several Ad Scenes, and the developer wants to know the data of Ad Scene dimensions (such as impression, clicks, etc.), he needs to create Ad Scenes in the backend -> App Management -> Ad Scene interface. And pass in the corresponding Ad Scene ID every time an Ad is impression.
If your game is in the sandbox category, you can differentiate between the Ad data of each developer through the Ad Scenarios feature.
3. Usage guides#
3.1 Instructions#
3.1.1 Data metrics#
a. Arrive at Ad Scene：App calls TradPlus SDK' interface of EntryAdScenario.
b. Impression ：Number of impressions recorded by TradPlus.
c. Click ：Ad clicks recorded by TradPlus. Note: Some ad networks may not provide click callbacks.
d. CTR ：Click / impression.
e. IMPs %: the number of impressions for the scenario / the total number of impressions for the Ad unit.
3.2 Add AD Scenes#
3.2.1 Preconditions#
Ad units have been added in [App Management].
3.2.2 Procedures#
1）Click【App Management】-【AD Scenes】-【Add AD Scenes】。
2）Fill in the Ad Scene Information
| Ad Scene Info | Instruction |
|---|---|
| APP | Apps created on TradPlus by developers need ad monetization. |
| Ad Units | Ad units created on TradPlus by developers. SDK gets ad config & loads ads through it. |
| Ad scene name（required） | Fill in the customized Ad Scene name. |
| Customized Ad Scene ID | a. If you select No, the Ad Scene ID will be automatically generated after the scene is successfully created and used for development calls； b. Select Yes to fill in the custom Ad Scene ID. |
| Status | Select [Enable]/[ Deactivate] Ad Scene |
| Note | / |
3）After confirming that the Ad Scene information is filled in correctly, click [ Confirm ] to save the Ad Scene information.
3.3 Edit Ad Scenarios#
Click the [Edit] on the right side of the Ad scene list to enter the edit page.
3.4 Call Ad Scenes#
After you add an Ad Scene in on TradPlus VisiM, you need to make a call in the code to use the Ad Scene.
You can find the instructions here：Ad scenes | TradPlus Knowledge Center
3.5 View and export Ad scene data#
1）You can view Ad Scene data on the Ad Scene List page.
2）Click the icon in the upper right corner of the report and select [Export] to export Ad scene data
4. Best Practices#
4.1. “ Enter the Ad Scene ” method#
It's usually a method to call into an ad scene when the app needs an Ad:
Android：entryAdScenario("sceneId")
iOS：entryAdScenario:@"Your Ad Scene ID"
If you need to distinguish the data of different Ad scenes, you need to generate Ad scene ID in the background-> App Management-> Ad scene interface; if you don't need to distinguish the data of different Ad scenes, you can directly pass the empty string for Ad scene ID.
The timing of calls for different Ad types is described below:
i. Rewarded video
The developer chooses the timing of the call accordingly, based on how the application handles the Ad viewing buttons
| Handling of Ad buttons | Timing of call |
|---|---|
| The app will gray out or hide the Ad buttons when it determines there are no Ads | Called when the user reaches the screen where the Ad button is located (see below) |
| Ad buttons are not grayed out or hidden by the app, users can always click on them. | Called when the user clicks on the Ad button |
ii. Interstitial
Call the “Enter Ad Scene” method when the ad trigger condition is met, for example:
Ad scenarios are called at the end of the cleanup if an interstitial ad pops up at the end of the cleanup;
Ad scenarios are pop-up interstitials that are called at the end of a game.
iii. Native Ads
Called when the user arrives at the screen where the Ad unit is located.
iv. Banners
If the app loads the Ad before the user arrives at the unit, it will be called when the user arrives at the screen where the Ad is located; if the app loads the Ad when the user arrives at the unit, it may not call the “Enter Ad Scene” method.
v. Splash
May not be called.
4.2 Calls to Impressions#
If you need to distinguish the impression data of different Ad scenes, you need to pass in the sceneID when you call the showad interface. SceneID is used to generate the Ad scene ID in the backend-> App Management-> Ad Scene Interface.
5. FAQs#
Q：What is the difference and connection between an Ad Scene and an Ad unit?#
A：
Difference: different definitions.
An Ad scene is a scene where an impression of an advertisement is displayed within the app, for example, such as an interstitial advertisement that pops up at the end of a game.
Ad units are the units for which TradPlus SDK requests ads.
Connection：
- One unit can correspond to multiple Ad scenes. For example, an incentive video unit corresponds to 3 scenarios: “Watch video to get props”, “Daily check-in” and “Level resurrection”.