First-party tracking host

Brave and other privacy browsers can drop third-party sendBeacon to collect.motiftrace.com while still reporting success. First-party collection is how Motif still sees those visits.

A website and a collector under one roof, with a spare box unused in the corner.

What you save in Motif

Every website starts with m.yourdomain.com as its tracking host. Point a CNAME at collect.motiftrace.com. DNS hosts that support Domain Connect, such as Cloudflare, do this in one click. Then click Check DNS on Websites. When the host is live, the snippet that Motif shows loads from it. Motif never puts an unverified host in the snippet. The file is /m.js, and events post to /v1/events on that host.

Reverse-proxy path

You can also proxy a path on your existing domain. The tracker posts v1/events relative to the script URL. Thus a proxy at /_m/m.js gets beacons at /_m/v1/events. Your existing TLS certificate covers that path.

How to tell it is working

Insights shows first-party collection share. This is the events whose collector host is this website's active tracking host, divided by the events that Motif stored. If that share is low after you saved a host, the snippet on the site still points at Motif's shared host. If the share is already high, the remaining Direct / unknown has no referrer to recover.