In the App-Specific Configuration section, you can select the conversion returns to be sent to the <Mintegral> for this application.
I. Select the Partner
Login to Singular platform, click【ATTRIBUTION】 > 【Partner Configuration】 >【 Add a Partner 】> select【Mintegral】.
II. Select the app to set up and postback data
A. Edit the existing configuration
Hover over the app site you want to edit, and click the edit button on the right.
B. Add a new configuration:
- Click Add App Site.
- In the Configuration window that opens, select the App for which you want to configure settings/postbacks, and then select the App Site ( platform version ).
III. Conversion Postbacks
IV. Event Postbacks
A. Under Send in-app events to <Mintegral>, you have the following options:
Send the postbacks about all events that users trigger in your app. We recommend you select "All".
- We recommend you postback the event related to revenue:
- __iap__ ： Default event for Purchase in app.
- __ADMON_USER_LEVEL_REVENUE__: Default event for Ad revenue.
- It is also recommended that you postback some other Revenue-related events:
-
-
__SESSION__: Default event for Open App.
-
game_completed_50_levels: Customised event for game level.
-
V. Postback window
Please be aware that the default postback window for in-app events in Singular is currently set to 7 days, which only covers data within the first 6 days after user installation. This default setting may lead to incomplete revenue data for D7 and beyond. To ensure the completeness of the data for the ROAS model's learning, we strongly suggest adjusting the event postback window to the maximum period.
VI. Map your event on Mintegral Dashboard
After event data is sent, log in to Mintegral to define the events in the “Manage Event” section.
- Below is an example of the mapping between [Original Event Name] and [Mintegral Standard Event Name]:
| Original Event Meaning | Mintegral Standard Event Name |
| Total ad revenue of the app | Ad Revenue |
| Total in-app purchase revenue of the app | Purchase |
| User opens the app | Open App |
| User reaches XX level | Game Level |
| User registers an app account | Register |
| User logs into the app | Login App |
| User reaches XX level and accumulates LTV to XX amount | Key Action |
| User reaches the XX level and completes the XX task | Key Action |
| User completes the tutorial | Key Action |
| User adds a product to the shopping cart | Key Action |
| Other key action events | Key Action |
-
- Enter the "Manage Event" in your account to proceed with the settings
-
Input the corresponding product's package name, event name, and their corresponding Mintegral event mapping categories, select submit, and complete the setup.
-
*Tips: To improve the efficiency of using event data and accelerate model learning, we strongly recommend completing the relevant event mapping as soon as possible after posting back the data and paying attention to the accuracy of the event mapping.
-
|
For more information, please refer to the Singular official website guidelines： |