Way to track all domains (wildcard tracking)

[zmweske]

Hello, I was digging into this neat project and I was wondering if there is a way to track all subdomains (i.e. *.example.com) where each one is a new individual site, rather than needing to create a new config for each subdomain (cloud.example.com, files.example.com, misc.example.com, etc). It doesn't seem like there is a way to support any form of this right now, but I wanted to make sure and suggest the feature if it does not currently exist.

[Rau-N]

Hi there @zmweske! Thanks for the suggestion.

Right now, you're correct that there's no built-in way to automatically treat each *.example.com subdomain as a separate Matomo site with its own Site ID using just a single wildcard DomainConfig.

That said, I'd like to get a better sense of how you imagine this working:
How would you expect the system to determine and assign individual Site IDs for each subdomain, given there's only one DomainConfig defined for the wildcard? For example, how would you want to tell the system that it should use Site ID 2 for cloud.example.com, Site ID 3 for files.example.com, and so on?

[zmweske]

For example, with this plugin for Umami, you can set it up to automatically create new tracked sites (for each subdomain) as it sees them. This utilizes a similar server-side tracking to what your plugin seems to use.

Here's a snippet from the configuration documentation table.

key	default	type	description
createNewWebsites	false	bool	If set to true, will try to create a new website on Umami, if domain not found there

In total, my traefik yaml config for the plugin is extremely short and allows me to track everything that goes through traefik:

    umami-feeder:
      plugin:
        astappiev-umami-feeder:
          umamiHost: "http://umami:3000"
          umamiUsername: admin
          umamiPassword: example
          createNewWebsites: true
          trackErrors: true

With regards to the site-id mapping, I don't know the best way to compute that or store it within the plugin, but there may be a way to do so through API calls to the matomo instance itself. I am not well enough versed in matomo working to know about anything along these lines, however.

[Rau-N]

Thanks for sharing the example with the Umami plugin — that definitely gives me a better idea of how dynamic subdomain tracking could work without explicitly defining each one as an individual DomainConfig.

To implement something similar, it would require the Matomo API to support specific endpoints for creating new sites and fetching site information like the Site ID. I'm not currently sure if the Matomo API offers that functionality, so I’d need to look into it further.