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
Wistia’s engagement heatmap shows per-second viewer retention for every video — the exact moments where viewers rewatch, skip, or drop off. This job pulls the engagement data for a video, identifies the sharpest drop-off points, then sends the timestamp and context to Mave with the question: “Viewers drop off at 0:45. Research best practices. Suggest specific edits.” The result is a creative revision plan grounded in actual viewer behavior — not gut instinct — with research-backed recommendations for each drop-off moment.Architecture
Code
Example Output
Error Handling
Engagement data format
Engagement data format
Wistia’s engagement data is an array of floats (0.0-1.0) representing the fraction of viewers still watching at each second. Some older videos may lack this granularity. If
engagement_data is empty, the video may not have enough plays to generate a heatmap (minimum ~5 plays).Hashed ID vs numeric ID
Hashed ID vs numeric ID
Wistia uses hashed IDs (alphanumeric strings like
abc123def4) in most API endpoints. Don’t confuse these with numeric media IDs. You can find the hashed ID in the video’s embed URL or via GET /v1/medias.json.Drop-off detection threshold
Drop-off detection threshold
The 10% threshold is configurable. For shorter videos (under 60s), tighten to 5% — a 10% drop in a short video is more significant. For long-form (10+ min), relax to 15% to avoid false positives from natural attention fluctuation.
What’s Next
Wistia Integration
Back to Wistia integration overview
Viewer-Level Persona Mapping
Map viewers to psychographic personas
CTA Performance × Focus Group
Optimize CTA placement and messaging
Mave Agent
Full reference for POST /api/v1/mave/chat