1. Validate association artifacts
Confirm AASA and assetlinks reachability before device tests so platform-level failures are caught early.
Deep link test checklist for iOS and Android launches
Deep links can appear healthy in one environment and fail in another. This checklist helps teams test installed-app routing, fallback paths, and attribution integrity before paid or lifecycle traffic scales.
Minimum deep link test matrix
| Scenario | Expected behavior | Must-pass check |
|---|---|---|
| iOS app installed | Universal link opens app route directly | Destination screen and parameters match test case |
| iOS app not installed | Fallback page loads with no redirect loop | Campaign parameters survive to fallback URL |
| Android app installed | App Link resolves to app route | Intent filter match and destination parity verified |
| Android app not installed | Fallback page or store route opens | No broken destination and no dropped parameters |
Execution order for release-day deep link testing
2. Test installed-app routing
Open production-intent links on physical iOS and Android devices and verify exact in-app destinations.
3. Test fallback and store behavior
Uninstall app variants and verify fallback pages or store destinations open with stable redirects.
4. Validate analytics parameters
Check that UTM/query parameters remain intact through every redirect and final destination.
Common breakpoints to monitor
- AASA or assetlinks files cached with stale content.
- App route names changed without matching link templates.
- Redirect policy strips or rewrites campaign parameters.
- Installed-app behavior passes, but fallback path is broken.
Related resources
- Deep link testing checklist - expanded QA workflow for product and release teams.
- Universal links troubleshooting - fix routing failures after test failures are reproduced.
- Attribution source checks - verify channel-level analytics fidelity after launch.