InfluToAttribution
Referral tracking for mobile apps, with no black box.
Most app attribution leans on ad-network guesswork that Apple keeps breaking. InfluTo is deterministic by design: a redeemed referral code is an exact match — no IDFA, no ATT prompt, no SKAdNetwork data holes.
In short
InfluTo attributes installs and subscriptions with deterministic referral codes: when a user applies a creator's code, the match is exact — no IDFA, no ATT consent, no probabilistic modeling. A link-click fallback covers taps that never carried a code into the app: the install is matched to a recent click within 72 hours, inside your app only, and never by device characteristics. Every purchase is verified through RevenueCat, StoreKit 2 or Google Play.
iOS ATT opt-in reported by the two leading MMPs in 2025 — anything IDFA-based loses the rest.
of SKAdNetwork installs vanish into 'organic' under Apple's privacy thresholds.
SKAdNetwork postbacks are delayed and randomly jittered — never real-time.
Sources: AppsFlyer (post-ATT, 2025) · Adjust (ATT opt-in, 2025) · Apple SKAdNetwork docs · Adjust/Singular privacy-threshold guidance (2025–26). Figures are MMP-reported ranges.
How it works
Deterministic on every platform.
A referral code is an explicit, recorded action, so it attributes regardless of tracking permission — it never relied on cross-app tracking, so privacy changes don't touch it. Web and Capacitor apps receive the code in the link itself. For taps that never carried a code into the app, InfluTo matches the install to that recent click within 72 hours — inside your app only, and never by device characteristics. Apple bans device fingerprinting outright, and InfluTo doesn't use it: it confirms real purchases instead, via cryptographically signed StoreKit 2 transactions, Google Play, and RevenueCat.
What makes it deterministic
An exact match on every redeemed code
Deterministic attribution — no fingerprint, no IDFA, no ATT prompt.
Immune to privacy change
ATT opt-in stalled near 50% (some MMPs ~35%); codes don't depend on it.
No SKAdNetwork data holes
Skip the ≥24h postback delay and the ~10–15% of installs SKAN buries as 'organic'.
Deterministic on Android too
Google Play's Install Referrer returns signed referral data straight from the install record.
Verified against real revenue
StoreKit 2 JWS, Google Play and RevenueCat confirm a real purchase before a commission counts.
Attribution FAQ
Does referral-code attribution need IDFA or ATT permission?
No. A redeemed code is an explicit recorded action, so it works regardless of ATT consent. IDFA-based methods lose the roughly half of users (some MMPs report ~35%) who don't opt in.
Isn't SKAdNetwork enough?
SKAdNetwork and AdAttributionKit are aggregate-only, delay postbacks at least 24 hours, and bury roughly 10–15% of installs as 'organic' under privacy thresholds. Deterministic codes have none of those gaps.
Is device fingerprinting a viable fallback?
Not on iOS — Apple prohibits fingerprinting outright, even when tracking permission is granted. InfluTo doesn't rely on it; it verifies real purchases instead.
How does Android attribution compare?
Google Play's Install Referrer API is deterministic, returning referral data signed by Play straight from the install record.
What's the catch with codes?
A code only attributes when the user actually applies it. For taps that never carried a code into the app, InfluTo matches the install to that click within 72 hours — inside your app only, and never by device characteristics.
How do you confirm a real purchase, not just an install?
Through RevenueCat, StoreKit 2 (cryptographically signed JWS) and Google Play — so commissions pay against verified revenue, not raw installs.
Attribute every install — and every dollar.
Deterministic codes, a link fallback, and revenue validated at the source. Free to start.
Start free