Flagship
Launch attribution mapping
A written map of every path a first user can take into a new app, which of those paths you can actually measure, and where installs are falling into “unknown.”
Open the engagementEngagements
Work we take when a new app still has a chance to name its sources.
Each engagement is a reading or a map, not a subscription. Pick the one that matches where you are: before spend, in the first fortnight, or staring at a report that already feels too tidy.
Pre-launch measurement setup
A pass over links, store referrers, campaign names, and the first-open event before the first ringgit of launch spend goes out.
Open the engagement
Paid versus organic source review
A reading that separates paid credit from store search, word of mouth, and staff installs when a launch report has already blurred them.
Open the engagement
First-window source readout
A concentrated reading of the opening fourteen days after a new app reaches the stores — when most source mistakes are still cheap to correct.
Open the engagement
Attribution window advisory
Advice on how long a click or view should be allowed to claim an install when you are running a short launch burst rather than an always-on calendar.
Open the engagementHow to choose
If the listing is not yet live, start with pre-launch measurement setup or go straight to the full map. If you launched last week, the first-window readout is the honest next hour. If a paid campaign looks suspiciously complete, ask for a paid versus organic review.
What we will not pretend to do
We do not place ads, write store screenshots, or promise a retained user from a named source. The work stops at whether you can tell the doors apart, and what that means for the next burst of spend.