Skip to main content

Scenario

Wistia captures individual viewer data that most platforms aggregate away — email addresses, geographic location, percent of video watched, number of visits, and viewing history. This job pulls your visitor-level stats, clusters viewers by their behavior patterns (binge-watchers, skimmers, one-time visitors, repeat engagers), then maps each cluster to a Mavera persona with psychographic depth. The result is not just analytics segments but fully realized personas that explain why viewers behave the way they do — so you can tailor content and outreach to each group.

Architecture

Code

Example Output

Error Handling

Wistia’s email-level visitor tracking requires Turnstile (email gate) to be enabled on your videos. Without it, visitors are anonymous and identified only by visitor_key (a cookie-based ID).
The /v1/stats/visitors.json endpoint returns max 100 visitors per page. For accounts with 10,000+ visitors, pagination can take 100+ requests. Stay well within the 600 req/min limit by adding 200ms delays.
The events array within each visitor contains per-viewing data including percent_viewed, received_at, and media_id. For deeper analysis, join events by media_id to see which specific videos each cluster prefers.

What’s Next

Wistia Integration

Back to Wistia integration overview

Heatmap-Informed Creative Optimization

Diagnose drop-off points with specific edit recommendations

Personas API

Full reference for POST /api/v1/personas

Mave Agent

Full reference for POST /api/v1/mave/chat