If we do double-tagging (eg a Piwik Site with both www and subdomain, and 2 each for the separate sites), that means we have to pay each event twice, right? There is no such thing as a “secondary server call” like in Adobe Analytics (GA4 has sth similar).
We don’t have “secondary server calls”. Each call is counted towards the plan limit.
What about setting it up by using one property together with cross-domain tracking? For that use case, you could set up an additional custom dimension to distinguish both domains via segmentation. This could be also done based on the event_url dimension.
That’s unfortunate. The other approach you mentioned would be also my fallback option, but it is not really a good one.
Client users have to learn to use a segment every time they want to see “only data from e.g. subdomain.site.com”
Right now, some external partners have access to only the www data. It would not be possible to handle that. These partners would have to get special Data Studio reports which increases the workload.
Thanks that would be great. Be sure to check out how Adobe Analytics is doing “Virtual Report Suites”, I think this approach is really the best solution for such use cases. Underneath it is actually all one Report Suite (=one Piwik “Site”), but people can select “Virtual Report Suites” with (invisible) Segments pre-applied. You can also give users only access to such Virtual Report Suites. There is even more functionality here, but just having these basic things mentioned would go a long way already.
Thank you for this feedback, it helps a lot. Yes, we were thinking about similar solution, covering both applying the filter as well as managing permissions to those views.
Yes, we were thinking about similar solution, covering both applying the filter as well as managing permissions to those views.