Multiple domains

[colmex]

Hi! I don't see anywhere for how to configure multiple domains? I see how to change the current domain, but what if I want to track a list of different domains that are all served from the same place.

[davidfiala]

In my experience, when you do the setup script, make that the name of the domain that you'll serve your analytics JS and the analytics dashboard from.

If you wanted: rybbit.foo.com then ./setup.sh rybbit.foo.com ....

After setup, goto https://rybbit.foo.com and create account and login.

Then, for every site you want to track, create a "site" inside of the rybbit dash. it'll give you a unique JS tag for each. ie, bar.com, baz.com and so on.

Note that due to a bug/open issue, if you want to track www.bar.com, then name the site bar.com without the www. prefix. Breadcrumb: #278 (comment)

[smileBeda]

If I understand the question correctly then @davidfiala gave the correct answer already, with the only difference that the "unique tag" basically is the site ID (as in 1, 2, or etc) and that's passed to the script when embedding it like <script src="https://your-rybbit-dash.tld/api/script.js" data-site-id="4" defer></script> - here data-site-id="4" being for example my 4th tracked site with rybbit.

You can add new domains on the "main page" of your rybbit instance, where it says "add website"

Please let us know if this was what you meant?

[colmex]

Yeah so I'm not using the self-hosted one. I could if that's the only way to add other websites to track.

I signed up on https://rybbit.io/. I was able to add a domain for my first site (i.e. https://stay.annwn.app) but I have a bunch of client sites I want to track that I serve from the same place, so yeah I'm wondering how to add them.

Here's what I see on the main page but I don't see that button anywhere

[smileBeda]

Adding #361 as a voice to it

[davidfiala]

A potential workaround is to use an nginx proxy and configure it to reply to CORS requests however you'd like. This would intercept and bypass any settings that are currently in rybbit.

In the event that rybbit still is checking the origin, then nginx could simply rewrite the Origin header as well.

But again, it's just a temporary workaround.

---

Long-term, I do believe that it is best (critical even) to implement a per property list of allowed CORS domains.

As a side note, it's important that we also allow one domain to be used across multiple properties (for instance, somebody might wish to allow localhost as an allowed origin on one or more properties, or perhaps for some reason they will have multiple tracking IDs all on the same origin as well on different pages).

I do appreciate that rybbit does enforce an origin mandate. This provides control for the analytics administrator to unilaterally shut down traffic from a misbehaving or unexpected source, rather than having to edit the HTML on a misbehaving page itself. For example, at times this might not be doable quick enough in the event that there is an incident. -- So I do hope that the origin restrictions remain in place. We just simply need to improve the implementation.

[goldflag]

Currently tracking multiple subdomains works. So demo.rybbit.io, staging.rybbit.io, and rybbit.io can coexist on the same siteId. That is what the new hostnames tab is for

However tracking unrelated domains under the same site Id is currently not possible. It can be added though.

[nellimonix]

I agree with this proposal. My project has 4 mirrors, on different domains, and I want to analyze statistics on all mirrors on one screen, without creating separate sites inside rybbit