Overview
After you connect AppsFlyer to MNTN, app installs and configured in-app events will appear in most MNTN Reports. Use reporting filters to review AppsFlyer performance by conversion source and conversion type, including installs and any custom in-app events you mapped during setup.
Some visit-based reports and metrics may not apply to app-only campaigns. See Reporting Availability to learn more.
Access It
Sign in to MNTN.
At the top of the platform, click on the REPORTING tab.
Use reporting filters to review AppsFlyer performance:
Filter | Value |
Conversion Source | AppsFlyer |
Conversion Type | Install, or the custom in-app events configured during setup |
If no AppsFlyer data exists in the selected date range, AppsFlyer values may not appear in the filter.
Reporting Availability
Most MNTN reports can populate with app install and in-app event data from AppsFlyer. However, these reports and metrics rely on website visit data, so they won’t apply to app-only performance:
Report or metric | Why it may not apply |
Visit Metrics Cost per Visit, Verified Visits, Visit Assist, and Visit Rate | App install campaigns don't generate website visits. |
Site Impact Report Site Visitor Metrics | App measurement is based on installs and in-app events, not site visitors. |
Attribution Paths Report | App-only campaigns don't generate website visit paths. |
Incrementality Report | App install campaigns don't generate website visit data. |
If you’re tracking both app performance and website performance, these reports and metrics can still function for website activity tracked by the MNTN Pixel.
Understand Reporting Differences
You may see different results in MNTN and AppsFlyer. This is expected because each platform measures performance differently.
AppsFlyer helps you compare app performance across many marketing channels, including channels where people click an ad before installing or opening your app.
MNTN Reporting is built to measure Connected TV (CTV) performance. CTV works differently from clickable channels because someone may see your ad on TV, then install or open your app later from another device.
To help measure that journey, MNTN connects CTV ad exposure to app activity at the household level. This helps capture cases where someone sees an ad on TV, then takes action later on a phone or tablet.
Difference | MNTN Reporting | AppsFlyer Reporting |
Attribution window | Uses the conversion window set in MNTN. The default is 30 days. | Supports a maximum 72-hour probabilistic view-through attribution window for CTV. |
Attribution priority | Measures MNTN performance using MNTN’s attribution methodology. | May assign credit to other channels that rank higher in AppsFlyer’s attribution model. |
Cross-device attribution | Uses household-level, ID-agnostic attribution to connect ad exposure to app installs across devices. | Requires the install to occur on a device using the same IP network as the CTV ad exposure. |
What this means
MNTN | AppsFlyer |
May show higher attributed performance because it is built to measure how CTV influences app activity across devices and over your configured conversion window. | May show lower attributed performance for MNTN campaigns because it uses a shorter CTV attribution window, may give credit to other channels, and requires IP-based matching. |
To compare reporting more conservatively, you can adjust your MNTN conversion window to more closely match your AppsFlyer attribution window.
Quick Answers
What is the attribution window for app performance in MNTN?
What is the attribution window for app performance in MNTN?
App performance uses the conversion window set in MNTN. The default is 30 days, but you can shorten or extend it.
If you run app and web campaigns in the same account, the same conversion window applies to both app and web performance. MNTN does not support separate conversion windows for app and web activity in the same account.