Skip to main content

Scenario

Amplitude tracks revenue events with properties like plan type, ARPU, and segment. You pull revenue metrics, compute ARPU by user segment, and run a Mavera Focus Group asking synthetic personas to rate willingness to pay at specific price points using Slider and NPS question types. The result is pricing validation grounded in real revenue data and tested against persona reactions.

Architecture

Code

Example Output

Error Handling

The /api/2/revenue/day endpoint only returns data if you track revenue events via amplitude.revenue() or the Revenue API. If you only track subscriptions externally, import revenue data via the HTTP API or use a CDP integration.
The sample ARPU values are hardcoded for demonstration. In production, calculate ARPU from the Revenue API response by dividing total revenue by paying user count per segment.
Mavera Focus Groups support free-text responses. To simulate Slider and NPS question types, phrase questions with explicit scales (1-10, 0-10) and ask personas to provide both a numeric rating and explanation. Parse numeric values from the response text.
Personas may anchor to the current price in their responses. For more accurate willingness-to-pay data, run separate Focus Groups with different proposed prices (Van Westendorp method: too cheap, cheap, expensive, too expensive).

What’s Next

Amplitude Integration

Back to Amplitude integration overview

Persona Calibration

Calibrate personas from Amplitude composition data

Focus Groups API

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

Personas API

Full reference for POST /api/v1/personas