Use PostHog Actions for Shared Metrics
Create an action when several existing events represent the same analytical concept. Keep the raw events distinct and make the action’s matching rules explicit so a convenient label does not hide incompatible behavior.
Before you start: Have representative events and permission to manage actions. List reports that will consume the action and agree the user outcome it represents.
Worked example: A meaningful report interaction could include report_saved and report_shared. Keep opening a help tooltip outside that action if it does not indicate the same product engagement.
Step-by-step guide
Define the shared concept
Write one sentence explaining what the action counts. List included and excluded events before configuring the rule.
Choose the source events
In Data Management, open Actions and click New action. Choose the captured events or autocapture matches for the shared concept. Prefer semantic events where a changing selector would make the definition fragile.
Add specific conditions
Narrow each match with the relevant properties. For an autocapture match, selected fields such as text, URL and selector must all match. Distinguish these conditions from alternative source events; use a funnel when actions must happen in sequence.
Check matching examples
Inspect known included and excluded journeys. Confirm that a broad condition does not count unrelated interactions or double-represent the intended outcome.
Review historical impact
Actions can apply to past events, so inspect prior periods as well as recent data. Explain any change in reported history to consumers.
Publish with ownership
Save a clear name and definition, then update one report first. Record an owner and the downstream insights affected before expanding use.
Common mistakes
Action used as sequence
A grouping does not prove ordered completion. Use a funnel for sequential behavior.
Fragile selector
A presentation change can break autocapture matching. Prefer stable events where feasible.
History changes unexplained
A changed action can alter old analytical results. Record the definition change.
Tips
Keep one excluded example beside the action definition.
Check an older period before adopting the metric broadly.
Avoid combining events merely because their names look similar.
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.