Skip to main content

Scenario

You’ve identified two behavioral cohorts in Amplitude — users who onboarded within 24 hours versus those who took more than 7 days. These groups have radically different retention curves, but you don’t know why the experience differs. You map each cohort to Mavera personas and run a Focus Group exploring how fast-onboarders and slow-onboarders experience the product differently — what drives urgency, what causes delay, and what each group needs.

Architecture

Code

Example Output

Error Handling

You must supply user IDs for each cohort. Export these from Amplitude cohorts (Amplitude → Cohorts → Export CSV) or query via the Behavioral Cohorts API. The User Activity endpoint does not accept cohort IDs directly.
Each /api/2/useractivity call counts against the 360/hour limit. For 20 users per cohort (40 total), this uses 40 of your 360 hourly queries. Add 1-second delays between calls.
2 personas × 5 questions × 2 responses = 20 total responses. Allow 90–150s for completion. The loop provides ~150s.

What’s Next

Amplitude Integration

Back to Amplitude integration overview

Pricing Focus Group

Validate willingness-to-pay with revenue-driven personas

Focus Groups API

Full reference for POST /api/v1/focus-groups

Personas API

Full reference for POST /api/v1/personas