LinkSense turns one short link into the right destination for every visitor: iOS lands in the App Store, Android in Google Play, desktop on a hosted landing page you never have to build. Deep-link straight into your app, keep context through install with deferred deep linking, and see every click by device, country and source. Native iOS and Android SDKs, a REST API, custom domains, and sub-50ms routing from 348 edge cities. Free tier, no card.
Hey Product Hunt 👋
I built LinkSense after watching the same thing happen too many times: you share your app, someone opens the link on desktop, and they land on an App Store page they can't install from. Or they tap a link to a specific screen, get sent to the store, install, and open to a generic home screen with all the original context gone.
Every fix I tried was either a weekend of glue code per campaign, or an enterprise attribution platform priced for a company much larger than mine.
LinkSense is one link that works the rest out:
- iOS → App Store, Android → Google Play, desktop → a hosted landing page generated from your store listing, so there's nothing to build
- Deferred deep linking, so the destination survives the install and the first open lands where the user meant to go
- Resolution at the edge — sub-50ms from 348 cities — with native iOS and Android SDKs and a REST API on the same contract
- Click analytics by device, country and source
The free plan is a real one: 1 project, 1,000 links, device routing, social previews, your own subdomain. No card.
The part I'd most like your read on: deferred deep linking is the piece everyone implements differently. Install Referrer on Android is reliable. iOS leaves you choosing between the clipboard (accurate, but users see the paste banner and it feels invasive) and probabilistic fingerprinting (invisible, and wrong some of the time). We default clipboard off and fall back to fingerprinting. If you've shipped install attribution: where did you land on that trade-off, and did your users ever notice?
Jan