Custom domain (CNAME)
This is one DNS record, and it's probably the highest-leverage ten minutes you'll spend in SetRoasFlow.
What it does
By default your events travel to custom.setroasflow.com. That works, but to a browser it's a third-party domain, and third-party is exactly what the modern web is built to block.
Point a subdomain of your own store at us instead:
data.yourstore.com → custom.setroasflow.comNow the same traffic is first-party. Same data, same code, but the browser treats it as your own site talking to itself.
Why it matters, concretely
Ad-blockers stop recognising it. Blocklists work on known tracking domains. data.yourstore.com isn't on any list; it's yours. Between 15% and 30% of DTC traffic runs an ad-blocker, and those conversions currently never arrive.
Safari stops truncating your cookies. Under Intelligent Tracking Prevention, a cookie set by a third-party script is capped at 7 days. Set from your own domain server-side, it survives far longer. On a 30-day consideration cycle that's the difference between attributing a purchase and losing it.
Attribution windows stay intact. Click IDs (fbclid, gclid, …) captured on day one are still there on day twenty-eight.
You don't lose anything by skipping it. You just leave conversions on the table.
Set it up
- Open your site under Websites, and in its configuration find Custom tracking domain (CNAME) → enter the subdomain you want (
data.yourstore.com,t.yourstore.com, anything you like). - Add the record shown, in your DNS provider:
| Type | Name | Value | Proxy |
|---|---|---|---|
| CNAME | data | custom.setroasflow.com | DNS only |
- Wait for propagation (usually minutes, up to a few hours). The page shows the live status.
- Once it's Active, the snippet on the Installation page updates by itself to use the new domain. Re-paste it on your site (or re-save in the plugin) so the change takes effect. See Install the tracking.
The TLS certificate is issued and renewed automatically. There's nothing to maintain.
Choosing a subdomain
Anything works, but avoid words that pattern-matching blockers look for. analytics., tracking. and pixel. are the obvious ones to skip.
Good: data., t., evt., srf., api.
Use a subdomain, never your root domain. yourstore.com must keep pointing at your store.
Common problems
| Symptom | Cause | Fix |
|---|---|---|
| Stuck on Pending | DNS hasn't propagated | wait; check with dig data.yourstore.com |
| Invalid | record points somewhere else, or is proxied | value must be custom.setroasflow.com, DNS-only (on Cloudflare: grey cloud, not orange) |
| Events stopped after activating | the site still has the old snippet | re-paste it from Installation |
| Certificate error | issuance hasn't finished | it completes automatically a few minutes after the DNS resolves |