Tencent daily report
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 |
|---|---|---|---|---|---|---|---|---|
| Daily report | API | Aggregated data | ✅ | ✅ | ✅ | ✅ | ✅ |
The Tencent Ads daily report supports sending back aggregated data, including metrics such as spend, clicks, and impressions
Integration process
The data integration process with Tencent Ads is as follows:
- Log in to the AE backend, go to the Third-party Integration module, add a Tencent Ads daily report integration plan, complete the related configuration, and copy the authorization callback URL
- Go to the Tencent Ads developer platform, register as a developer, create an app, and get the Client ID and Client Secret
- Go back to the AE backend, edit the Tencent Ads daily report integration plan you created earlier to use the app's Client ID and Secret, and open the authorization link to complete authorization
- Check whether the AE system receives the data successfully, and build reports
1. Plan configuration
Before connecting Tencent Ads data, create the corresponding integration plan in the AE backend and get the authorization callback URL. Follow this document to create the integration plan
1.1 Enter temporary authorization information
First, click Configure authorization information in the authorization information section. In the authorization information dialog that appears, enter any authorization information as temporary authorization information. You need to adjust it after you create the app on the Tencent Ads developer platform.
1.2 Sync Schedule
In the Sync Schedule module, you can set the policy for the AE system to pull Tencent Ads daily report 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
1.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.
1.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 |
| source | metrics | Fields of the pulled data. List type. Customizable |
| group_by | Aggregation conditions of the pulled data. List type. Customizable | |
| extra_params | level | Report type level of the pulled data. Customizable |
- Report type levels and aggregation conditions
The report type level and aggregation conditions determine the data granularity of the daily report, for example, whether data is aggregated by ad group or by material. Each query can use only one report type level, and different report type levels support different aggregation conditions. The following are some commonly used levels and the aggregation conditions they support. For details, see the official documentation. The default report type level and aggregation conditions are REPORT_LEVEL_AD and "date","ad_id","site_set" respectively. To adjust them, enter the report type level in extra_params and the aggregation conditions in source.group_by:
| Report type level | Description | Default | Supported aggregation conditions |
|---|---|---|---|
| REPORT_LEVEL_ADVERTISER | Advertiser-level report | "date" | |
| REPORT_LEVEL_CAMPAIGN | Campaign-level report | "date", "campaign_id" | |
| REPORT_LEVEL_ADGROUP | Ad group-level report | "date", "adgroup_id", "site_set" | |
| REPORT_LEVEL_AD | Ad-level report | Yes | "date", "ad_id", "site_set" |
| REPORT_LEVEL_MATERIAL_VIDEO | Video material report | "date", "material_id", "site_set" | |
| REPORT_LEVEL_MATERIAL_IMAGE | Image material report | "date", "material_id", "site_set" |
- Pulled fields
The following are the grouping fields that the daily report pulls by default. Note that grouping fields are affected by the pulled dimensions: a fine-grained aggregation condition supports the grouping fields of its coarser-grained aggregation conditions. For example, with "ad_id" as the aggregation condition, you can pull coarser-grained grouping fields such as "campaign_name" and "adgroup_id". To adjust them, enter the names of the grouping fields you need in source.metrics:
| Grouping field | Description |
|---|---|
| campaign_name | Campaign name |
| campaign_id | Campaign ID |
| adgroup_name | Ad group name |
| adgroup_id | Ad group ID |
| ad_name | Ad name |
| ad_id | Ad ID |
| account_id | Ad account ID |
The following are some of the metrics supported by the daily report. Because this report has a very large number of metrics, only some commonly used ones are shown here. To learn about all metrics, see the official documentation. To adjust them, enter the field names in source.metrics:
| Field | Description |
|---|---|
| view_count | Impressions |
| download_count | App download completions |
| activated_count | Total app activations |
| activated_rate | App download-to-activation rate |
| thousand_display_price | Average cost per 1,000 impressions |
| valid_click_count | Clicks |
| ctr | Click-through rate |
| cpc | Average cost per click |
| cost | Spend |
| key_page_view_cost | Key page visit cost |
| coupon_click_count | (Games) Gift pack redemption button clicks |
| coupon_issue_count | (Games) Gift packs (coupons) issued |
| coupon_get_count | (Games) Gift packs (coupons) claimed |
| download_rate | App download rate |
| download_cost | App download cost |
| install_count | App installs |
| install_cost | App install cost |
| click_activated_rate | App click-to-activation rate |
| activated_cost | App activation cost |
| app_register_count | Registrations (app) |
| register_by_display_count | Registrations (view-through attribution) |
| app_register_cost | Registration cost (app) |
| app_order_cost | Order cost (app) |
| app_checkout_count | Payment actions (app) |
| app_checkout_by_display_count | Payment actions (view-through attribution) |
| app_checkout_cost | Payment action cost (app) |
| app_ad_paying_users | Ad monetization users (app) |
| ad_pur_val_app | Ad monetization amount (app) |
| game_create_role_count | In-game character creations |
| game_authorize_count | Game authorizations |
| game_tutorial_finish_count | Game tutorial completions |
| app_checkout_rate | Click-to-payment action rate (app) |
| app_activated_checkout_rate | Activation-to-payment action rate (app) |
| app_register_rate | Registration rate (app) |
| install_rate | App install rate |
| first_pay_count | Users with a first payment action |
| first_pay_rate | First activation-to-payment rate |
| wechat_app_register_uv | WeChat mini game registered users |
| no_interest_count | "Not interested" clicks |
| mini_game_register_users | Mini game registered users |
| mini_game_register_cost | Mini game registration cost |
| mini_game_register_rate | Mini game registration rate |
| mini_game_ad_monetization_users | Mini game ad monetization users |
| mini_game_paying_count | Mini game purchases |
| mini_game_paying_amount | Mini game payment amount |
| mini_game_first_paying_users | Mini game first-time paying users |
| mini_game_create_role_users | Users who created in-game characters |
| mini_game_create_role_cost | In-game character creation cost |
| mini_game_key_page_viewers | Mini game key page visitors |
| mini_game_key_page_view_cost | Mini game key page visit cost |
| mini_game_ad_monetization_amount | Mini game ad monetization amount |
| key_page_view_rate | Key page visit rate |
| activate_register_rate | Activation-to-registration rate |
| key_behavior_conversions_count | Key action conversions |
| key_behavior_conversions_cost | Key action conversion cost |
| key_behavior_conversions_rate | Key action conversion rate |
| mini_game_ad_monetization_cost | Mini game ad monetization cost |
| mini_game_bf_uv | Mini game returning users |
| mini_game_bf_cost | Mini game returning user cost |
| mini_game_bf_income_uv | Ad monetization users among mini game returning users |
| mini_game_bf_income_amount | Ad monetization amount from mini game returning users |
| mini_game_bf_income_d1_uv | First-day ad monetization users among mini game returning users |
| mini_game_bf_income_d1_amount | First-day ad monetization amount from mini game returning users |
| mini_game_bf_income_d1_cost | First-day ad monetization cost of mini game returning users |
1.5 Get the authorization callback URL
After completing the above configuration, click Save and authorize in the upper-right corner to get the authorization information. Copy the authorization callback URL from the first step and keep it safe. Then click Reject authorization. to close the pop-up:
The plan is saved when you click Save and authorize, so you do not need to save it separately. You have now temporarily completed the configuration in the AE backend. Next, complete the related configuration in the Tencent Ads backend.
2. Register as a developer and create an app
Next, log in to the Tencent Ads developer backend and register as a developer with another QQ account.
After registering as a developer, click Create New App on the app management dashboard.
Then, create the app on the Create App page:
- For the app type, select Third-party Application
- The app icon, app name, and app description can be customized
- For the callback URL, enter the authorization information URL you got in the AE system
In Permission Selection, select at least the Ads Insight permission
After creating the app, get the app's client id and client_secret and write them down
3. Go back to the AE backend and complete authorization
After creating the Tencent app, go back to the AE backend, open the Tencent integration plan you created earlier, and click Configure authorization information under Authorization Information:
Next, enter the Client ID and Client Secret of your Tencent app in the corresponding fields. In Login ID, enter the QQ number or WeChat ID you plan to log in with during authorization. In Account ID List, you can enter the IDs of the ad accounts to pull data from. Separate multiple IDs with ",". If you leave it empty, data for all authorized ad accounts is pulled. After editing, click the save button:
Then click Save and authorize in the upper-right corner to open the authorization information dialog again. Click Go to authorization to open the Tencent authorization page
On the authorization page, log in to your ad account, select at least the Ads Insight data permission, and click the agree button to complete authorization
Note that if you log in and authorize with a QQ direct customer account, you only get data permissions for the current customer's promotion account. If you log in and authorize with a QQ Business Manager account, you get data permissions for all promotion accounts under the manager account.
After completing authorization, in Authorization Information, click I have completed the above two steps in the lower-left corner, and then click Complete Authorization in the lower-right corner to finish the configuration. You have now completed the data integration for the Tencent platform.
4. Data ingestion
4.1 Ingestion rules
- The start_date field in the data, that is, the aggregation time of the data, is used as the event's #event_time
- The default event name is —— tencent_ads_daily_report
- All other fields are ingested
4.2 Standardized fields
The AE system standardizes some fields in the Tencent daily report data:
| Original field | Standardized | Description |
|---|---|---|
| campaign_name | te_ads_object.campaign_name | Campaign name |
| campaign_id | te_ads_object.campaign_id | Campaign ID |
| adgroup_name | te_ads_object.ad_group_name | Ad group name |
| adgroup_id | te_ads_object.ad_group_id | Ad group ID |
| ad_name | te_ads_object.ad_name | Ad name |
| ad_id | te_ads_object.ad_id | Ad ID |
| account_id | te_ads_object.account_id | Ad account ID |
| view_count | te_ads_object.impressions | Impressions |
| valid_click_count | te_ads_object.clicks | Clicks |
| cost | te_ads_object.cost | Spend |
| install_count | te_ads_object.installs | App installs |