Define Core Action Frequency in Amplitude
Measure how often eligible people complete a core value action, then interpret frequency in the context of their task. High volume can indicate useful work, automated behavior or repeated failure.
Before you start: Have a successful-action event and a realistic usage cadence. Separate people, accounts and total events before selecting the report.
Worked example: A reporting product may be useful when a team shares one weekly report. A person repeatedly retrying a failed export should not be considered the most engaged customer.
Step-by-step guide
Define the meaningful action
Choose confirmed value rather than a generic page visit. State whether repeated completion is beneficial.
Choose the unit
Decide whether frequency concerns an individual or account. A large team naturally generates more events than one person.
Set the cadence
Use an interval appropriate to the workflow. Document whether frequency means total completions or distinct active days.
Inspect distribution
Look beyond an overall average to occasional and heavy groups. Keep the original population and exclusions visible.
Check outliers
Review representative high-frequency journeys. Distinguish legitimate repeated work, automation and retries.
Connect to outcomes
Compare frequency with task success or return behavior without claiming causality. Choose a product question the pattern can actually inform.
Common mistakes
Average hides distribution
Heavy users can dominate.
Retries equal engagement
Check successful outcomes.
Daily expectation imposed
Match the natural task frequency.
Tips
Write the event and cadence in the metric name.
Inspect high-frequency outliers.
Keep total events separate from distinct active days.
Sources and verification
Based on product documentation checked on 2026-10-24. This is a documentation-based guide, not a hands-on benchmark. Features and availability can change.