How-to

Deep link inspection workflow for release-ready routing

Deep link inspection closes the gap between "link opens" and "link is launch-ready." Use this workflow to verify platform resolution, fallback behavior, and attribution-safe parameters before traffic scales.

Inspect universal links Validate UTM parameters

Four checks every deep link inspection should include

Inspect platform resolution

Confirm iOS resolves with universal links and Android resolves with App Links for installed-app scenarios.

Inspect fallback routing

Uninstall app variants and verify web/store fallback destinations with no redirect loops.

Inspect parameter integrity

Check that UTM and source parameters persist through redirects to final destination.

Inspect destination parity

Validate that destination routes match the exact in-app screen and web page intended for each channel.

Inspection matrix for iOS and Android

Scenario	Expected route	Inspection evidence
iOS app installed	Universal link opens the exact in-app screen.	Validated destination route and preserved query parameters.
Android app installed	App Link resolves to the expected Android intent route.	Verified intent route parity and no intermediate misrouting.
App not installed	Fallback opens correct web or store destination.	Checked fallback status, destination URL, and parameter integrity.
Android emulator QA	Test link reproduces platform routing behavior consistently.	Captured emulator result and compared against real-device checks.

Common inspection misses

Only validating one platform while the other uses stale route rules.
Passing route checks but missing dropped UTM/source parameters.
Skipping fallback tests after redirect rule or CDN changes.
Testing staging links only, then shipping unverified production domains.