Claiming the Result

Set a deep link scheme in the funnel's settings and the success screen offers a link that opens your app directly. The link carries the token and the project (packages/shared/src/funnel/claim-link.ts:25-26, apps/api/src/services/funnel/claim-links.ts:44-46):

yourscheme://onboarding-complete?token=<token>&project=<projectId>

Handle that URL in your app and pass the token to claimFunnelToken. The /confirm response hands this link to the success screen alongside the token (apps/api/src/services/funnel/claim-email.ts:9-10).

Set a universal link domain and the success screen offers an https link instead: https://<domain>/universal/funnels/open/<token> (packages/shared/src/funnel/claim-link.ts:22, packages/shared/src/funnel/claim-link.ts:29-31). The link is served by the API under /universal (apps/api/src/app.ts:261, apps/api/src/routes/public/funnel-universal.ts:52-53), so the domain has to reach the API.

What the landing does depends on who opens it: an Android user agent redirects to the Play Store with the install referrer carrying the token, an iOS one stashes a deferred fingerprint row and redirects to the App Store, and anything else gets a page with both store links (apps/api/src/routes/public/funnel-universal.ts:87-92, apps/api/src/routes/public/funnel-universal.ts:94-121, apps/api/src/routes/public/funnel-universal.ts:124-128).

If the app was not installed yet, there is nothing to open. After a fresh install the SDK can ask whether a recent visit belongs to this device:

• Android reads the Play install referrer, which the universal-link landing wrote (apps/api/src/routes/public/funnel-universal.ts:7-9). The referrer is authoritative: a token in it is looked up and handed straight back (apps/api/src/routes/v1/funnel-claim.ts:557-569).
• iOS matches on a hashed IP, and only when exactly one unclaimed visit matches — never a device fingerprint, and never a guess between two (apps/api/src/routes/v1/funnel-claim.ts:572-586).

The window is one hour from the visit (apps/api/src/routes/public/funnel-universal.ts:50). The success screen's CTA also writes a clipboard marker the app can read on first launch — the deferred handoff for a fresh install (apps/dashboard/src/runner/clipboard.ts:2-10, apps/dashboard/src/runner/funnel-runner.tsx:1356-1361).

For a buyer who closed the tab. Two ways in:

Rovenue emails them. When the Stripe webhook completes the purchase first — a closed tab, a phone that slept — the token is minted with nobody there to receive it, and the buyer is emailed the same link the success screen would have shown (apps/api/src/services/funnel/claim-email.ts:9-19, apps/api/src/services/stripe/stripe-webhook.ts:484-496). This needs the funnel to have a deep link or a universal link configured; without one there is nowhere to send them, and no email goes out (apps/api/src/services/funnel/claim-email.ts:40-49).

The app asks. Your app can also ask Rovenue to look up an email; if there is a match, Rovenue emails a magic link that opens the app. That call always answers 202 with a null body whether or not a match existed, so it cannot be used to test which addresses have bought (apps/api/src/routes/v1/funnel-claim.ts:610-614, apps/api/src/routes/v1/funnel-claim.ts:633-638).

let token = "<token from the opened URL>"
let result = try await Rovenue.shared.claimFunnelToken(token)
print(result.subscriberId)
print(result.funnelAnswersJson)

Or observe claims resolved by any path on Rovenue.shared.funnelClaims (packages/sdk-swift/Sources/Rovenue/Rovenue.swift:949).

val token = "<token from the opened URL>"
val result = Rovenue.shared.claimFunnelToken(token)
println(result.subscriberId)

Rovenue.shared is the configured instance (packages/sdk-kotlin/src/main/kotlin/dev/rovenue/sdk/Rovenue.kt:206-208); funnelClaims streams claims resolved by any path (packages/sdk-kotlin/src/main/kotlin/dev/rovenue/sdk/Rovenue.kt:905).

import { Rovenue } from "@rovenue/react-native-sdk";

const openedUrl = "<the URL that opened the app>";
const token = "<token from the opened URL>";

// One call that tries the lot: the opened URL, then the deferred match.
const claim = await Rovenue.resolveFunnelClaim({ url: openedUrl });

// Or redeem a token you already have:
const result = await Rovenue.claimFunnelToken(token);

resolveFunnelClaim runs the no-gesture chain — the deep link, then the platform deferred match — while the clipboard and the email link stay gesture fallbacks you surface yourself (packages/sdk-rn/src/api/funnel.ts:141-157).

const token = '<token from the opened URL>';
const openedUrl = '<the URL that opened the app>';

final result = await Rovenue.instance.claimFunnelToken(token);

// Or let the SDK read the token out of the URL that opened the app:
final claim = await Rovenue.instance.claimFromUrl(openedUrl);

(packages/sdk-flutter/rovenue_flutter/lib/src/rovenue.dart:29, packages/sdk-flutter/rovenue_flutter/lib/src/rovenue.dart:299, packages/sdk-flutter/rovenue_flutter/lib/src/rovenue.dart:337-340).