One app, two stores
Configure the iOS listing, Android listing and a website fallback. Test all three paths; the fallback should explain your app to people who cannot install it on their current device.
Practical app-link setups
These are example setups to configure and test in the dashboard, not importable rule files or verified campaign results.
An app on one platform
Set the store destination your app supports. Use your website for other visitors instead of directing them to an incompatible store listing.
Separate campaign placements
Create distinct links or consistent campaign labels for placements you want to compare. Follow the UTM naming guide and test each final URL.
Custom routing
Use the controls available in your dashboard for the audience you want to reach. Record each intended match and fallback, then test them. Do not assume an example from another tool maps to AppRoute’s configuration.
App-link launch checklist
Copy these steps into your launch notes. This covers the link journey; it is not a complete app-store submission or product-launch checklist.
- Copy the full public App Store and Google Play URLs for the correct app.
- Choose a website fallback for other devices and missing store destinations.
- Save the link and record its short URL before adding it to campaign material.
- Open the short URL on iPhone, Android and desktop; record the actual destinations.
- Repeat from the social app or browser where the campaign will appear.
- Check unsupported devices and any custom rules you have configured.
- Review campaign tags, expiry, passwords and click limits that apply to the link.
- For QR placements, scan the final printed size on both iOS and Android.
- Check click reporting after the test and identify QA traffic in your notes.
- Repeat destination checks after editing the link and before a wider rollout.
| Visitor context | Expected destination | Observed result | Pass / follow-up |
|---|---|---|---|
| iPhone browser | Your configured URL | To test | To record |
| Android browser | Your configured URL | To test | To record |
| Desktop browser | Your configured URL | To test | To record |
| Social app browser | Your configured URL | To test | To record |
| Printed QR | Your configured URL | To test | To record |
A successful redirect confirms that the tested link reached a destination. It does not prove an installation or purchase. Read click reports with that distinction in mind.
Keep exploring