GUIDE
When Smart Linker is enough
Smart Linker is enough when your team needs one public URL that routes people to the App Store, Google Play, or a web fallback. When the job expands into native deep linking or attribution, use the tools built for that job. For the routing-vs-deep-link boundary, see app install links vs deep links.
Direct answer
Smart Linker is enough when routing is the job. It is not enough when you need app opens, deferred deep linking, attribution, or mobile measurement partner (MMP) workflows.
Smart Linker is enough when
One public URL is needed
Keep one shareable link across campaigns, QR codes, websites, and support materials.
Device routing is the job
Send each visitor to the App Store, Google Play, or the configured web fallback.
Destinations should remain editable
Change targets later without replacing the public URL everywhere it is used.
QR-ready links are needed
Use one public URL in print and offline materials while keeping the routing flexible.
Custom domains are useful
Use a branded domain when trust and consistency matter in public-facing assets.
Aggregate analytics are sufficient
You need simple click visibility, not visitor-level reporting or attribution.
Smart Linker does not require an SDK for routing.
Smart Linker is not enough when
- Native app screen opening is required
- Deferred deep linking is required
- Attribution or postbacks are required
- Cohorts, ROAS, or LTV reporting are required
- MMP workflows are required
- SDK-based routing or measurement is required
Decision table
| Need | Smart Linker fit | Better fit when needed |
|---|---|---|
| One public install-routing URL | Yes | No additional platform is required |
| QR-ready distribution | Yes | A custom domain may help with trust and recognition |
| Deferred deep linking | No | Native links or an attribution platform |
| Attribution / postbacks | No | Branch, AppsFlyer, or another mobile measurement partner (MMP) |
| Native app screen opening | No | Apple Universal Links or Android App Links |
Examples
Launch card
Use one public link on a launch card when the goal is routing, not measurement depth.
Support email
Send one link in support replies so the customer lands where their device makes sense.
Printed QR poster
Keep one QR asset stable while the destinations behind it stay editable.
Brand-aware public link
Use a custom domain when the visible link should be easier to trust and remember.
Official docs for native links
Apple’s Universal Links documentation explains the native iOS setup for opening installed apps from verified links.
Apple Developer: Supporting universal links in your appAndroid’s App Links and deep links docs explain the native Android setup for verified app-domain links.
Android Developers: App Links and deep linksFAQ
Answers are visible by default for quick scanning.
When is Smart Linker enough?
Smart Linker is enough when you need one public URL for App Store, Google Play, and web fallback routing, plus editable destinations and basic aggregate clicks.
When is Smart Linker not enough?
It is not enough when you need native app screen opening, deferred deep linking, attribution, postbacks, cohorts, ROAS/LTV, or MMP workflows.
Do I need an SDK for Smart Linker routing?
No. Smart Linker handles the routing job without requiring an SDK.
Does a custom domain add attribution or deep linking?
No. A custom domain can improve recognition and trust, but it does not create attribution or deep-link behavior by itself.
Use the routing tool when routing is the job
Keep the routing layer simple, and leave attribution or native deep-link work to the platforms built for it.
Create your Smart Link