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.
What you save in Motif
On Websites, set a tracking host such as m.yourdomain.com and point a CNAME at collect.motiftrace.com. When the host is active, the snippet Motif shows uses that host instead of collect.motiftrace.com. The same file is /m.js; 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, so a proxy at /_m/m.js receives beacons at /_m/v1/events. Your existing TLS certificate covers it.
How to tell it is working
Insights reports first-party collection share: events whose collector host is this website's active tracking host, over events 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, remaining Direct / unknown has no referrer to recover.