Deferred deep link
A deep link flow that survives the install step so the user can still reach the intended content after first open.
Formal definition
A deferred deep link is a deep link flow that preserves an intended in-app destination across the install boundary so the user can be routed after first open if the app was not installed at click time.
Plain-English explanation
If the app is missing, the user goes to the store first, installs the app, and still lands in the right place after the first open.
Visual journey
Journey: the user taps a deep link before the app is installed, goes through the store, opens the app for the first time, and still reaches the intended offer screen because the destination context was preserved across install.
Examples
- A referral link should still open the invite-accept screen after installation.
- A promo campaign should still deliver the user to the limited-offer screen after first launch.
How it works
- The initial click stores destination context before redirecting to the store.
- After install, the SDK or backend resolves that stored context on first open.
- The app receives the destination payload and routes the user to the intended experience.
How Attriax uses it
- Deferred deep linking is a core Attriax flow because many campaign journeys cross the install boundary.
- The platform keeps the source and destination context together so post-install routing still reflects the original intent.
- This is especially important for onboarding, referral flows, and store-driven campaigns.
Questions people ask
What if the app is already installed?
Then the flow usually behaves like a regular deep link instead of a deferred one. The user can be sent directly to the target screen without the install step in between.