Deep links in your app
Save your app's identity, create a tracking link, and let a tap on it open your app and credit the install.
A tracking link does two jobs: it logs the tap, and it hands the tap's id to your app so the install is credited to the link. This page is what your app needs for that to work. It's step 4 of Setup, and your coding agent can do most of it. See the links overview for what a click does on the server.
1. Set your app's identifiers
In app.json:
{
"expo": {
"scheme": "myapp",
"ios": { "bundleIdentifier": "com.yourcompany.yourapp" },
"android": { "package": "com.yourcompany.yourapp" }
}
}A bundle ID is hard to change once the app has shipped, so pick it with care.
2. Save the same values in Fictura
Your bundle ID, Apple Team ID and Android package go in App identity, or your agent saves them with the MCP update_app_identity tool. Find the Team ID at developer.apple.com under Membership.
3. Add expo-linking
npx expo install expo-linkingThe SDK reads the link that opened your app by itself and sends its parameters with the next batch of events. Attribution needs no code of your own.
4. Create a link and tap it
Create one on the Links page, or your agent does with the MCP create_tracking_link tool. For a test, point it at your app's own scheme, like myapp://:
- Build a development build. Expo Go doesn't have your app's scheme, and Expo says a new scheme needs a new build:
npx expo run:iosornpx expo run:android. - Close the app fully. The SDK reads the launch link once, when the app starts.
- Open the link in your phone's browser, and allow it to open your app.
On a simulator, xcrun simctl openurl booted <the link> does the same.
The tap logs a click, the browser hops to myapp://?growth_slug=…&growth_click=…, and the app opens and reports it. Setup ticks A real tap reached your app.
For real campaigns, point the link at your store page instead. See How attribution works.
Opening your app without the browser hop
Universal Links (iPhone) and App Links (Android) open your app straight from the tap, with no browser in between. Both need a verified branded domain, because Apple and Google check a file on the domain itself. Once you have one, add it to app.json:
{
"expo": {
"ios": { "associatedDomains": ["applinks:go.yourapp.com"] },
"android": {
"intentFilters": [
{
"action": "VIEW",
"autoVerify": true,
"data": [{ "scheme": "https", "host": "go.yourapp.com", "pathPrefix": "/l" }],
"category": ["BROWSABLE", "DEFAULT"]
}
]
}
}
}Fictura serves both association files on your verified domain, built from your App identity. See Expo's guides to iOS Universal Links and Android App Links.
When the app is already installed
With Universal Links or App Links set up, a tap on a /l link by someone who already has your app opens the app directly. No redirect runs, so the server sees no click on its own.
The latest SDK reports these opens. For any link that contains /l/, /w/ or /r/, or growth_* parameters, it calls POST /api/v1/link-open. Fictura logs the click, records a re-engagement (or a first touch, if the install is only minutes old), and returns the link's deep_link_value. The SDK passes that value to onDeepLink, so you route the person to the right screen.
Older SDKs read only query parameters, not the /l/<slug> path, so with them these taps reach the app with no link data and show no click. Update to the latest SDK.