Branded domains & email deep links
Real DNS verification against public resolvers, and links built on your own domain once it passes.
Dashboard → Links → Domains.
Branded domains
POST /api/v1/acquisition/domains with your host returns the exact two DNS records to publish — a CNAME and a TXT verification token — so nothing needs to be constructed by hand:
CNAME <your-host> → <edge host>
TXT _fictura.<your-host> → fictura-verify=<token>Verification is a genuine DNS read, not a self-assertion: both records are resolved independently against public resolvers, and a missing record reads as "not published yet" rather than an error, with a specific reason when something's wrong (e.g. "the CNAME points at X instead of Y"). A claim lasts 7 days. A domain not verified by then shows as expired and can be renewed.
Where a verified domain is used
Once a domain is verified, the Links page builds your links on it: the copy button, the QR code and the CSV export. Links the agent mints use it too. The url field in the links API's responses still uses the standard host. Old links keep working.
Every verified domain gets a managed TLS certificate. If a security rule says the private key must come from your own certificate authority, use Custom certificate on the domain's row: Fictura generates the key and a CSR, you upload what your CA signed, and renewing it on time becomes your job.
App association files (apple-app-site-association, assetlinks.json) are served automatically once a domain reaches verified and your app's team ID / bundle ID / package name are configured in the App association panel on this tab, so Universal Links and App Links have something correct to check against.
Email deep links (ESP repair)
Not in the dashboard right now
The Links page no longer has an Email section, so there is no screen for the pairing and the trace described here. The endpoints behind them (/api/v1/acquisition/esp, /api/v1/acquisition/esp/trace) still exist and take a dashboard session.
The problem: most email platforms rewrite your links onto their own click-tracking domain — click.<esp>.com — which isn't yours, so a device can't match it to your app and the tap opens a browser instead.
What this does — and what it doesn't. Fictura can't sign association files for your ESP's domain; only the ESP can serve those. What it provides is the pairing plus a live check:
- Pair your ESP (Klaviyo, Mailchimp, Braze, Iterable, Customer.io, or SendGrid) with one of your verified domains.
- Set your click-tracking domain to that host in the ESP's own settings — the dashboard shows the exact path for each provider.
- Trace a real link — the dashboard walks the actual redirect chain server-side, up to 8 hops, and tells you plainly whether it ends at your app or not. Only status codes and the hop chain are read; response bodies never are.
This is verification, not automation — nothing here talks to your ESP's API, and there are no ESP credentials stored anywhere.