Native Ads for Mobile Apps: Routing, Attribution and Test Design
Plan web-to-app routing and privacy-aware attribution, verify installed and new-user journeys, and calculate CPI against retention and contribution.

Native advertising can introduce a mobile app through a publisher feed, but the useful outcome is an engaged user, not a cheap click or an ad that remains visible for weeks. Choose the destination and measurement method for the app, operating system and campaign you can actually support. A web landing page is one option; it is not a universal requirement or a guarantee of attribution.
What the historical examples show#
The June 2026 examples in this guide included WalkFit on the Microsoft Audience Network, a NetEase game update on that network, and browser-game messages attributed to MediaGo. These illustrate different propositions: an exercise use case, a content update and a game that can be played without downloading an app.
They do not establish installs, retention or profitable acquisition. In particular, the Rise of Kingdoms message offered browser play; that is not an observed app-install funnel. Nor does a game-update headline identify whether the advertiser selected acquisition or re-engagement targeting. Previously reported 30–38-day observation spans must not be read as continuous delivery, sustained spend or successful economics. The archive does not expose those advertisers' conversion data.
Use such examples to ask a concrete question: does your creative explain an honest reason to try the product, and does the destination deliver that experience? A lifestyle image and a product screenshot are competing creative choices to test, not a documented universal winner.
Separate destination routing from attribution#
A useful flow may be:
Ad → optional product page → configured app link → store or installed app → first open → meaningful event
The landing page can explain a product that needs context. A direct app link can reduce steps for an already understandable offer. Decide using measured downstream results rather than assuming that every extra page improves user quality.
An ordinary URL parameter carried to an app store does not, by itself, join an advertising click to an install. You need the selected measurement partner's supported integration, the app implementation and an eligible attribution method. Deep linking, deferred deep linking and attribution answer different questions:
- Deep linking: did an installed app open the intended screen?
- Deferred deep linking: after installation, did the app recover the intended destination?
- Attribution: did the measurement system assign an event to the campaign under its rules?
Success at one does not prove success at the others.
For one concrete implementation, AppsFlyer's OneLink setup documentation requires an app, a configured template and SDK integration for install measurement. Opening specific content requires app development as well as link configuration. Verify the app build's Universal Links or Android App Links association and implement the intended deep-link value; a marketer editing a URL alone cannot complete that work.
On Android, the Google Play Install Referrer API can return referral information from Google Play. That is a specific supported mechanism, not evidence that arbitrary parameters survive every store, browser and distribution path.
Respect the selected iOS measurement method#
Apple's privacy and data-use requirements require ATT permission for the cross-company tracking they describe. Another identifier is not a workaround for refusal, and device fingerprinting is prohibited. A website consent prompt does not override the app's ATT choice.
AppsFlyer's OneLink troubleshooting guidance distinguishes link behavior from attribution and limits the contexts in which it describes probabilistic modeling on iOS 14.5 and later. Do not generalize that statement into permission to model every non-consenting paid-ad user. Ask which method the exact integration uses, what it reports in aggregate, and what remains unavailable. Record those limits alongside results.
Private Relay, browser behavior and an outdated app build can also affect the journey. Handle an unavailable destination with a usable fallback; do not promise deterministic attribution or force tracking consent to repair it.
Verify the journey before spending#
Use a dedicated test link or platform preview, not a live ad click. Keep synthetic events separate from campaign reporting. The following is a reproducible test specification, not a report of tests performed for this article.
| Device and state | Routing observation to record | Measurement observation to record |
|---|---|---|
| iOS, app installed, ATT allowed | Intended screen or documented fallback | Test source and event, with supported attribution method |
| iOS, app installed, ATT denied | App remains usable and opens supported destination | No prohibited tracking; record aggregate or unavailable attribution explicitly |
| iOS, app absent, ATT allowed after install | Correct store, first open, intended deferred destination | Install and test event under the selected method |
| iOS, app absent, ATT denied | Correct store and functional first open | Actual permitted result; do not require a user-level match |
| Android, app installed | Intended screen and back-navigation behavior | Test event and campaign identifiers where supported |
| Android, app absent | Correct distribution store, install and first open | Supported referrer, attribution and test event |
| Unsupported OS or browser | Explicit web or store fallback | No invented install event |
Repeat relevant rows with consent for optional analytics denied, with the main in-app browser used by the campaign, and with Private Relay where applicable. Capture device/OS/browser, app and SDK versions, link configuration, consent state, timestamps and redacted event receipts. Follow the partner's test-device procedure so a reinstall is not silently treated as an existing user. Check duplicate-event handling and the destination reached, not merely a dashboard total.
An account screenshot alone cannot complete this matrix. It requires the instrumented app and actual devices or a documented supported test environment. A test install proves plumbing in that configuration; it does not establish campaign lift, retention or return on spend.
Calculate an affordable install cost#
For a click-priced campaign, with consistent cohorts and denominators:
CPI = spend ÷ attributed installs
A planning decomposition is:
CPI = CPC ÷ (landing-to-store rate × store-to-install rate)
For illustration only, $0.25 CPC, 35% landing-to-store and 45% store-to-install imply approximately $1.59 CPI. These are invented planning inputs, not network benchmarks. Attribution loss, a different denominator or organic installs mixed into the result will break the comparison.
Connect this to retained-user economics. If that hypothetical cohort retains 30% at day 7 and 15% at day 30, acquisition cost per retained user is about $5.29 and $10.58 respectively. Neither number is LTV. Suppose expected net contribution per acquired user is $2.40 after store fees, refunds and service costs: the acquisition margin would be about $0.81 at $1.59 CPI, before other overhead. If contribution is only $1.20, the same acquisition loses about $0.39. Use a defined payback horizon and mature cohorts to replace these assumptions.
Choose a campaign you can interpret#
Check the exact network's app eligibility, destination rules, OS/device controls and supported measurement partner. Do not infer those capabilities from seeing a competitor's creative. Split campaigns where it produces an actionable comparison—such as different apps, eligible regions or incompatible measurement paths—without fragmenting a limited test into unusably small cohorts.
Predefine a spending limit, the event that represents a useful user and the delay before results mature. Select an available bidding strategy that supports that event; there is no universal requirement to begin manually. Compare incremental acquisition cost and retained-user contribution with your alternatives using the same attribution window. Lower CPC alone is not a reason to scale.







