At a glance: Description and comparison of aggregated and analytics attribution reports, tools, and APIs available.
Aggregated and analytics performance reporting—tools and reports
Aggregated analytic tools in the platform provide advertisers with metrics enabling them to assess the performance of their apps, campaigns, and users.
The tools differ in the way data is presented. For example, the Overview dashboard provides lifetime value metrics of campaigns (LTV) whereas Cohort is used to analyze user engagement over time.
The tools detailed in this article relate to data that can be exported from the platform. Use the tool comparison table that follows to understand the main function and differences between the tools.
Related reading: About raw-data reporting
Tool comparison
工具 | LTV/ activity |
说明 | Multi /single app (1) | 数据新鲜度 | Timezone | 货币 |
---|---|---|---|---|---|---|
Dashboards in the UI | Both |
Download dashboard data in a CSV |
单应用 | 持续滚动 |
取决于应用层级的配置 |
取决于应用层级的配置 |
Aggregated data export page | 用户生命周期价值 |
Aggregate reports download in a CSV |
单应用 | 持续滚动 |
取决于应用层级的配置 |
取决于应用层级的配置 |
Pull API*-aggregate |
用户生命周期价值 |
Aggregate reports via API
|
Single |
Continuous |
Selectable |
取决于应用层级的配置 |
|
Both |
Performance metrics (KPIs) |
Multi | 每日 | Selectable Default: UTC (2) |
可选 默认值:美金 |
Pivot P |
Both | Get campaign performance metrics (KPIs) via the user interface. | Multi | 每日 | App-specific (2) | USD |
Cohort |
用户生命周期价值 |
See the section that follows. It details the Cohort flavors
|
Multi | 每日 | App-specific (2) | 取决于应用层级的配置 |
Notes/abbreviation: (2) Apps all need to be set to the same app-specific time zone. If not, then the time is in UTC. |
Cohort flavors
Cohort is available in a number of different flavors being Cohort dashboard, Cohort API, and Cohort analytics via Data Locker. The table that follows lists the differences.
主要特点 |
Data Locker中的群组分析报告 |
Cohort Dashboard |
群组报告API |
---|---|---|---|
高级功能 | ![]() |
否 | ![]() |
Multi or single app |
Multi. Data is grouped per app in a single file or segregated into separate files per app. |
Multi. Combined performance or grouped by app options. | 单应用 |
币种 | USD and app-specific (both) | 取决于应用层级的配置 | Either USD or app-specific |
分组 |
Full campaign hierarchy and event names. Approx. 20 groupings |
4 groupings | 7 groupings |
Metrics available | All metrics | 1 selectable metric and 4 fixed metrics per view | 1 selectable metric and 4 fixed metrics per call |
Days post-attribution available (cohort days) | 365 | 180 | 180 |
数据新鲜度 | Daily. Midnight UTC and avialble at 10:00 UTC. | Continuous (using app-specific timezone) | Continous (using UTC or app-specific timezone) |
Data export limitations | Entire data set is available | Manual download and settings | Rate and response size limited |
Transparent agency support | 是 | 是 | Not supported. This means that the media source of agency-driven traffic is always masked. |
Customizable request | 否 | 是 | 是 |
用户链路报告
- The reports described are available via the Export Data page or by using Pull API aggregate.
- They are Lifetime value (LTV) so the reporting date range relates to the attribution date being:
- Install date for UA and Protect360 reports
- Re-attribution or re-engagement date in the case of retargeting reports
- The earliest reporting date available is the first app install date.
UA reports
报告名称 | 分组维度: |
---|---|
合作伙伴(媒体渠道) | Agency, media source, campaign |
渠道每日汇总 | Date, agency, media source, campaign |
日常行为 | Date, agency, media source, campaign |
地理位置 | Country, agency, media source, campaign |
国家/地区+每日汇总 | Date, country, agency, media source, campaign |
浏览型归因(VTA)的KPI | |
Note: If Facebook is the media source selected then additional columns are included: Adgroup ID, Adgroup name, Adset ID, Adset name |
Date fields in the CSV files have the format yyyy-mm-dd. When you open a CSV file in Excel, date fields are formatted using your computer's date and time settings. Be sure to select the appropriate date display in Excel.
Examples of aggregate reports
Report examples in a spreadsheet
Field | 描述 |
报告名称 |
||||
---|---|---|---|---|---|---|
Partner (media source) |
Partner by date |
每日 |
地理位置 |
国家/地区+每日汇总 |
||
国家 |
Install country |
✓ |
✓ | |||
日期 |
Attribution date |
✓ |
✓ |
|||
Agency/PMD (af_prt) |
Agency/partner name |
✓ |
✓ |
✓ |
✓ |
✓ |
媒体渠道 (pid) |
Media source bringing the user (pid=media source) |
✓ |
✓ |
✓ |
✓ |
✓ |
广告系列活动 |
Campaign 名称 (c= campaign name) |
✓ |
✓ |
✓ |
✓ |
✓ |
广告系列活动ID |
Facebook campaign ID |
FB only |
FB only |
FB only |
FB only |
FB only |
Adgroup ID |
Facebook ad group ID or Ad ID |
FB only |
FB only |
FB only |
FB only |
FB only |
Adgroup Name |
Facebook ad group |
FB only |
FB only |
FB only |
FB only |
FB only |
广告组ID |
Facebook 广告组 ID |
FB only |
FB only |
FB only |
FB only |
FB only |
广告设置名称 |
Facebook adset name |
FB only |
FB only |
FB only |
FB only |
FB only |
ARPU |
每用户平均收入 |
✓ |
✓ |
✓ |
✓ |
|
平均eCPI |
平均eCPI |
✓ |
||||
点击 |
Number of clicks |
✓ |
✓ |
✓ |
✓ |
✓ |
转化率 |
Number of installs/number of clicks |
✓ |
✓ |
✓ |
✓ |
✓ |
CTR |
点击至激活率 |
✓ |
✓ |
|||
{your event name}(Unique users) |
Number of unique users who performed the event |
✓ |
✓ |
✓ |
✓ |
|
{your event name} (Event counter) |
事件数量 |
✓ |
✓ |
✓ |
✓ |
|
{your event name} (Sales in XXX) |
Event sales in XXX where XXX is the app-selected currency |
✓ |
✓ |
✓ |
✓ |
|
展示 |
Number of impressions |
✓ |
✓ |
|||
安装 |
安装数量 |
✓ |
✓ |
✓ |
✓ |
✓ |
忠诚用户数量 |
[default] User who opens the app more than 3 times |
✓ |
✓ |
✓ |
✓ |
✓ |
忠实用户数/总激活数 |
忠诚用户率 |
✓ |
✓ |
|||
投资回报率 |
Return on investment |
✓ |
✓ |
|||
互动 |
|
✓ |
✓ |
✓ |
✓ |
✓ |
总成本 |
- |
✓ |
✓ |
|||
总收入 |
Total revenue generated from the media source and campaign |
✓ |
✓ |
✓ |
✓ |
|
Note: FB-only columns are included when selecting Facebook as the only media source. |
再营销
- Retargeting reports consist of users who engaged with a retargeting campaign and performed a re-engagement or re-attribution.
- In retargeting reports, there is no distinction between organic and non-organic users.
- To get retargeting reports via Pull API, append the &reattr=true parameter to performance reports URIs.
报告名称 | 分组维度: |
---|---|
合作伙伴(媒体渠道) | Agency, media source, campaign |
渠道每日汇总 | Date, agency, media source, campaign |
Activity by date | Date, agency, media source, campaign |
国家 | Country, agency, media source, campaign |
Country by date | Date, country, agency, media source, campaign |
Field | 描述 | 合作伙伴 | 每日 | 渠道每日汇总 | 国家/地区+每日汇总 | 地理位置 |
---|---|---|---|---|---|---|
日期 | Conversion date | ✓ | ✓ | |||
国家 | ✓ | ✓ | ✓ | |||
Agency/PMD (af_prt) | Agency/partner name | ✓ | ✓ | ✓ | ✓ | ✓ |
媒体渠道 (pid) | ✓ | ✓ | ✓ | ✓ | ✓ | |
广告系列(c) | ✓ | ✓ | ✓ | ✓ | ✓ | |
点击 | ✓ | ✓ | ✓ | ✓ | ✓ | |
转化量 | ✓ | ✓ | ✓ | ✓ | ✓ | |
转化类型 | Re-attribution or re-engagement | ✓ | ✓ | ✓ | ✓ | ✓ |
转化率 | Conversions/clicks | ✓ | ✓ | ✓ | ✓ | ✓ |
互动 | ✓ | ✓ | ✓ | ✓ | ✓ | |
忠诚用户数量 | ✓ | ✓ | ✓ | ✓ | ✓ | |
忠实用户数/总激活数 | ✓ | ✓ | ✓ | ✓ | ✓ | |
总成本 | ✓ | ✓ | ✓ | ✓ | ✓ | |
平均eCPI | ✓ | ✓ | ||||
总收入 | ✓ | ✓ | ✓ | ✓ | ✓ | |
投资回报率 | ✓ | ✓ | ✓ | ✓ | ✓ | |
ARPU | ✓ | ✓ | ✓ | ✓ |
功能报告
SKAdNetwork
Blocked fraud Protect360
- Blocked fraud aggregate reports provide details of events blocked by Protect360.
- The reports are available via Pull API. These reports aren't available via the Export Data page.
- The date range relates to the install date.
报告名称 |
---|
合作伙伴(媒体渠道) |
渠道每日汇总 |
地理位置 |
国家/地区+每日汇总 |
Partner's campaign report |
Limitation: The blocking reason Bots displays even in cases where the reason should be app version or missing customer user id.