Skip to main content

Scenario

Segment’s identity graph merges user identities across sources — the same person visiting your website, using your mobile app, and opening your emails appears as one unified profile. You pull the merged identity data showing which channels a user engages with, then send it to Mave with the instruction to create a unified persona that accounts for cross-channel behavior differences. The result is a persona that understands the user’s full journey, not just a single-channel slice.

Architecture

Code

Example Output

Error Handling

The identity resolution features (external_ids, merged profiles) require Segment Engage. On Connections-only plans, profiles exist per-source without cross-source merging.
Common external_id types include user_id, email, ios_id, android_id, anonymous_id, and ga_client_id. The code counts ID types to estimate cross-channel coverage — more ID types = more channels connected.
The example uses traits like web_sessions_30d and mobile_sessions_30d. These must be set up as computed traits in Segment Engage. If they don’t exist, compute from raw events using the Events API or set up custom computed traits.

What’s Next

Segment Integration

Back to Segment integration overview

Real-Time Persona Triggers

Auto-trigger research from live events

Mave Agent

Full reference for POST /api/v1/mave/chat

All Integrations

50+ API integrations with full code