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
Klaviyo computes predictive analytics for each profile — predicted customer lifetime value (CLV), churn risk probability, expected next order date, and historic CLV. You pull profiles with these predictions, group them by CLV tier (high/medium/low), and create Mavera Custom Personas enriched with predictive data. The result is personas that know not just who your customers are, but what they’re worth and how likely they are to leave.Architecture
Code
Example Output
Error Handling
Predictive analytics availability
Predictive analytics availability
Predictive CLV and churn risk require Klaviyo Growth+ plan and sufficient data (500+ customers, 180+ days of orders). On lower plans,
predictive_analytics fields are empty. Fall back to historic_clv from order history.Revision header required
Revision header required
Every Klaviyo API request must include a
revision header. Without it, requests fail with 400. Use the latest stable revision from Klaviyo’s API changelog.Tiered rate limits
Tiered rate limits
Klaviyo’s rate limits vary: Profiles GET allows 10-75 req/sec depending on plan. On 429, read
Retry-After header. The burst limit (up to 350/sec) applies to Tracking/Events endpoints, not Profiles.What’s Next
Klaviyo Integration
Back to Klaviyo integration overview
Flow Content Refresh
Rewrite underperforming flow content
Personas API
Full reference for POST /api/v1/personas
Mave Agent
Full reference for POST /api/v1/mave/chat