Multi tenant is a fancy way of saying one app serving many separate customers, each of whom should only ever see their own world. Analytics makes that harder than it sounds.
On a platform I worked on, each organization needed its own analytics, tied to its own tracking, not pooled into one big shared bucket. The challenge is wiring that up so the right measurement lands under the right tenant automatically, without a human choosing it each time and without one customer’s numbers leaking into another’s.
The key was to treat the tenant as data, not as a special case. The app looks up which organization it is serving, loads that organization’s own tracking configuration, and wires the analytics accordingly. Add a new customer and it just works, because nothing was hard coded to a single account.
That is the whole mindset with multi tenant work. Anytime you are tempted to hard code something that belongs to one customer, stop, and make it a value you look up instead. The version that treats every tenant the same is the version that scales without you babysitting it.