Custom tracking domains

Configure a hostname#

Open the site's tracking-domain settings and choose a subdomain belonging to the site, such as analytics.example.com. An unrelated hostname is rejected. Remove the existing tracking domain before replacing it with another.

Add both DNS records#

Use the exact TXT ownership token and CNAME target displayed by Weeveo. The TXT name is _weeveo.<tracking-hostname>. Do not reuse another site's verification token. DNS propagation can take time; recheck the authoritative values before retrying.

Verify and activate#

Choose Verify. Weeveo checks both records, provisions the supported Cloud Run mapping, then checks HTTPS ownership before activation. pending_https means the domain is not ready for installation yet. Self-hosted operators need the Cloud Run project, service, region and mapping permissions configured for this provisioning flow.

Reinstall the snippet#

Once active, copy the updated installation snippet. Check both script and collection requests use the intended host. If you remove the custom domain, reinstall the standard-host snippet first and remove obsolete DNS records afterward.

API equivalents#

Use get_tracking_domain, set_tracking_domain, verify_tracking_domain and remove_tracking_domain. Domain changes require administrator access and write consent.