Native Mobile Advertising Test
Make the ad advance the user's immediate in-app objective
- Difficulty
- Moderate
- Time to result
- ~weeks to results
- Steps
- 5
- Confidence
- 90%
The Native Mobile Advertising Test starts from the observation that mobile applications provide little screen space and usually immerse users in one focused activity. Desktop banners transplanted into that environment interrupt the task without using the application's unique capabilities. A stronger ad unit begins with the user's immediate objective and asks whether a sponsor can help advance it. In navigation, that might mean promoting a relevant destination the user can route to; in an augmented-reality game, it might mean sponsoring a real-world location players already seek. Because the interaction occurs through the application's normal workflow, the product can often measure a meaningful outcome rather than an impression. The test succeeds when the ad feels like a useful native action, produces consent-aligned attribution, and preserves the experience even on a small screen.
Origin
Extracted from Acquired's discussion of Waze, location-based attribution, and why mobile advertising needed formats designed for each application's specific experience.
Core principles
- 01Design for the mobile context rather than shrinking desktop formats
- 02Align the advertisement with the user's current objective
- 03Make the promoted action native to the product's core interaction
- 04Use observable outcomes to close the attribution loop
- 05Respect the permission users granted for the product's primary purpose
How to run it
- 1
Name the Immediate User Objective
Describe what the user is trying to accomplish during the exact session in which an advertisement may appear.
Pro tip Use a concrete verb such as navigate, discover, message, watch, or purchase.
Watch out Broad goals like engagement are too vague to guide a native format.
- 2
Find a Helpful Sponsored Action
Identify an advertiser-funded action that can move the user closer to that objective rather than diverting attention from it.
Pro tip Start with businesses, content, or locations already relevant to the task.
Watch out Relevance alone does not make an interruption useful.
- 3
Use the Product's Native Interaction
Deliver the promotion through a familiar action already central to the application, such as routing to a destination or visiting a game location.
Pro tip Avoid introducing a separate advertising interaction model.
Watch out A desktop rectangle embedded in a feed is not automatically native.
- 4
Close the Measurement Loop
Measure a meaningful outcome using signals users reasonably expect the application to process.
Pro tip Prefer navigation starts, arrivals, reservations, or completed actions over impressions.
Watch out Do not stretch a functional permission into unrelated tracking.
- 5
Validate Experience and Incrementality
Test whether the format helps users, creates incremental advertiser outcomes, and avoids degrading retention or trust.
Pro tip Compare against both no-ad and conventional-format controls.
Watch out High click-through rates can conceal accidental taps or long-term product damage.
In the wild
A driver sees a relevant promoted location, chooses it, and asks Waze to navigate there. The ad uses the product's core routing interaction, while expected location signals let Waze observe whether the trip reaches the destination.
→ The advertiser receives a measurable real-world action rather than a mobile banner impression.
A café sponsors an in-game location that nearby players already want to visit. The promotion adds value to the game's location-seeking loop and can be measured through visits without placing an unrelated display box over gameplay.
→ The business gains foot traffic while the promotion remains part of the native experience.
Common mistakes
Shrinking a Desktop Banner
Mobile has limited screen space and focused sessions, so a smaller desktop unit remains structurally interruptive.
Optimizing Impressions Instead of Outcomes
A native format should measure a useful action such as navigation or arrival, not merely exposure.
Abusing Functional Permissions
Users may permit location for navigation without consenting to unrelated tracking or opaque data sharing.
Is it for you?
Best for
It is best for focused mobile experiences where a sponsored action can naturally help users discover, navigate, communicate, or transact.
Not ideal for
It is not ideal when advertisers cannot contribute to the user's immediate objective or when attribution requires unexpected surveillance.
From the transcript
“the idea of putting it into an app where you very explicitly have said, please track me.”
“the way that mobile advertising succeeds is that it's native, it's very specific to the platform”
From the episode
Waze