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 Klaviyo flows (welcome series, abandoned cart, post-purchase) are underperforming — open rates dropped, click rates are flat, revenue per email is declining. You pull metric aggregates to identify which flows and specific messages are lagging, then use Mavera’s Generate to rewrite the underperformers with your brand voice. The result is refreshed flow content informed by actual performance data.Architecture
Code
Example Output
Error Handling
Metric aggregates API structure
Metric aggregates API structure
Klaviyo’s metric aggregates endpoint uses a JSON:API format with nested
data.attributes. The filter array uses Klaviyo’s filter syntax. Test queries in Klaviyo’s API playground first.Flow-level vs. message-level metrics
Flow-level vs. message-level metrics
The metric aggregates can be filtered by
flow_id (all messages in a flow) or by flow_message_id (specific message). For granular rewrites, query per message.Brand voice alignment
Brand voice alignment
For best results, create a Mavera Brand Voice from your top-performing Klaviyo campaigns before using Generate. This ensures rewrites match your established tone.
What’s Next
Klaviyo Integration
Back to Klaviyo integration overview
Predictive Persona Enrichment
CLV-tier personas with churn profiles
Segment Overlap Analysis
Simplified segmentation recommendations
Generate API
Full reference for POST /api/v1/generations