Does the identifier field need to have the same name on every panel?
No. Field names can differ across panels. What matters is that the value represents the same user across all panels.
Can more than one common identifier be used?
No. Group-Level Unification (GLU) unifies users through a single identifier. Other identifiers continue to work within each panel ac but do not drive cross-panel matching.
What happens if a user exists on one panel but not another?
Nothing breaks. The user is treated as a regular single-panel user until the common identifier is populated on the second panel, at which point GLU recognizes them as the same user going forward.
Does GLU replace single-panel segmentation?
No. Single-panel segments continue to work as they do today. GLU adds the option to switch an audience to group level where appropriate.
Is GLU available on every channel?
GLU is available wherever the audience builder exposes the group-level selector. This currently includes Architect, Email, SMS, WhatsApp, Web Push, and App Push. Availability can vary by account and plan.
Will a user who opted out of one brand receive messages from another brand via GLU?
No. Consent remains panel-specific. A campaign is delivered only to users who have opted in, regardless of how they are unified across panels.
Does an attribute's value need to match on every selected account?
No. GLU resolves to the most recently updated value across the selected accounts, so the values don't need to be equal.
If I select two accounts on an event condition, is the count evaluated per account or combined?
Combined. GLU sums the event count across all selected accounts, for users common to those accounts, and evaluates your condition against that total.
Can I still filter using just one account's data inside a segment that also uses Group Level conditions?
Yes. Add a separate condition scoped to a single account and combine it with your other conditions using AND or OR.