No account-level analysis: engineering solution

Instrument the approved group type and a stable group value after your organization enables the Accounts add-on. Data Assistant can't add group context to events, and group changes affect new data rather than historical events. Start from the group definition in the decision guide, and confirm your organization enabled the Accounts add-on before you begin.

Create the group schema

1. In Amplitude Data, go to Data > Groups and select Create group.
2. Name the group type for the business object, such as account or workspace, rather than a specific account value.
3. Add a description, owner, source, and planned group properties.
4. Use a stable internal identifier as the group value. Send a separate human-readable group property, such as account name, for display and segmentation.

Choose the membership model

• Use an event-level group when membership applies only to specific events, or can change between events. Include the groups field on every relevant event through an SDK, the HTTP V2 API, or your customer data platform.
• Use a user-level group when all future events from a person should belong to the group. Assign it through an SDK Identify call or the Identify API. Amplitude doesn't let you remove a user-level group association. You can only overwrite it.
• Use the Group Identify API to set and update group properties. Group-property updates don't apply retroactively.

Validate the group

1. Send test activity for two people in the same group.
2. Open Users > Group Profiles and find the group.
3. Confirm the profile holds both people's relevant events and the expected group properties.
4. Build an Event Segmentation or Funnel Analysis chart and change the counting unit from users to the new group type.

Refer to Plan your Accounts instrumentation for the full event-level and user-level design guidance.