Documentation Index
Fetch the complete documentation index at: https://docs.mavera.io/llms.txt
Use this file to discover all available pages before exploring further.
Scenario
Segment’s Profile API computes traits from raw events — lifetime value, purchase frequency, feature adoption score, engagement tier. These computed traits are richer than raw event properties because they aggregate behavior over time. You pull profile traits for a sample of users, identify trait clusters, and create Mavera Custom Personas enriched with CDP-computed behavioral data. This is the Advanced persona creation path — using real computed metrics instead of guesswork.Architecture
Code
Example Output
Error Handling
Profile API requires Engage
Profile API requires Engage
The Profiles API (
/spaces/{id}/collections/users/profiles) requires Segment Engage. On free plans, use the Tracking API to send events and create personas from event patterns instead.Computed traits vs. custom traits
Computed traits vs. custom traits
Computed traits (like LTV, purchase count) are defined in Segment Engage → Computed Traits. If they don’t exist, the profile traits will only include properties set via
identify() calls.Profile pagination
Profile pagination
The Profiles API returns up to 200 profiles per page. Use the
cursor parameter from the response for pagination. Each page counts as one API call.What’s Next
Segment Integration
Back to Segment integration overview
Audience Segments → Focus Groups
Map audiences to focus group research
Real-Time Persona Triggers
Auto-trigger research from live events
Personas API
Full reference for POST /api/v1/personas