Fictura
Links

iOS exact paths

How an iPhone tap on a Fictura link gets an exact match without IP guessing: custom product pages, a clipboard token, or a typed code.

The App Store passes nothing from a link to the app it installs. Fictura never guesses iOS installs from IP addresses, so an iOS install without one of the paths below is organic. Every path on this page gives an exact match. They work for iCloud Private Relay users too.

Pathmatch_typeBest forNeeds
Custom product pageproduct_pagePaid campaigns, creatorsiOS 18+, App Review per page
Clipboard tokenclipboardAny link that goes through a landing pageThe clipboard flow turned on, latest SDK
Typed codecodeBio linksA code screen in your app
Apple Ads tokenapple_adsApple AdsLatest SDK. See Apple Ads

An App Clip is planned as a later option.

A custom product page is a second App Store page for your app, made in App Store Connect, with its own screenshots and its own deep link. On iOS 18 and later, when someone installs from that page and taps Open, the app opens with the page's deep link. The SDK reads the cpp=<id> value from it and sends it as product_page_id.

  1. Make one custom product page per campaign or creator in App Store Connect, and give it a deep link. Each page goes through App Review.
  2. Put the page's id on the Fictura link as product_page_id.
  3. Point the link at that custom product page's App Store address.

Installs from older iOS versions, or where the person opens the app from the home screen instead of Open, don't carry the deep link.

Clipboard token

When the clipboard flow is on, an iPhone tap on /l or /w shows a short landing page:

  1. The person taps the button that opens the App Store. In that same tap, the page copies fct_<clickId> to the clipboard and shows it.
  2. On first launch the SDK checks the pasteboard with UIPasteboard.detectPatterns first. That check doesn't read the content and shows no paste banner.
  3. Only when it finds a probable fct_ token does it read it and send it as clipboard_token.

The copy happens only on the person's own tap, never on page load.

Typed short code

For bio links, where the tap happens inside an app's browser, the landing page shows a short code. The person types it into a screen in your app on first launch, and the SDK sends it with resolveWithCode(). See Bio links.

When the app is already installed

A tap by someone who already has the app opens it through a Universal Link and is reported as link_open. See Deep links in your app.

On this page