Key Actions

A Key Action is a first class named event Appcues fires whenever a key lifecycle moment, defined by you, happens for one of your users — a purchase, a feature adopted, a plan upgraded, a milestone reached. Once defined, Key Actions can be used across Appcues: as campaign objectives, in targeting, and in analytics.

How is this different from just using an event directly? A Key Action isn't a replacement for your events — it's built on top of them. It's the curated, named layer you use to tell Appcues "this specific moment matters," which is what makes it usable as a campaign objective (rather than asking you to pick from your entire raw event list) and lets you add extra context — like distinguishing a customer's first order from a later upsell using the same underlying event.

Why use a Key Action?

Use a Key Action any time you want to promote a real-time event — or a set of conditions — into a meaningful, reusable moment in your users' lifecycle, especially moments that can happen more than once, like:

• A purchase or renewal
• A feature being adopted
• A support ticket being resolved
• A milestone being re-achieved
• A user state change

Two ways to build a Key Action

1. From conditions on the user

Define a set of conditions on your users — for example, "user has sent more than 10 messages." All conditions are treated equally, with no particular moment singled out as "the" event. Once every condition is true, the Key Action fires — once, ever — at the exact moment that state is first reached. This is the right choice for a genuine one-time milestone.

2. Anchored to a triggering event

Anchor your Key Action to something that actually happens in your product — an event — and optionally refine it with:

• An event attribute (e.g., order_processed where amount > 0)
• A user property (e.g., only for users on the Enterprise plan)
• A history requirement (e.g., only after signup_completed has already happened)

This unlocks two things a conditions-only Key Action can't do:

• It fires every time the event and conditions match — not just once — so you get a real, countable, trendable metric.
• It checks that your other conditions were true at the moment the event happened, not just at some point before or after. If the order in which things happen matters to what you're measuring, this gives you real confidence you're capturing the moment you actually mean.

Example: suppose you consider it a meaningful moment when a user publishes content for the first time, after already completing their profile and sending events. Built from conditions alone, a user who published content before finishing their profile would still count once all three things eventually became true — order doesn't matter. Anchored to the publish event instead, it only counts if the profile was already complete and events were already flowing at that exact moment — so it correctly excludes the user who did things out of order.

When to use which: if what you're tracking is a true one-time milestone and the order things happened in doesn't matter, conditions alone are simpler and sufficient. If the moment can happen more than once, or the sequence of events matters to what you're really trying to capture, anchor it to a triggering event.

Using Key Actions

Once created, a Key Action can be used to:

• Set the objective a Campaign is held accountable to
• Target content to users the moment they achieve it
• Report on volume and rate over time, broken down by segment or other dimensions
• Build funnels using Key Actions as steps
• Feed outcome reporting (Acquisition, Activation, Retention, Engagement, Feature Adoption)

A note on naming

Give your Key Action both a clear display name and a short identifier (slug) when you create it. The identifier is permanent — renaming the display name later won't change the underlying identifier other systems (like webhooks) reference.