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
Your Mailchimp audience has segments — VIP customers, newsletter-only subscribers, recent signups, inactive members. Each segment represents a real behavioral group. You pull segment definitions and member data, aggregate demographics and engagement patterns per segment, and create a Mavera Custom Persona for each. The result is a persona library built from your actual email audience, not hypothetical demographics.Architecture
Code
Example Output
Error Handling
10 simultaneous connection limit
10 simultaneous connection limit
Mailchimp enforces 10 concurrent connections per API key. The code uses sequential requests with 500ms delays. For parallel processing, use a connection pool limited to 8.
Segment member pagination
Segment member pagination
The
/segments/{id}/members endpoint returns max 1,000 members per request. Use offset for pagination. Each page counts as one connection.Merge fields vary by audience
Merge fields vary by audience
Member
merge_fields (FNAME, LNAME, etc.) depend on your audience configuration. The code uses stats which are always available regardless of merge field setup.What’s Next
Mailchimp Integration
Back to Mailchimp integration overview
Campaign Content Optimization
Train brand voice from winning campaigns
Personas API
Full reference for POST /api/v1/personas
All Integrations
50+ API integrations with full code