custom domains in tracking script

[net47]

Currently (at least what I see) the tracking script uses the base domain for every website to be tracked.

.env file:

# Domain and URL Configuration
DOMAIN_NAME=rybbit.mydomain.com
BASE_URL="https://${DOMAIN_NAME}"

It would be great if this could be dynamic, so that tracking for website example.com would allow to use metrics.example.com even if the Rybbit base domain is still rybbit.mydomain.com. Off course, admins would have to make sure that traffic to metrics.example.com would then reach rybbit.mydomain.com using CNAME records, load balancers, etc...

Currently, you have to use for every website:

<script
    src="https://rybbit.mydomain.com/api/script.js"
    data-site-id="XYZ"
    defer
></script>

[timscha]

I would love to have that feature too. I tried to add multiple domains already in my nginx config, but when opening rybbit afterwards and trying to login I got the "Error Logging In Not allowed by CORS" message.

[zehjotkah]

would also love to be able to set multiple domains, so that for my different projects I could load the script and login into Rybbit from/via rybbit.website.com instead of having a 3rd party domain.

[Enjer]

Better to support TRACKER_SCRIPT_NAME and COLLECT_API_ENDPOINT variables like Umami, so we can use our own domains and bypass ad blocker.

https://umami.is/docs/bypass-ad-blockers

[HerrDerb]

Yes, this would be really nice.
I really would like to be able use my own application domain for the rybbit request. maybe also a change to rename the endpoint at all.