Product reference
Product capabilities and limitations
Use this page to confirm what Smart Linker supports, what it does not support, and where install routing ends. It is a public trust reference for the product boundaries that matter to customers and operators.
What you can confirm here
- What Smart Linker can route.
- Which routing flows are supported.
- Which analytics are available.
- What Smart Linker intentionally does not provide.
- Where install routing ends and deep linking or attribution begins.
Governed product reference
This reference stays aligned with Smart Linker’s governed public capability boundaries.
- What this page helps you confirm
- What Smart Linker can route, which routing flows are supported, which analytics are available, and what it intentionally does not provide.
- Boundary
- Install routing ends where deep linking, attribution, and native app-opening behavior begin.
- Truth rule
- Runtime mismatches are governance defects and must be resolved before the next governed release.
Product overview
Smart Linker is a smart-link service for mobile app distribution. It keeps one public URL stable while the routing target behind that URL can be edited later.
Contract stability
This surface only carries stable, user-visible, governance-relevant behavior. It does not commit roadmap items, speculative future capabilities, or temporary implementation details.
Core capabilities
- Stable public link
- One public URL can stay in campaigns, bios, QR assets, and landing pages while the destination behind it remains editable.
- Device-aware routing
- The resolver sends iPhone traffic to the App Store, Android traffic to Google Play, and desktop traffic to the configured web fallback or public fallback page.
- QR support
- A QR code can point at the same Smart Link, so the printed surface stays stable while the destination behind it can change later.
- Public fallback behavior
- If a requested destination is missing, Smart Linker can render a public fallback page instead of inventing a redirect target.
Supported routing flows
| Context | Behavior |
|---|---|
| iPhone | App Store destination when configured, otherwise the public fallback page. |
| Android | Google Play destination when configured, otherwise the public fallback page. |
| Desktop | Web fallback when configured, otherwise the public fallback page. |
| QR scan | The same public Smart Link can be encoded in a QR asset and routed by device at scan time. |
Editable destination behavior
The public URL is stable by design. Operators can update store and fallback destinations later without reissuing the public link everywhere it appears.
Analytics and exports
Free keeps 3 active smart links, 2,000 redirects/month, and recent link activity. Pro includes unlimited smart links, unlimited redirects, custom domains, advanced analytics, and CSV export. Supported labels are Total traffic, Link clicks, QR scans, Routing quality, Traffic over time, Traffic mix, Routing & referrers, Top referrers, Fallback page, and Direct / unknown. CSV export is aggregate-only and excludes raw click rows, IP addresses, user agents, full referrer URLs, user IDs, click IDs, and per-click timestamps.
Public-link model
Smart Linker is intended for one public link that can serve campaigns, social bios, partner placements, QR codes, and launch pages without forcing visitors to choose a platform first.
What Smart Linker intentionally does not provide
- No deferred deep linking guarantees.
- No SDK attribution platform.
- No runtime AI-generated routing.
- No ad-network attribution system.
- No hidden redirect cloaking.
- No analytics surveillance platform.
Architecture and governance boundaries
- This page is the public rendering of the canonical capability contract, not a pSEO page.
- It is self-canonical and sitemap-controlled.
- It does not add runtime-generated content or localization variants.
- It does not commit roadmap items or speculative future capabilities.
- It does not change redirect semantics, analytics behavior, or indexing policy.
Security and privacy posture
Smart Linker routes public traffic deterministically on the server. It does not expose private account data through this page, and it does not claim cloaked or hidden routing behavior.