Branded domains & email deep links
Real DNS verification against public resolvers — and the one thing it doesn't do yet, stated plainly.
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").
Verifying a domain doesn't yet route links through it
This is the one place in the product worth being blunt about: DNS verification is real and working, but no generated link URL uses a verified domain today — every link still resolves through the standard host. Verify a domain to confirm ownership and prepare it now; don't point external campaigns at it as the click URL yet.
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, so Universal Links and App Links have something correct to check against the moment routing does land on this.
Email deep links (ESP repair)
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.