# Account-level reporting in Amplitude Report on accounts, organizations, or other aggregated units instead of individual users. Source: https://amplitude.com/docs/analytics/account-level-reporting --- On this page - [Before you begin](#before-you-begin) - [How group-level reporting works](#how-group-level-reporting-works) - [Event-level vs user-level group definitions](#event-level-vs-user-level-group-definitions) - [Add groups to charts](#add-groups-to-charts) - [Groups in Experiment](#groups-in-experiment) - [Create group-level behavioral cohorts](#create-group-level-behavioral-cohorts) - [View and download groups with Microscope](#view-and-download-groups-with-microscope) - [Explore the behavior of a specific account](#explore-the-behavior-of-a-specific-account) - [Set properties at the group level](#set-properties-at-the-group-level) - [Dynamic group properties](#dynamic-group-properties) - [Create group properties using the Salesforce integration](#create-group-properties-using-the-salesforce-integration) # Account-level reporting in Amplitude In Amplitude, the default reporting level is the individual user. Charts and analyses rely on data from individual users. Sometimes, you need reports built around an aggregated unit of measurement, such as accounts, order IDs, or charts. The Amplitude Accounts add-on provides group-level analysis. A group is an object that a set of users might belong to, such as a company of customers, a team of users, or a playlist with listeners. Group-level analysis helps you understand how specific accounts interact with your product, instead of only viewing individual users in those companies. ## Before you begin - With the Accounts add-on, you can instrument up to five different group types per project. You can manage and remove groups using Amplitude Data. - Account-level properties have a limit of 1000 per project. - Changes to account groups and group properties apply to new data and don't affect historical data. - To [instrument account-level reporting in Amplitude, refer to the Help Center documentation](/docs/analytics/account-level-reporting-setup). ## How group-level reporting works After you [set up groups](/docs/analytics/account-level-reporting-setup), Amplitude includes them in a drop-down list in the [Segmentation Module](/docs/analytics/charts/build-charts-add-user-segments). From there, you can report at the group level instead of the individual user level. An analysis using group-level reporting counts distinct user property groups. Common use cases include: - Analyzing how many distinct accounts were active or sent a certain event (group by account ID) - Tracking how many charts users in your organization copy, save, and modify, then identifying which charts people use most often (group by chart ID) - Discovering how conversion rates change between different order types (group by order ID) - Using group-level reporting in funnel analyses: - such as determining how many accounts have converted from free trials to paid accounts (group by either account ID or project ID), or tracking how frequently users draft posts they don't publish in your social media platform (group by post ID) In a standard [funnel analysis](/docs/analytics/charts/funnel-analysis/funnel-analysis-build), the same person must complete all steps of the funnel to count as a conversion. With group-level reporting, different members of the group can complete different steps in the funnel, and Amplitude still interprets that as a conversion. Group-level reporting is useful for multi-sided marketplaces or B2B2C companies whose conversion processes involve multiple people. For example, a product for medical practices might include a conversion funnel with "send invoice" and "send payment" steps. An admin sends the invoice, while the patient sends the payment. In workflows like this, group-level reporting accurately measures total invoice conversion. ### Event-level vs user-level group definitions Amplitude supports event-level and user-level group definitions. - An **event-level** group is one that **only** includes specific events in the users' journey. Users aren't affected by the events, meaning future events triggered by the users **aren't** added to the group **unless** explicitly assigned. - By contrast, membership in a **user-level** group is **independent** of specific events. After the [Identify API](/docs/apis/analytics/identify) assigns users to the group, they remain in it for all future events. This is useful when you want to attribute all events a user triggers to a particular group. You can't un-set a user's group type. You can only overwrite it. ### Add groups to charts All chart and report types in Amplitude support [group-level reporting](#how-group-level-reporting-works), except the Personas and Compass reports. To use an instrumented group in your chart, select the group in the *Users* dropdown in the [Segmentation Module](/docs/analytics/charts/build-charts-add-user-segments). For example, to track the number of daily active organizations and group them by region, set up an [Event Segmentation](/docs/analytics/charts/event-segmentation/event-segmentation-build) chart like this: ### Groups in Experiment Beta This feature is in Beta. This feature may continue to evolve. This documentation may not yet reflect the latest updates. Groups in Experiment have two usages: 1. What property to randomize on 2. What unit to analyze on For example, as a B2B company, you may want to randomize and analyze by customer ID. If you analyze an onboarding funnel, you might not care whether one person completes step 1 and another person completes step 2, as long as both people belong to the same company. Refer to [how to evaluate groups and group properties](/docs/feature-experiment/data-model#users) for more details. Refer to [setting the bucketing unit](/docs/feature-experiment/overview) for configuration instructions. ### Create group-level behavioral cohorts To create a group-level [behavioral cohort](/docs/analytics/behavioral-cohorts), use the dropdown on the left to specify the group for the cohort. For example, you could create a behavioral cohort of companies that triggered the event `Create customized report`. Then, apply that cohort to a Retention Analysis chart to compare retention between companies that sent that event and companies that didn't. You can also import a cohort of groups from a file. The file must contain exactly one group name per line. ### View and download groups with Microscope You can also use [Microscope](/docs/analytics/microscope) with account-level reporting. Microscope is useful when you perform an account-level analysis and want to inspect a single data point or bucket. For example, imagine you have an instant messaging application and you want to increase new user invites. Create a funnel analysis with steps from `Activate Account` to `Invite New Contact`. Then use Microscope to view the groups in the last step's drop-off, or download the groups to understand why those groups drop off before inviting additional co-workers. You can also create a group-level cohort of those accounts, apply that cohort to other charts, or open [Investigate Conversion Drivers](/docs/analytics/charts/funnel-analysis/funnel-analysis-identify-conversion-drivers) for detailed analysis. ## Explore the behavior of a specific account Accounts let you inspect a single group's behavior, similar to the User Activity section. To access the Accounts tab: 1. Click *User > Group Profiles*. 2. Click any of the groups you have instrumented. 3. Optionally, search for a specific group or group property. Group property searches must follow the syntax of `name = value`. These searches cover only groups that have been active in the last six months. Amplitude searches across all historical values held by the property, not only the most recent group property value. Use quotes for multi-word strings. Avoid delimiters like commas or semicolons when possible. Spaces are optional. Clicking on an account takes you to that account’s page, where you can view the account’s properties and activities. Find the account’s most recent properties in the top panel. Set the account's properties with one of the following: - The [Group Identify API](/docs/apis/analytics/group-identify). - The [Salesforce integration](/docs/data/source-catalog/salesforce-group). - Event Segmentation to create dynamic properties. Use these properties to describe the account as a whole (for example, `30 day active users`, `account manager`, `plan type`, or `renewal date`). ## Set properties at the group level Group properties are account-level properties. These properties apply to all users who belong to that account. ### Dynamic group properties You can turn your KPIs into dynamically updating group properties. Add group properties such as “Last 7 Day Active Users” or “Monthly Active Users” to each account in your product. Admin-level users create dynamic group properties through an [Event Segmentation](/docs/analytics/charts/event-segmentation/event-segmentation-build) chart, with the following steps: 1. **Save a single time series Event Segmentation chart:** Save a user-level chart with a single time series metric that you want to track. Dynamic properties aren't supported on frequency and property distribution metrics, or on custom formulas. 2. **Determine time interval:** Set the time interval you would like to update the group property on. For example, a rolling window of "last 7 day active users" updates every day, while "weekly active users" updates after every calendar week. Dynamic properties aren't supported on static time ranges. 3. **Name group property:** Choose your group type and name for the group property. Editing the chart that creates the dynamic group property doesn't affect the property. ### Create group properties using the Salesforce integration To learn how to create **group properties** using Amplitude's Salesforce integration, refer to [Salesforce Group](/docs/data/source-catalog/salesforce-group) in Amplitude Sources. Was this helpful?