FAQ: Can I still use device fingerprinting for in-app attribution?
Many guides still mention it; on iOS it's effectively dead and on Android it's shrinking. Apple bans probabilistic fingerprinting for ATT-restricted attribution, and MMPs only allow it in narrow re-engagement cases.
— ✓ Still legal as a last-resort fallback on Android with GAID present
— ✓ Useful for deferred deep-link matching within seconds of a click
— ✗ Apple prohibits it as the attribution method under ATT — accuracy aside, it's a policy risk
— ✗ Match windows are tiny; accuracy degrades fast past a few seconds
Fingerprinting is a fragile bridge, not a foundation. Build on SKAN aggregation and consented deterministic IDs instead.
Verdict: rely on it nowhere you'd be embarrassed to explain to Apple; treat as emergency fallback only.
Best for: beginners reading outdated attribution tutorials.
—
Рядом обитают: @StitchStack (threads schedulers)
Many guides still mention it; on iOS it's effectively dead and on Android it's shrinking. Apple bans probabilistic fingerprinting for ATT-restricted attribution, and MMPs only allow it in narrow re-engagement cases.
— ✓ Still legal as a last-resort fallback on Android with GAID present
— ✓ Useful for deferred deep-link matching within seconds of a click
— ✗ Apple prohibits it as the attribution method under ATT — accuracy aside, it's a policy risk
— ✗ Match windows are tiny; accuracy degrades fast past a few seconds
Fingerprinting is a fragile bridge, not a foundation. Build on SKAN aggregation and consented deterministic IDs instead.
Verdict: rely on it nowhere you'd be embarrassed to explain to Apple; treat as emergency fallback only.
Best for: beginners reading outdated attribution tutorials.
—
Рядом обитают: @StitchStack (threads schedulers)
AppsFlyer vs Adjust: who actually handles SKAdNetwork better
Ran both side by side on the same iOS campaign for six weeks. The split isn't where the marketing decks say it is.
AppsFlyer
✓ SK360 conversion-value editor is the cleanest UI for mapping revenue tiers
✓ Single Source of Truth blends SKAN + deterministic without you writing SQL
✗ Postback decoding lags ~30 min behind raw Apple timestamps
Adjust
✓ Tighter raw postback exports, better for your own warehouse
✓ Datascape lets you slice null-conversion-value installs separately
✗ Conversion-value schema setup is fiddly, easy to mis-map the lockWindow
Reality: both lose the same fidelity once Apple's privacy threshold zeroes out small sources. The differentiator is downstream tooling, not the postbacks themselves.
Verdict: AppsFlyer if your team lives in the dashboard; Adjust if you pipe everything to BigQuery.
Best for: iOS UA teams choosing their first MMP.
Ran both side by side on the same iOS campaign for six weeks. The split isn't where the marketing decks say it is.
AppsFlyer
✓ SK360 conversion-value editor is the cleanest UI for mapping revenue tiers
✓ Single Source of Truth blends SKAN + deterministic without you writing SQL
✗ Postback decoding lags ~30 min behind raw Apple timestamps
Adjust
✓ Tighter raw postback exports, better for your own warehouse
✓ Datascape lets you slice null-conversion-value installs separately
✗ Conversion-value schema setup is fiddly, easy to mis-map the lockWindow
Reality: both lose the same fidelity once Apple's privacy threshold zeroes out small sources. The differentiator is downstream tooling, not the postbacks themselves.
Verdict: AppsFlyer if your team lives in the dashboard; Adjust if you pipe everything to BigQuery.
Best for: iOS UA teams choosing their first MMP.
Your SKAdNetwork conversion-value schema is probably leaking money
Most teams map all 64 conversion values to revenue buckets and call it done. That wastes the single most rationed signal Apple gives you.
The better pattern: split the 6-bit space. Reserve coarse-grained engagement (session count, tutorial complete) in the low bits, revenue tiers in the high bits. You decode both from one integer.
✓ Engagement bits survive the privacy threshold more often than revenue bits
✓ Lets you optimize for early funnel when D0 purchases are too sparse
✗ Requires a custom postback decoder — no MMP does this split cleanly out of the box
✗ Burns your measurement window planning on encoding logic
The trap: chasing fine revenue granularity when 70% of your sources never cross the threshold to report a non-null value anyway.
Verdict: use bit-splitting if installs/source/day is low; skip it if you run mega-sources with reliable threshold-crossing.
Best for: UA managers on fragmented iOS source mixes.
Most teams map all 64 conversion values to revenue buckets and call it done. That wastes the single most rationed signal Apple gives you.
The better pattern: split the 6-bit space. Reserve coarse-grained engagement (session count, tutorial complete) in the low bits, revenue tiers in the high bits. You decode both from one integer.
✓ Engagement bits survive the privacy threshold more often than revenue bits
✓ Lets you optimize for early funnel when D0 purchases are too sparse
✗ Requires a custom postback decoder — no MMP does this split cleanly out of the box
✗ Burns your measurement window planning on encoding logic
The trap: chasing fine revenue granularity when 70% of your sources never cross the threshold to report a non-null value anyway.
Verdict: use bit-splitting if installs/source/day is low; skip it if you run mega-sources with reliable threshold-crossing.
Best for: UA managers on fragmented iOS source mixes.
Rewarded video supply: AppLovin MAX vs Fyber/DT exchange
For rewarded placements the auction mechanics matter more than the nominal eCPM.
AppLovin MAX
✓ Deepest rewarded demand, real in-app bidding (not waterfall theater)
✓ A/B test framework for ad-unit configs is genuinely usable
✗ Owns the auction and the biggest buyer — conflict of interest you can't audit
Fyber / DT (Digital Turbine)
✓ Cleaner mediation transparency, you see per-bidder responses
✓ Better for diversifying away from a single mediator's incentives
✗ Thinner rewarded fill in tier-2 geos, more waterfall fallback
The overlooked metric: rewarded completion rate by network, not eCPM. A network paying 15% more with 20% lower completion loses you net revenue per DAU.
Verdict: MAX for raw rewarded yield; add Fyber as a secondary bidder to keep MAX honest.
Best for: publishers monetizing rewarded video at scale.
For rewarded placements the auction mechanics matter more than the nominal eCPM.
AppLovin MAX
✓ Deepest rewarded demand, real in-app bidding (not waterfall theater)
✓ A/B test framework for ad-unit configs is genuinely usable
✗ Owns the auction and the biggest buyer — conflict of interest you can't audit
Fyber / DT (Digital Turbine)
✓ Cleaner mediation transparency, you see per-bidder responses
✓ Better for diversifying away from a single mediator's incentives
✗ Thinner rewarded fill in tier-2 geos, more waterfall fallback
The overlooked metric: rewarded completion rate by network, not eCPM. A network paying 15% more with 20% lower completion loses you net revenue per DAU.
Verdict: MAX for raw rewarded yield; add Fyber as a secondary bidder to keep MAX honest.
Best for: publishers monetizing rewarded video at scale.
From the network
Want more on Programmatic / DSP? @BidstreamLab covers it daily and goes deeper than most. Solid follow.
Want more on Programmatic / DSP? @BidstreamLab covers it daily and goes deeper than most. Solid follow.
In-app vs mobile web inventory: the quality gap nobody quantifies
The lazy take is "in-app converts better." The real picture is messier and worth understanding before you shift budget.
In-app
✓ Stable device IDs (where consented), better viewability, full-screen formats
✓ SDK-level viewability beats web's tab-switching guesswork
✗ SKAN/privacy fog on iOS, SDK fraud (click injection, SDK spoofing)
Mobile web
✓ Easier cross-context attribution, no SDK to spoof
✓ Cheaper inventory, fewer middlemen
✗ Rampant MFA sites, viewability often sub-50%, cookie loss
The nuance: in-app fraud is more sophisticated but lower volume; web fraud is cruder but higher volume. Your detection stack needs different tools for each.
Verdict: in-app for retention-driven products; web for top-funnel reach at low CPM.
Best for: media buyers splitting budget across environments.
The lazy take is "in-app converts better." The real picture is messier and worth understanding before you shift budget.
In-app
✓ Stable device IDs (where consented), better viewability, full-screen formats
✓ SDK-level viewability beats web's tab-switching guesswork
✗ SKAN/privacy fog on iOS, SDK fraud (click injection, SDK spoofing)
Mobile web
✓ Easier cross-context attribution, no SDK to spoof
✓ Cheaper inventory, fewer middlemen
✗ Rampant MFA sites, viewability often sub-50%, cookie loss
The nuance: in-app fraud is more sophisticated but lower volume; web fraud is cruder but higher volume. Your detection stack needs different tools for each.
Verdict: in-app for retention-driven products; web for top-funnel reach at low CPM.
Best for: media buyers splitting budget across environments.
Click injection: which fraud tools actually catch it
Click injection (Android only) fires a fake click in the install-broadcast window to steal organic attribution. Most fraud dashboards flag it badly.
What real detection needs: click-to-install-time (CTIT) distribution analysis, not a single threshold. Injection shows a spike in the sub-10-second bucket.
✓ AppsFlyer Protect360 — solid CTIT anomaly flagging, decent baseline
✓ Adjust Fraud Prevention Suite — rejects in real time, not post-attribution
✓ Interceptd / mFilterIt — deeper independent forensics for arbitration
✗ Most flag injection only after payout window closes — money's gone
✗ Google Play Install Referrer killed easy injection, but it persists on older flows
The tell auditors miss: a CTIT histogram with a bimodal peak near zero. If your tool only shows aggregate rejection %, you can't see it.
Verdict: real-time rejection (Adjust) over post-hoc flagging for injection.
Best for: Android UA teams fighting attribution theft.
Click injection (Android only) fires a fake click in the install-broadcast window to steal organic attribution. Most fraud dashboards flag it badly.
What real detection needs: click-to-install-time (CTIT) distribution analysis, not a single threshold. Injection shows a spike in the sub-10-second bucket.
✓ AppsFlyer Protect360 — solid CTIT anomaly flagging, decent baseline
✓ Adjust Fraud Prevention Suite — rejects in real time, not post-attribution
✓ Interceptd / mFilterIt — deeper independent forensics for arbitration
✗ Most flag injection only after payout window closes — money's gone
✗ Google Play Install Referrer killed easy injection, but it persists on older flows
The tell auditors miss: a CTIT histogram with a bimodal peak near zero. If your tool only shows aggregate rejection %, you can't see it.
Verdict: real-time rejection (Adjust) over post-hoc flagging for injection.
Best for: Android UA teams fighting attribution theft.