Group Properties Overview
Send account-level attributes to Appcues so you can target experiences by customer account, not just individual users.
Table of Contents
Group properties are attributes that describe your customer accounts rather than individual users. If every user within a customer account shares the same value for a property — like company name, industry, or employee count — that property belongs at the group level.
Also known as: account properties, account-level data.
When to use group properties
Use group properties to target experiences based on account characteristics instead of individual user traits. For example, you can show an experience only to companies with more than 50 employees, or to accounts with a renewal date in the next 30 days.
You can include account-level data directly in user profiles, but group properties are a better fit when:
- Group and user data live in separate systems and combining them before sending to Appcues isn't practical.
- You use Segment (or a similar tool) that already sends group and user data separately, and reworking the integration for Appcues isn't feasible.
- Your CRM treats account-level data on individual contact records as messy or redundant.
Appcues handles the connection — it associates each user with their group and checks group properties when evaluating targeting rules.
For more on targeting, see Targeting Flows.
Send group properties
Send group properties using Appcues.group() (or the equivalent group() call in your integration). Call identify() first so Appcues can associate the user with the correct group.
Web installation
If installed via Freshpaint, Rudderstack, or Segment, Appcues automatically receives data from your existing group() calls as long as the source is connected to the Appcues destination.
Mobile installation
Appcues.group() follows the same format as Appcues.identify(). Pass the group ID first, then any custom group properties. identify() must be called before group() for proper user-to-group association.
Framework-specific guides:
Using the Segment-Appcues plugin? Appcues receives data from your existing group() calls automatically.
View your group properties
All group properties appear on the Properties page in Settings > Data > Properties > Account. Properties only show up after at least one user with that property has been identified.
You can also inspect properties on any page of your app by opening the Appcues Debugger.
Which group properties to send
Start with these and add more as needed.
Required
| Property | Why |
|---|---|
| Group ID | The only required property. |
Recommended
| Property | Why |
|---|---|
| Account Manager / Success Manager | Know which team member manages an account. |
| Plan Type | Lifecycle targeting (e.g., trial vs. paid). |
| Plan Tier | Tier-based targeting (e.g., standard vs. enterprise). |
| Beta User / Feature Flags | Communicate with accounts that have access to specific features. |
| MRR | Gate in-product messages to certain revenue tiers. |
| Address Info | Target by city, state, or country at the account level. |
Use the installation plan template to map out group properties, user properties, and events before your developers start the installation.
Groups and the Public API
The Appcues Public API supports group calls for retrieving group profiles, updating group profiles, and associating users with a group. You'll need the account_id and group_id parameters. See the Public API documentation for setup instructions and example calls.
Groups and Zapier
The Zapier integration supports the Update Group Profile in Appcues action. Supply the Group ID and the group properties you want to update. For use-case ideas, visit the Appcues Integration Hub for Zapier.
Remove group properties
Contact support@appcues.com with a list of group properties to remove from your Appcues Studio interface.