You’re not doing anything “wrong” in your implementation; the behavior you’re seeing comes from how Group Analytics works and how the prebuilt B2B Company reports are configured.
From the docs, there are a few key points:
1. Events must have the group key as an event property to count for groups
- “The group key(s) and their value should be present in every event you want associated with the group (much like the ID of a user).” [Tracking events]
- “Having the group key present as a user profile property does not automatically attribute the events by that user to the group.” [FAQ]
You’ve already done this (companies show up, activity feed has events), so attribution is working.
2. Users can belong to multiple groups → properties are lists
- For user profiles: "company_id": ["1", "2"] is the recommended shape. [Add group key to profile]
- For events: company_id can also be a list if an event belongs to multiple companies. [Tracking events]
Because of this, the correct operator in filters/breakdowns for group keys is typically “any in list”, not “distinct id is”.
3. B2B Company Analytics (Company Profiles, DAU, Power Users, etc.) are built on top of Group Analytics
- Company Analytics is “an advanced offering ‘within’ group analytics” and uses the designated B2B Company key. [B2B overview]
- You must designate the group key as the B2B Company Key in Project Settings. [Implementation setup]
The prebuilt cards on the Company Profile page are just saved Mixpanel reports. In your project, they appear to be using a filter like:
Company Id → Distinct Id is X
That assumes company_id is a scalar identifier, not a list. When you manually change it to:
Company Id → Any in list is X
the report works, which matches the docs’ guidance for multi-membership.
