Similar to Appcues.identify(), Appcues.group() is used to identify specific attributes, or properties, about your users. Feel free to check out this article for an introduction to group properties! 

Build Guide

Step 1: Send Group Properties using group()

While in most cases all user properties can be sent through identify(), there are other cases where using both identify() and group() is ideal:

• Individual properties and Group properties are stored or managed in different locations in your application, and it would be better to send those through the two methods rather than one large, combined identify()
• You are installed through a Customer Data Platform (Segment.io, Rudderstack, etc.) which requires an individual’s properties be identified separately to their group properties using an Analytics.group() call

An example of what this would look like:

Individual Properties vs Group Properties

Users in Appcues are identified by passing relevant properties through your installation to then use for meaningful content targeting and segmentation. These can be individual and group-level properties:
Examples of individual properties:

• Email
• User Created At
• Role

Examples of group properties:

• Company/Account Name
• Company/Account ID
• Account Status (trial, paid, etc.)
• Plan Type (free, enterprise, etc.)
• Account Created At

Step 2: Build Your Experience

For this example, a Slideout has been created to announce a new feature for employee management:

Step 3: Target using Group Properties

Group properties are nearly identical to User properties in how they can be used for targeting. The only difference? Selecting Group Properties rather than User Properties in the first dropdown! In the Audience settings within your Appcues experiences, or within a segment’s conditions, we can target any Group property information we have received.

Using the same employee management example, this announcement should only be shown to Admin users as they have access to use this new feature. Additionally, this new feature is designed more to manage many employees, so we’ll want to make sure we’re targeting it to users with enough employees:

Once configured, feel free to publish and test! Happy building!