How to Track App Install Sources Without ATT
You can track app install sources without ATT by using privacy-first attribution methods that don't require device-level consent. Attribr provides a server-side solution that attributes installs to campaigns and channels using post-install signals and first-party data.
Why ATT Alone Isn't Enough
Apple's App Tracking Transparency has made IDFA unavailable for most users, blocking traditional mobile attribution. Many apps lose visibility into 60 - 80% of their install traffic because users decline tracking prompts. ATT dependency leaves you unable to measure campaign performance across organic, paid, and partner channels. This is why alternative attribution methods have become essential for app marketers who need actionable data without compromising user privacy.
Privacy-First Attribution Without ATT
Privacy-first attribution uses post-install behaviour, first-party data, and probabilistic modelling to infer install sources. Instead of tracking individual users, these methods aggregate campaign signals - such as install timing, cohort characteristics, and referral tags - to attribute volumes to channels. Server-side solutions like Attribr work by collecting consented data points (e.g. email, phone number, custom user IDs) and matching them against your campaign records. This approach respects user consent while delivering reliable attribution for budget allocation.
Using Deep Links and Custom Parameters
Deep links and URL parameters remain one of the most reliable ATT-free tracking methods. Attach unique identifiers or campaign codes to your install links - via branch.io, AppsFlyer, or direct URL schemes - then capture these parameters post-install. Your app can log the parameter to your server and match it to a known campaign. This method works for organic, email, and owned-channel traffic. For paid channels without deep link support, combine this with cohort analysis or first-party data matching to close attribution gaps.
First-Party Data Matching
If your users sign up or log in post-install, you can match their identity to your marketing database. Collect email addresses, phone numbers, or user IDs and share them (with consent) with your attribution platform. Server-side solutions then cross-reference these identities against your paid campaign audiences to determine which ad set drove the install. This method works best for apps with strong sign-up flows and is particularly effective for referral and affiliate channels where users are pre-identified.
Server-Side Attribution Platforms
Attribr and similar server-side attribution tools eliminate reliance on device IDs by processing install data on your own infrastructure. They ingest raw events from your app, match users to campaigns using consent-based signals, and model attribution for unmatched installs using statistical cohort analysis. This approach scales across iOS and Android, works for all install sources, and complies with privacy regulations. Setup typically involves installing an SDK, passing post-install events, and connecting your ad account API keys for campaign data.
Measuring What Matters: Cohort Analysis
When individual attribution is unavailable, cohort-level analysis becomes your window into campaign performance. Group installs by day, channel, and campaign, then track retention, spend per install, and LTV by cohort. This method doesn't identify every install source, but it reliably measures which channels and creatives drive value. Combined with incrementality testing, cohort analysis provides the confidence you need to shift budget without losing transparency to ATT limitations.
Ready to try Attribr by MRVL?
One tap to download. No sign-up wall.
Frequently asked questions
Can I track app installs without asking users for ATT permission?
Yes. You can use server-side attribution, deep links, first-party data matching, and cohort analysis - none of which require ATT consent. These methods work by capturing post-install signals and matching them to campaign data on your server.
What's the difference between server-side and client-side attribution?
Client-side attribution relies on device identifiers (IDFA) captured before install - blocked by ATT. Server-side attribution processes post-install user data and campaign records on your server, making it ATT-independent and more privacy-compliant.
How accurate is privacy-first attribution compared to IDFA-based tracking?
Privacy-first attribution achieves 85 - 95% accuracy for matched installs and uses statistical modelling for the remainder. While not pixel-perfect, it's reliable enough for budget allocation and significantly more complete than ATT-limited methods.
Which channels work best with ATT-free attribution?
Deep-link channels (email, SMS, organic, owned channels) are easiest to attribute. Paid channels benefit from first-party data matching or cohort analysis. Referral and affiliate traffic can be tracked via custom parameters or partner API data.
Do I need to integrate multiple tools to track without ATT?
Not necessarily. A server-side platform like Attribr handles most attribution types in one place. You may still use deep-link providers for certain channels, but centralising server-side processing reduces complexity.