Mintegral integration plan
Note that data generated by third-party data integration counts toward the cluster's data consumption
Summary
Interface overview
| Interface | Type | Granularity | Attribution | Cost | Revenue | Impressions | Clicks | Conversions |
|---|---|---|---|---|---|---|---|---|
| Ad performance report (advanced) | API | Aggregated metrics | ✅ | ✅ | ✅ | ✅ |
The AE system currently supports connecting Mintegral ad campaign data. Through the ad performance report, aggregated metric data such as clicks, impressions, installs, and cost can be sent back
Integration process
The process for integrating Mintegral ad campaign data is as follows:
- Log in to the advertiser platform and get the Access Key and API Key
- Log in to the AE backend, go to the Third-party Integration module, add a Mintegral integration plan, and complete the related configuration
- Check whether the AE system receives the data successfully, and build reports
1. Get the authorization information
Before connecting data, log in to the advertiser platform and click Account Management > Basic Information in the navigation bar to get your Access Key and API Key.
2. Plan configuration
After you get the authorization information from the Mintegral backend, you can log in to the AE system and configure the new plan in the Third-party Integration module. The image below shows the Mintegral configuration page. Follow this section to create the plan:
2.1 Authorization information configuration
Click the Configure authorization information button under Authorization Information and enter the information you obtained in the previous step in the pop-up:
2.2 Sync Schedule
In the Sync Schedule module, you can set the policy for the AE system to pull Mintegral data on a schedule. You can choose to pull data for a period of time at a specific time every day. Because pulled data also counts toward the data volume, avoid pulling data for overly long periods on a schedule
2.3 Receive Settings
You can control whether the data is written as events. If you turn this off, the data is not written to the event table, so do not turn off this setting.
2.4 Configuration
Finally, in the Configuration module, you can control the detailed settings of data pulling, including the time aggregation granularity of the data, the metric fields and dimensions to pull, and the event name after ingestion.
The content of the configuration is a JSON, which you can customize as follows:
| Module | Name | Description |
|---|---|---|
| sink_event | event_name | Event name after ingestion; customizable; string type. |
| source | time_granularity | Time granularity of data pulling. Options:
|
| group_by | Grouping dimensions in the data; list type; customizable | |
| transfer | double_columns | Metrics in the data; list type. These fields are ingested as numeric types when the data is received, and the other fields are ingested as strings (or time). We don't recommend changing it |
- Analysis granularity
The following are the analysis dimensions supported by the ad performance report and the dimensions pulled by default. Note that some fields aren't supported at hourly granularity. To change them, enter the dimension names in source.group_by:
| Dimension | Grouping field | Description and notes | Default |
|---|---|---|---|
Offer | Offer ID | Ad unit ID | Yes |
| Offer Name | Ad unit name | Yes | |
| Offer UUID | Ad unit name generated automatically by the system | Yes | |
| Campaign | Campaign ID | Ad (campaign) ID | Yes |
| Creative | Creative ID | Creative ID. Doesn't support hourly granularity and is incompatible with the Sub dimension | Yes |
| Creative Name | Creative name. Doesn't support hourly granularity and is incompatible with the Sub dimension | Yes | |
| AdType | Ad Type | Ad type | Yes |
| Location | Location | Country where the ad is delivered | Yes |
| Currency | Currency | Yes | |
| Sub | Sub ID | Incompatible with the Creative dimension |
2.5 Data ingestion rules
- The date or timestamp (hour) field in the data, that is, the aggregation time of the data, is used as the event's #event_time
- The event name is mintegral_performance_report
- All other fields are ingested
The following are the dimension and metric fields supported by the ad performance report. Dimension fields are included in the data only when the corresponding analysis granularity is selected:
| Field | Description | Remarks |
|---|---|---|
| offer_id | Ad unit ID | |
| offer_name | Ad unit name | |
| offer_uuid | Ad unit name generated automatically by the system | |
| campaign_id | Ad (campaign) ID | |
| campaign_name | Ad name | Derived from campaign_id |
| creative_id | Asset ID | Unavailable in hourly reports |
| creative_name | Creative name | Unavailable in hourly reports |
| product_name | Product name | Derived from campaign_id |
| package_name | Product package name | Derived from campaign_id |
| platform | App platform | Derived from campaign_id |
| sub_id | Sub ID | |
| ad_type | Ad type | |
| click | Total clicks | |
| conversion | Conversions | |
| cpc | CPC | |
| ctr | CTR | |
| currency | Currency. The default is USD | |
| cvr | CVR | |
| ecpm | eCPM | |
| impression | Total impressions | |
| location | Country where the ad is delivered | |
| spend | Total spend |
2.6 Standardized fields
The AE system standardizes some fields in Mintegral data:
| Original field | Standardized field | Remarks |
|---|---|---|
| campaign_id | te_ads_object.campaign_id | Ad (campaign) ID |
| campaign_name | te_ads_object.campaign_name | Ad name |
| offer_id | te_ads_object.ad_group_id | Ad unit ID |
| offer_name | te_ads_object.ad_group_name | Ad unit name |
| creative_id | te_ads_object.ad_id | Asset ID |
| creative_name | te_ads_object.ad_name | Creative name |
| product_name | te_ads_object.app_name | Product name |
| package_name | te_ads_object.app_id | Product package name |
| platform | te_ads_object.platform | App platform |
| click | te_ads_object.clicks | Total clicks |
| conversion | te_ads_object.installs | Conversions |
| currency | te_ads_object.currency | Currency. The default is USD |
| impression | te_ads_object.impressions | Total impressions |
| location | te_ads_object.country | Country where the ad is delivered |
| spend | te_ads_object.cost | Total spend |