Basic store routing and click analytics need no mobile SDK. You can use the AppRoute dashboard to set up a smart link without changing your mobile app or shipping an app update. If your goal is to share one link that routes visitors to the right app store and see its clicks, start with smart routing setup.
01 Which problem am I solving?
Separate store routing, in-app navigation, automation and revenue attribution before choosing an integration.
| Your goal | Capability to consider | What to check first |
|---|---|---|
| Send visitors to the right app store and see clicks | Store routing and click analytics | Start in the dashboard; basic routing needs no mobile SDK. |
| Open a specific screen or piece of content inside your app | Deep linking | Check your app’s navigation requirements and the association setup for each platform. |
| Automate work from your own systems | API integration | Confirm that the API supports the workflow you need. |
| Connect an individual link click to revenue | Click-based revenue attribution | This is coming soon; overall revenue imports serve a different reporting need. |
A deep link points to content inside an app. Android App Links add a verified association between a website and an Android app. Choosing that path requires checking your app’s configuration; don’t assume a store-routing link establishes the association for you.
02 What can I set up without a release?
Configure your store URLs and website fallback in the dashboard, then test the link where you plan to share it. Basic store routing and click analytics need no mobile SDK or change to your app, so you can set up this path without shipping a new release.
- Add your store destinations. Set the App Store listing for iPhone visitors and the Google Play listing for Android visitors. Check that each URL points to the app you intend to promote. The smart routing setup explains the routing path.
- Choose your website fallback. Set the web page that other devices should reach. Open that destination separately and check that it gives visitors a useful next step.
- Open the same smart link on each device. Check where it lands on an iPhone, an Android device and a desktop browser. Record the expected destination beside the actual result so you can spot a wrong listing or fallback.
- Repeat from your intended placements. Open the link from the bio, email or other placement you plan to use. Check the destination again from that starting point before sharing it more widely.
Use these checks as a pre-share checklist. If any destination is wrong, review the dashboard URLs and repeat the affected check before publishing the link.
03 What should I confirm before integrating?
Confirm the supported platform and release, authentication method, and test requirements before adding an API or SDK integration. Ask for instructions specific to your account and use case; don't assume that a package, version, or feature is available on both iOS and Android.
Send support your integration requirements, including the job you need it to do.
Use these questions to make the integration scope concrete:
- Which platforms and versions are supported for this use case, and which release should I use?
- What authentication is required, and where should credentials be stored?
- Which data fields must I provide, and what does each field represent?
- Which device states and failure cases should I test before release?
- How should I handle retries, duplicate requests, and failures?
If store routing and click analytics cover your needs, start with the dashboard setup. If you need an API or SDK integration, use the confirmed instructions to define what you'll build and how you'll check it.