Deep Links and QR Reference
Deep links and QR are high-impact acquisition surfaces and should be configured carefully.Deep-link behavior model
A deep-link setup usually defines:- iOS deep-link target
- Android deep-link target
- web fallback destination
- in-app browser breakout strategy
Deep-link configuration checklist
- Confirm app target identifiers are correct for iOS and Android.
- Confirm fallback URL is live and optimized for mobile users.
- Confirm rule-level overrides do not conflict with link-level deep-link settings.
- Confirm campaign goals align with deep-link destination intent.
- Confirm QA has tested app-open and fallback behavior on real devices.
Fallback strategy
Always define a safe fallback destination for:- devices without app installed
- unsupported deep-link scheme contexts
- app open failures
- app store product page
- mobile web landing page
- campaign-specific web destination
In-app browser handling
Some traffic sources open links inside in-app browsers with restricted deep-link behavior. Operational guidance:- test social in-app browsers separately from standard browser apps.
- verify expected behavior for app-installed and app-not-installed paths.
- use fallback messaging that clearly tells users what to do next.
Testing matrix
Validate deep links across:- iOS browsers and in-app browsers
- Android browsers and in-app browsers
- desktop fallback behavior
- iOS universal/app-link behavior
- Android intent/app-link behavior
- default-browser breakout behavior for in-app social browsers
Deep-link troubleshooting patterns
| Symptom | Likely cause | What to validate |
|---|---|---|
| App does not open on mobile | App link/universal link config mismatch | Platform-level app link association |
| Users land on wrong page in app | Incorrect deep-link path/parameters | Final generated deep-link target |
| High fallback share after release | In-app browser restrictions or app not installed | Browser source mix and install rate |
| Different behavior between iOS and Android | Platform-specific deep-link constraints | Platform test matrix completion |
QR operations
QR setup typically includes:- destination mapping
- campaign and link assignment
- visual style customization
- print-safe testing
- foreground/background color
- optional logo overlay
- error-correction tuning for print reliability
- PNG/SVG download workflows
QR publishing checklist
- Validate scan reliability at expected print size and distance.
- Avoid extreme low-contrast color combinations.
- Re-test whenever destination routing changes materially.
- Keep one QR per campaign objective to simplify analytics interpretation.
- Store versioned assets so reprints use the intended destination logic.
QR analytics interpretation
Track and compare:- total scans
- unique scanners
- mobile scan share
- deep-link app-open share
- fallback redirect share
- high app-open share usually indicates strong mobile app adoption.
- high fallback share can indicate missing app install base or deep-link breakage.
- large changes after creative or channel shifts usually reflect audience/device mix changes.
Operational guidance
- keep QR campaigns isolated for cleaner attribution
- avoid changing destination logic after large print distribution
- monitor app-open vs fallback ratio after deep-link updates
- if domain changes are required, validate QR dependencies before migration
- align QR naming with campaign naming to reduce reporting confusion.
- maintain a device test log for each high-volume QR campaign.
/user-guides/manual/growth/links-and-settings-reference/user-guides/manual/data/analytics-views-reference/user-guides/manual/data/conversions-customers