Fictura
Attribution

How attribution works

Every install gets one first touch. Exact matches always win, iOS is never guessed, and every row says how sure it is.

Dashboard → Attribution. Every install gets one first-touch source. Each answer is labelled with how it was found: exact, weak or modelled. An install with no answer is organic.

What counts as an install

An install starts when a device first reaches Fictura: the first SDK event batch, or a /v1/resolve call. That moment is the install time (install_at). It is set once and never moves.

Server-side sources never create an install. A RevenueCat webhook, a web checkout, a claim, a push token, a placement call or an import can attach to a person who already exists, but none of them makes a new install.

  • Reinstalls are reported on their own, not as a second install. The SDK keeps an install id in normal app storage, which is deleted on uninstall, and a device id in the Keychain, which is not. When the device id is there but the install id is gone, the install is a reinstall.
  • Test devices never count. See Fraud and test devices.
  • Fraud-flagged installs are kept, but left out of non-organic counts and payouts.

Match types

match_typeKindPlatformHow it is captured
gp_referrerexactAndroidThe Play Install Referrer carries growth_click / growth_slug from the /l redirect.
meta_referrerexactAndroidThe Meta Install Referrer, decrypted on the server. See Fraud and test devices.
apple_adsexactiOSThe AdServices token, exchanged with Apple. See Apple Ads.
click_claimexactanyA verified click id your app claims after sign-in.
link_openexactanyA Universal Link, App Link or /l path opened in the app.
clipboardexactiOSAn fct_ token the landing page copied, found by the SDK. See iOS exact paths.
codeexactiOSA short code the person typed (bio links).
product_pageexactiOSA custom product page deep link (cpp=<id>).
ad_idexactanyThe IDFA (only with ATT permission) or GAID equals the ad id on a click.
link_paramsexactanyA click id in the launch URL, inside the link's click window from install time.
utmweakanyRaw UTMs with no click id.
modelledmodelledAndroid, webAn IP match to a recent click. Rules below.

Older rows can show types from before the current rules: probabilistic and view_through read as modelled, legacy reads as weak.

Which answer wins

  • An exact match always replaces a weak or modelled one. The old answer is kept as a contributor. Up to 3 contributors are kept per install.
  • An exact row is never replaced.
  • A click id credits one install only. A shared URL with a click id in it can't credit a second phone.
  • Ties go to the most recent touch.
  • No answer means no row: organic is the absence of an attribution row.

Windows start at install time

Every window is measured from install_at, not from now.

  • A touch more than 5 minutes after install time is never a first touch. It may count as a re-engagement instead.
  • A touch older than the link's click window (click_lookback_days, default 7) is rejected.

So a person who installed in August and taps a link in November stays organic for August.

No guessing on iOS

Fictura never matches iOS installs by IP address or device traits. Apple's rules forbid it, so every iOS install is exact or organic. To get an exact answer on iOS, use the paths in iOS exact paths, Apple Ads and SKAdNetwork.

Modelled matches (Android and web only)

When nothing exact arrives, Android and web installs can fall back to an IP match:

  • Only clicks in the 60 minutes before install time.
  • Same platform only. A click from a computer never matches a phone.
  • One install per click.
  • A confidence score from 0 to 1 is stored on the row. Exact rows have confidence 1.
  • A modelled match never pays an affiliate or creator.

IP addresses are hashed before they are compared. See Privacy.

Claiming a click by hand

On iOS a tap can open Safari and go through the App Store before your app runs, so the SDK can't always see the click at launch. When your app gets a growth_click id from a link, or a signup started on the hosted landing page (/w/<slug>), claim it once the user is signed in:

Anywhere after the user is signed in
import { claimAttribution } from "@fictura/sdk";

const claimed = await claimAttribution(growthClickId); // boolean

The claim is click_claim, an exact match. It attaches to the existing install and never creates one. If the server doesn't know the device yet, it answers unknown_user and the SDK tries again after its next batch is saved.

Re-engagement

A person who already has the app is not re-attributed. A tap from them, or a link marked is_retargeting, writes a separate re-engagement record. It never changes the first touch, so revenue is never counted twice between the original source and a win-back campaign. Retargeting rows never count as installs.

When someone who already has the app taps a /l link, the app opens directly. The latest SDK reports that open with POST /api/v1/link-open and gets back the link's deep_link_value for onDeepLink. See Deep links in your app.

What the SDK reads back

onConversionData gives the current answer with its match_kind and confidence. may_still_resolve is true while the answer is weak or modelled and the install is under 48 hours old, because an exact signal can still arrive. A user with no identity yet reads back as pending, not organic.

Past numbers

Numbers from before the current rules went live are frozen, not recomputed. Charts on the dashboard draw a New counting rules marker on the day the rules changed, so a step in a chart there is explained.

On this page