✍XMP supports receiving customer data via Postback, which helps you to:
- View relevant data in real-time, including ROI, LTV, ROAS, retention, and more.
- Integrate attribution data and ad data into a unified report.
XMP Postback Address
XMP Postback address: https://xmp-postback.mobvista.com/s2s/postback
The user sends activation information back to the XMP Postback address, Get method requests
Parameter Settings
The parameters to be returned are as follows:
parameters | type | required | description |
channel | string | Yes | channel source, see enumerated values in the table below, please pass the values according to the specification or the data will not be matched |
campaign_id | string | Yes | campaign id |
adset_id | string | Yes | adset id |
ad_id | string | Yes | ad id |
country | string | Yes | country code, two uppercase letters, e.g., CN, US If you can't determine the region, pass an empty space |
subsource_id | string | No | subsource id |
activity_kind | string | Yes |
The 'activity_kind' field is used to record the type of postback event. Postback event types are as follow: Installation: install In-app events: in-app-event In-app event aggregated data: in-app-event-agg |
event_name | string | No | event name |
event_count | int | No | event count |
event_value | numeric | No | event value, up to 6 decimal |
event_unique_users | int | No | event users |
event_revenue_usd | numeric | No | us dollar amount of income from the event, up to 6 decimals |
event_time | int | Yes | second timestamp of when the event occurred, e.g. 1687881600 |
active_time | int | Yes | the seconds timestamp of the attribution time, which attributes the event to the user's activation time, must be within the last 90 days, for example, 1687881600, this field will not match data if not passed |
timezone | string | No | data timezone, see enumerated values in the following table |
request_id | string | No | Serves as a unique identifier for each piece of data, used for deduplication of data, with only data received in the last 14 days being deduplicated. This ID is generated by the requestor and must be unique. XMP will deduplicate based on the request_id, selecting the most recently received record before aggregating the data. If it is not provided, then XMP will directly aggregate the data. |
app_id | string | Yes | iOS format: starts with id, e.g. id123456789; Android format: e.g. com.app.game |
idfa | string | No | iOS device ID |
idfa_md5 | string | No | iOS device ID-md5 |
idfv | string | No | iOS device ID |
gaid | string | No | Android device ID |
oaid | string | No | Android device ID |
oaid_md5 | string | No | Android device ID-md5 |
android_id | string | No | Android device ID |
android_id_md5 | string | No | Android device ID-md5 |
imei | string | No | device ID |
mac | string | No | device ID |
ip | string | No | IP address at the time of activation |
customer_user_id | string | No | customized user id |
customer_order_id | string | No | customize order id |
Channel Source
channel | value |
Organic | organic |
TikTok | tiktok |
Kwai | kwai |
Huawei Global | huawei_global |
Apple Search Ads | apple |
Mintegral | mintegral |
Applovin | applovin |
Unity | unity |
ironSource | ironsource |
Vungle | vungle |
Time Zone
time zone | value | time zone | value |
0 time zone | UTC+0 | - | - |
+1 time zone | UTC+1 | -1 time zone | UTC-1 |
+2 time zone | UTC+2 | -2 time zone | UTC-2 |
+3 time zone | UTC+3 | -3 time zone | UTC-3 |
+4 time zone | UTC+4 | -4 time zone | UTC-4 |
+5 time zone | UTC+5 | -5 time zone | UTC-5 |
+6 time zone | UTC+6 | -6 time zone | UTC-6 |
+7 time zone | UTC+7 | -7 time zone | UTC-7 |
+8 time zone | UTC+8 | -8 time zone | UTC-8 |
+9 time zone | UTC+9 | -9 time zone | UTC-9 |
+10 time zone | UTC+10 | -10 time zone | UTC-10 |
+11 time zone | UTC+11 | -11 time zone | UTC-11 |
+12 time zone | UTC+12 | -12 time zone | UTC-12 |
Page Configuration
I. Authorized Platforms
1. Add a self-built attribution account in Administration > Platform Management > Add Platform.
2. Select Factorization Platform > Self-created Factorization and enter the account name.
II. Binding applications
1. Go to the Management > Platform Management > Application Binding page.
2. Click [Select Apps], in the pop-up dialog box, select one or more apps to be bound, binding platform select Self-built attribution, select the Self-built attribution account you need to bind, for Android apps, enter the package name of the app, and for iOS apps, enter the store ID, e.g. id387683439; click OK to submit.
III. Incident management
👇If you don't complete this step, you won't be able to view Roas, user revenue, retention, and other related metrics.
1. Go to Administration > Platform Management > Application Binding page, which supports single or batch management of customized events, as shown in the figure below Click the function portal of Event Management
2. Fill in the name of the event for which the self-attribution statistic is Revenue and Retention.
View Data
1. After completing the above steps, the data can be viewed in 1~2 hours
2. Where to view the data: Promotion / Reports / Traffic etc. > Custom Columns > S2S
Description
1、For the timeliness of data submission, it is recommended to report data to XMP side in real time.
2、For data integrity, it is recommended to retry up to 2 times in a minute after a failed report.
3、The latest report data of the day is updated every 3 hours.
4、This is a premium paid feature, please contact your business/operation manager before using it.