How to test app links inside Instagram
Test the published placement on real iPhone and Android devices, and keep a short record of the route, prompts and final destination.
19 October 2026 · PAD team
On this page
Prepare one test record per journey
Use the same campaign link you intend to publish. Choose a test audience appropriate for your account. Do not send an unfinished campaign to customers simply to check its destination.
Date and time:
Published placement: profile / Story / message / ad
Shared URL:
Phone and OS version:
Instagram version:
App installed: yes / no
Expected destination:
Observed destination:
Prompt or extra tap:
Campaign parameter retained: yes / no / not checked
Result and evidence:Run the cases that your campaign needs
| Case | What to verify |
|---|---|
| iPhone, app not installed | Correct App Store listing and an actionable fallback if needed |
| Android, app not installed | Correct Google Play listing and an actionable fallback if needed |
| App installed, when app opening is configured | Intended app screen or the documented fallback |
| Desktop | Useful website destination |
| Original URL after a destination edit | The existing campaign path still routes correctly |
These are test cases, not measurements from a GoToApp device study. Record your own results and versions. A route that passes once can still behave differently for another account, app version or device.
Test from the placement
- Open the published profile, Story, message or ad preview inside Instagram.
- Tap the link as a visitor and follow any prompt or manual button.
- Record the final app or page. If a screen recording contains personal information, remove it before sharing.
- Compare a failed case with the exact same URL in Safari or Chrome.
- Check the resulting campaign parameters separately; arriving at the right listing does not establish correct attribution.
Decide whether to launch
A failed required platform is a reason to fix the destination or provide a working alternative before launch. A successful test is evidence for that tested journey, not a percentage delivery guarantee. Keep manual test results separate from automated requests in your dashboard.
When reporting a problem, include the smallest reproducible case. The Story checklist and browser checklist help separate placement, destination and handoff problems.
Set up your link
Create a dedicated campaign link, then keep this worksheet with your launch checklist.
Questions
Can a desktop link checker replace phone testing?
No. It can inspect HTTP routing but cannot confirm the phone’s store handoff, prompts or app-opening behavior.
Should I test with the app installed?
Yes when your campaign intends to open an installed app. Also test the new-user store journey.
Create a GoToApp link with your destinations, then test it on the devices and channels you plan to use. Free for up to three projects.