Use Amplitude Custom Events Correctly
Use a custom event to group interchangeable existing events for analysis, not to infer an ordered journey. Confirm plan and role availability before building a shared definition around it.
Before you start: Custom events are available on Plus, Growth and Enterprise plans. Admins, managers and members can create them. Validate the raw events and list downstream charts before changing an established definition.
Worked example: A content product may count document published or report shared as a meaningful output. Do not include editor opened if that action does not represent a completed output.
Step-by-step guide
Define the grouped outcome
Write why either source event should count. If both are required in sequence, use a funnel instead of a reusable OR grouping.
Inspect source events
Validate their triggers and necessary properties. A shared label should not conceal incompatible success definitions.
Create the custom grouping
In Amplitude Data, choose Events in the left navigation and click Create Custom Event. Select the source events in the modal and add any event-specific filters. Use this OR grouping only when either qualifying event represents the intended outcome.
Test example users
Select the saved event from the chart event picker’s Custom category. Compare known journeys with its source events and filters; a person with neither qualifying outcome should remain excluded.
Review property consistency
Only depend on fields that are meaningfully available on the underlying events. Document differences before building breakdowns.
Manage changes carefully
Record consumers before renaming or editing the custom event. Validate affected charts after a change and preserve the previous definition for interpretation.
Common mistakes
OR treated as AND
A custom grouping is not proof that every action occurred.
Properties assumed universal
A field may exist on one source event only.
Rename without consumers
Dependent charts can require updates. Check them explicitly.
Tips
Keep the grouping rationale next to its name.
Test an excluded example as well as a match.
Use a funnel for ordered completion.
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.