Group-Level Unification (GLU) is available across segmentation, personalization, dynamic content, exit criteria, and action elements. This article covers how each feature area works with GLU enabled.
GLU is available across Email, Web Push, SMS, WhatsApp, and App Push products.
Architect
GLU is supported in the following Architect starters: On Past Behavior, On Dynamic Date, On Event, and On Attribute Change. These starters allow you to filter events and target users across multiple brand accounts within the same group.
Select group accounts
Select the customer accounts you want to include. This defines which brand panels contribute users and event data to the segment.
Select events
After selecting your accounts, choose the events to filter on. Event filtering uses AND logic, meaning the selected events must be present across all selected accounts for a user to qualify.
Segmentation
You can add a Group Level condition to any additional segmentation section.
After selecting the accounts, define your conditions to build the segment.
Segmentation uses AND logic by default.
Example: A segment targeting users whose birthday falls between 1 June 2025 and 31 July 2025 across two selected accounts uses AND logic. Both accounts must have the birthday attribute within the defined range for the user to qualify.
To build segments with OR logic, click Add Segment Group. This creates multiple segment groups, each of which can qualify the user. Both AND and OR logic are supported within the same segmentation setup.
How GLU resolves attribute values across accounts
When the same attribute exists on multiple brand panels, GLU evaluates the most recent value across all selected accounts.
Example:
A commerce group uses last_visited_category_name on two panels:
gluautomation1 sets last_visited_category_name = Home on 10 April
gluautomation2 sets last_visited_category_name = Mobile Phone on 14 April
A group-level Email campaign is built with the following condition:
Attribute: last_visited_category_name
Equals: Mobile Phone
Among the users of gluautomation1 and gluautomation2
The user qualifies because gluautomation2 holds the most recent value. If the campaign also personalizes content using last_visited_category_name, the email is built around Mobile Phone.
GLU always evaluates the most recently updated attribute value across all selected accounts. The account that set the value most recently takes precedence.
Dynamic content
GLU allows you to pull dynamic content from any connected account into your campaign communications. Personalization can reference attributes, events, and catalog data from a brand panel other than the one running the campaign.
To add group-level dynamic content:
Select the customer account for which you want to use dynamic content.
Choose the dynamic content type. Available types include default attributes, custom attributes, events, and product catalog attributes, all sourced from the selected account.
The selected content populates in your message from the chosen account.
Example: If you select gluautomation2 as the source account, all dynamic content in the message is populated from that account's data, regardless of which panel is sending the campaign.
