All posts

June 2026 · The Nohmo team

Deterministic app install attribution, without the SDK bloat

Knowing which campaign drove an install is table stakes for mobile growth — but the mobile measurement partners that do it well are heavyweight, expensive, and enterprise-gated. Nohmo does deterministic install attribution with the same mechanism the big players use, built right into the SDK.

The click

You build a tracking link in the dashboard (Settings → App → Attribution Link Builder) with your UTM fields. When a user taps it, Nohmo records the click and routes them to the right store with a click ID attached.

Android: the Play Store referrer

On Android, the click ID rides along in the Play Store install referrer. Google Play delivers it to your app on first open, and the SDK reads it automatically — a 100% deterministic match back to the exact click. No GAID, no fingerprinting.

iOS: the system pasteboard

The App Store has no referrer parameter, so iOS uses a brief click interstitial that writes the click ID to the system pasteboard. On first open the SDK reads and clears it — deterministic when the user taps through, with GAID/IDFA and probabilistic IP matching as graceful fallbacks.

Zero code in your app

Attribution is built into the SDK. There’s no extra package to install and nothing to wire up — the SDK reads the referrer (Android) or pasteboard (iOS) on first open and sends it to the backend for matching. Results show up in App Analytics → Install Attribution, broken down by source, campaign, and match type.

Even invite-a-friend is attributed

Want installs from in-app sharing attributed to the user who shared? buildInviteLink() returns a short link carrying the sharer’s id, so you can see exactly who referred whom — deterministic on Android, best-effort on iOS.