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
Customer.io stores rich customer attributes — plan type, industry, usage frequency, signup source, feature flags. These attributes define natural audience clusters, but they live as flat key-value pairs with no synthesis. This job pulls customer attributes via the App API, clusters them by plan tier and industry, then creates Mavera Custom Personas for each segment. Every focus group and content generation can now target the exact mix of attributes that defines each customer type. Flow: Customer.io App API → Customer attributes → Cluster by plan/industry/usage → MaveraPOST /api/v1/personas → Attribute-driven persona library
Architecture
Code
Example Output
Error Handling
App API 10 req/sec limit
App API 10 req/sec limit
Individual customer attribute lookups burn rate fast. The code throttles to 120ms between requests. For 1,000+ customers, use Customer.io’s data export or segment-based approaches instead of per-customer calls.
Missing attributes
Missing attributes
Not all customers have
plan_type, industry, or usage_tier. Defaults to free/unknown/low. Ensure these attributes are set via Track API identify calls before running this job.Segment membership pagination
Segment membership pagination
The
/segments/{id}/membership endpoint returns up to 200 IDs per page. For larger segments, paginate with the next cursor.Persona duplication
Persona duplication
Re-running creates duplicates. Check with
GET /api/v1/personas?search=CIO: before creating, or DELETE old versions first.What’s Next
Customer.io Integration
Back to Customer.io integration overview
Campaign Messaging Strategy
Analyze campaign metrics for winning patterns
Webhook → Mave Trigger
Automated retention research on churn signals
Personas API
Full reference for POST /api/v1/personas