Listen for incoming links
After initializing the SDK withInvytoDeeplink.init(), you can listen for incoming link open events. The exact API depends on the invyto_deeplink package; a typical pattern is a stream or callback of URI or path + query.
Example (adapt to your package’s API):
invyto_deeplink documentation for the exact method names (onLinkReceived, getInitialLink, etc.).
Deferred deep linking
If the user did not have the app installed when they clicked the link, they are sent to the store. After they install and open the app, you still want to show the same content (e.g. the sale page). This is deferred deep linking.- First launch after install — The DeepLink backend stores the click (and UTM/path) and matches it to the install (e.g. via Track Install or SDK init).
- SDK or API — On first launch, the SDK or your call to the Track Install API returns attribution (e.g. path, UTM). Use that to navigate the user to the right screen.
- User taps
https://yourapp.deeplink.com/sale?utm_campaign=summer. - User goes to store, installs, opens app.
- Your app calls
InvytoDeeplink.init()(or Track Install API); the backend returns something like{ "path": "/sale", "utm_campaign": "summer" }. - Your app navigates to the sale screen and can log the campaign.
invyto_deeplink API; use the initial attribution payload to drive the first navigation.
UTM and query parameters
DeepLink links can include UTM and custom query parameters. When you handle a link (or deferred deep link), readuri.queryParameters or the attribution response and pass them to your analytics or routing:
utm_source,utm_medium,utm_campaign,utm_term,utm_content- Any custom keys you add when creating the link in the dashboard
Next steps
- Create links in the Dashboard and set paths and UTM.
- Use the Track Install API to record installs and get attribution if you are not using the SDK for that.

