Domains, referrers and labels

The Data tab holds three lists. Two of them decide how your traffic gets attributed, and one just makes the interface easier to read.

Of everything in project settings, the domain list is the one most worth getting right on day one — it’s the only setting here whose effect can’t be applied retroactively.

Domains

Your project’s domains are listed with the primary one marked · primary. The primary domain is derived from your project URL and cannot be deleted. Add more with the form below the list (placeholder: app.yourproduct.com).

Why domains matter

The collector uses your domain list as an origin allowlist.

A browser event whose Origin isn’t in the list — or is missing entirely — is still accepted. It isn’t dropped. But it’s marked unattributed, and its referrer, UTM and attribution fields are stripped.

So you keep the traffic, and lose the story behind it. The visit counts; where it came from doesn’t. During setup, an event from an unlisted origin won’t show up on the test screen at all, which is usually how people discover the problem.

If you serve your app from app.yourproduct.com as well as yourproduct.com, add both. Otherwise every event from your app subdomain arrives with no source, no campaign, no referrer — and your sources table quietly under-reports the channels that drive real usage.

Marketing site on the apex, product on a subdomain, docs on a third host: that’s three entries, and all three need to be there.

This is the setting to fix before you accumulate data, not after. Stripped attribution isn’t recoverable — unlike your tracking configuration, which you can change retroactively any time.

Validation

Domains are normalized to a lowercase host. Scheme, www., port and path are stripped, so https://www.Example.com:443/app becomes example.com.

Rejected values:

Invalid input shows Invalid domain.

There’s no wildcard support, so subdomains are listed one by one.

Ignored referrers

A textarea — one host per line, or comma-separated. Saving replaces the whole list.

The help text: Domains that don’t count as a source (one per line): stripe.com, accounts.google.com…

The problem this solves

Payment and auth providers send users back to your site. Someone clicks your Google Ad, browses, checks out through Stripe, and lands on your confirmation page — with stripe.com as the referrer.

Without this list, Stripe shows up as a traffic source. That’s misleading. Stripe didn’t send you that customer; it handed them back. The user originally came from somewhere else, and that somewhere else is what you’re trying to measure.

Left unchecked, your best-converting “source” ends up being your own checkout flow — a number that’s true and useless at the same time.

Typical entries:

stripe.com
checkout.stripe.com
accounts.google.com
github.com
paypal.com

Add whatever your stack sends users through: payment processors, OAuth providers, SSO portals, email verification links.

Same host validation as domains, with one difference: invalid entries are silently dropped rather than raising an error. If a line doesn’t survive a save, it wasn’t a valid host.

Your own domains don’t need to be here — a referrer matching your own host is already ignored as internal navigation. See sources for the full classification order.

Event labels

Map an event name to a friendly display name:

account_created → Signup
ticket_purchased → Ticket sold
fv_project_created → First project

Your code keeps sending account_created; the interface shows Signup.

Display text is truncated to 60 characters, so keep labels short — they’re headings, not sentences.

Labels appear in:

• the Pulse stat strip,
• the journey funnel,
• chart titles,
• the portfolio cards.

This is presentation only. It doesn’t affect matching, counting, aliases or alerts — it changes what you read, never what’s measured.

Worth doing anyway. Snake_case event names are correct in code and slightly hostile on a dashboard, especially one you show to someone who didn’t write the instrumentation. A label costs ten seconds and makes the funnel legible at a glance.

A quick setup pass

1. Add every host you serve from — apex, app subdomain, docs, anything with the tracker on it.
2. Add your payment and auth providers to ignored referrers.
3. Label your conversion and first-value events.

Then check sources in a day or two. If your own domain or your payment provider is showing up as a source, something on this page needs another line.

Where to go next

• Sources — how attribution is classified
• Project settings — the other three tabs
• Conversions and activation — defining success
• Going live — the pre-launch checklist
• Troubleshooting — when events arrive but attribution doesn’t