Fictura
Links

Links overview

One redirect endpoint, one parameter contract, and no premium tier — the whole deep-linking suite is on for every app.

Dashboard → Links. A link is a slug plus a destination and a set of parameters that live server-side — edit the campaign, the destination, or the cost model on an existing link, and every future click picks up the change immediately, including on a link already printed on something physical.

What a click does

GET /l/<slug> is public — the slug is the credential:

  1. The click is logged (its ID rides the redirect, so attribution can resolve it later). Bots, link previews, HEAD requests and prefetches still get the redirect but are not logged as clicks. A slug only works on its own domain (or Fictura's default host).
  2. Android with a configured Play Store URL → redirects there with referrer=growth_slug=<slug>&growth_click=<id>, which the Play Install Referrer API hands back to the SDK on first launch. This is an exact match (gp_referrer). A gclid on the tap rides along in the referrer too.
  3. A computer (Windows, Mac, Linux or ChromeOS) → redirects to the link's desktop URL if it has one. Otherwise, when the destination is a store page or an app scheme a computer cannot open, it goes to your website from Settings > App identity. It carries the same parameters as step 4. A link whose destination is already a web page keeps it, and so does a Magic link. With no desktop URL and no website on file, a computer follows step 4. iPads on iPadOS 13 and later send the same browser string as a Mac, and Safari sends no client hints, so a Mac browser that gives no hints gets a small page that checks for a touch screen: an iPad goes on to the store and a Mac goes to the website.
  4. Otherwise → redirects to the link's destination, forwarding every incoming query param the destination doesn't already have (so fbclid/ttclid/gclid survive the hop), plus growth_slug, growth_click, and utm_source/utm_campaign when the link names a provider.

On iPhone there is no referrer, and Fictura never guesses an iOS install from its IP address. See iOS exact paths for the ways an iOS tap gets an exact match.

On first launch the SDK waits up to 3 seconds to read the launch URL, the Play Install Referrer and the other signals, then sends them with its first event batch. It re-sends them until the server confirms they were saved (attribution_saved).

A creator link is either Direct (the tap goes straight to the store) or Magic (the tap goes through your own website first, and the download button there comes back through the same link). Direct converts a little better because it is shorter; Magic gives the install a much firmer click to match against, which is what you want when you are paying for it. Magic links carry a plum badge in the Links table. See Magic links.

Web-to-app

Two separate mechanisms:

  • GET /w/<slug> — a hosted landing page with OG tags and store buttons that route back through /l/<slug>, so the tap still counts as a click. There's no link to it in the dashboard UI today; if you want it, construct it from the slug directly.
  • The smart banner — a script tag (Dashboard → Links → Web-to-app) that renders a dismissible top or bottom bar on your own site, forwards the page's UTMs plus fictura_placement=smart_banner, and serves only an explicit comment in the script (missing ?app=, banner disabled, tracking link not found) when something's misconfigured, so no bar appears.

Interstitial isn't wired yet

The banner offers three placements — top, bottom, interstitial — but the served script only ever renders top or bottom; picking interstitial alone silently produces a bottom bar. Pick top or bottom.

Bulk creation

A rows × columns matrix (e.g. creators × channels) generates one link per cell — up to 500 pairs per request, in a single transaction, all or nothing. Slugs are random rather than derived from the row/column names on purpose, so a batch can't be walked by guessing.

Inspect

Paste any URL — yours or a third party's — and get back its parsed parameters and, if it's one of your own links, the routing table it would actually produce (Android without the app, iOS without the app, app installed, desktop) and whether each path gives an exact match. No network request is made; it's read entirely off the link's own stored configuration.

On this page