01
First-open destination resolve
After install, the SDK can ask Attry for the pending deep link destination and open the correct onboarding, paywall, referral, or campaign-specific screen.
AttryDeferred Deep Links
Deferred deep links that survive the store install.
Attry keeps campaign context alive while a user moves from a link click to the App Store or Google Play and then into the first app open. Your SDK can resolve the pending destination and connect installs, opens, and revenue events back to the original campaign.
Short-lived click context for install flows
Android Install Referrer and SDK resolve support
Confidence labels for iOS matches that are not deterministic
Click context after install
Deferred deep linking lets a campaign click become a first-app-open destination instead of disappearing during the store handoff.
01
click_
creator campaign
02
store_
App Store or Google Play
03
first open_
SDK resolve
04
result_
/paywall + campaign
attribution payload_
source=tiktok · campaign=spring · match=high
Deferred attribution without fake certainty
Attry is built around the reality of modern mobile privacy. It records strong signals when they exist, uses deterministic store APIs where possible, and labels probabilistic matches clearly.
02
Android Install Referrer support
Android installs can use Google Play Install Referrer signals for high-confidence campaign matching when the referrer is available.
03
iOS confidence labels
For iOS installs outside Apple Search Ads, Attry uses timing, device context, country, link metadata, and SDK events carefully instead of presenting estimates as facts.
04
Revenue context after install
Trials, purchases, renewals, and subscriptions can inherit the click and campaign metadata that started the install path.
How deferred deep links work in Attry
The flow is intentionally simple: record the click, preserve the match window, resolve on first open, and keep attribution attached to later events.
01
Record the campaign click
Attry stores source, campaign, device, location, routing, and custom link data with a short-lived match context.
02
Send the user through the store
If the app is not installed, Attry routes the user to App Store or Google Play while preserving the click context server-side.
03
Resolve from the SDK
On first app open, the SDK calls Attry to resolve the deferred destination and attach the original campaign to the install.
04
Measure downstream events
Subscription and purchase events can roll up by link, campaign, source, keyword, country, city, and confidence level.
Deferred deep linking for subscription apps
Deferred deep links matter most when paid acquisition and revenue happen after an install. Attry helps mobile subscription apps understand which campaign created the install, which path the user should open after first launch, and which later events should be attributed to that entry point.
useful for_
Deferred deep links for iOS and Android apps
First-open route resolution through the Attry SDK
Android Install Referrer and iOS confidence-based matching
Campaign attribution for trials, purchases, and subscriptions
Clear match confidence instead of hidden black-box attribution
Common questions
Practical answers for teams comparing deep linking tools, mobile attribution platforms, and SDK-based event tracking.
What is a deferred deep link?
A deferred deep link preserves the intended app destination and campaign context when the user does not have the app installed yet. After the user installs and opens the app, the SDK resolves the original destination.
Is deferred deep linking deterministic on iOS?
Not always. Apple Search Ads can provide deterministic campaign IDs through Apple APIs, but many non-ASA iOS install paths require confidence-based matching. Attry labels these matches instead of hiding uncertainty.
Can deferred deep links attribute revenue?
Yes. When SDK events include trials, purchases, renewals, or subscriptions, Attry can connect those events back to the click, campaign, and link that started the install path.