Conversion Goals
Track business outcomes tied to your flows with conversion goals.
Conversion Goals
Conversion goals let you measure whether your flows drive real business outcomes. Instead of only tracking views and completions, you can define specific events that represent success -- like a user activating a feature, completing a purchase, or upgrading their plan -- and see how often those events occur after a flow is shown.
How conversion goals work
A conversion goal connects a flow to a target event. When a user sees the flow and later triggers that event within a defined time window, Setgreet records it as a conversion.
The conversion tracking pipeline works as follows:
- A user is shown a flow (a flow display event is recorded).
- The user later triggers an event in your app that you have configured as a conversion goal.
- Setgreet checks whether the user saw the associated flow within the conversion window.
- If they did, a conversion is recorded and linked to that flow display.
Each user is counted only once per flow display -- if the same user triggers the goal event multiple times after viewing a flow, only the first conversion is recorded.
Setting up a conversion goal
Conversion goals are managed inside the Path Analytics panel of a flow:
- Open the flow in the flow builder.
- Click the flow menu in the top bar and select Path Analytics.
- Find the Conversion Goals section and click Add Goal (or edit an existing one).
- Configure the goal:
- Name -- a descriptive label (for example, "Feature X Activated" or "Plan Upgraded"). Up to 200 characters.
- Event name -- must match the event name your app sends to the Setgreet SDK (for example,
feature_activatedorplan_upgraded). - Conversion window -- the number of hours after a flow view during which conversions are counted. The default is 24 hours, and the maximum is 168 hours (7 days).
- Property filter (optional) -- narrow conversions to events that match specific property values.
Property filters
Property filters let you target a subset of events. For example, if your purchase_completed event includes a plan property, you can filter conversions to only count events where plan equals "pro".
Each filter has three parts:
| Field | Description |
|---|---|
| Key | The event property name (e.g., plan, amount, category). |
| Operator | How to compare: equals, contains, or greaterThan. |
| Value | The value to match against. |
You can add one property filter per goal.
Viewing conversion data
Once a goal is set up, the Path Analytics panel shows conversion metrics alongside the standard flow analytics:
| Metric | Description |
|---|---|
| Total Conversions | Number of conversion events recorded within the window. |
| Unique Users Converted | Number of distinct users who converted. |
| Conversion Rate | Percentage of unique flow viewers who converted. |
| Average Time to Conversion | Mean time between the flow display and the conversion event. |
These metrics are scoped to the date range selected in the panel.
Conversion funnel
The conversion funnel view shows the path from flow impression to goal completion:
- Flow views -- total unique users who saw the flow.
- Flow completions -- users who finished the flow.
- Goal conversions -- users who triggered the goal event within the conversion window.
This three-step funnel helps you identify where to optimize. If completions are high but conversions are low, the flow content may not be compelling enough to drive action. If views are high but completions are low, users may be dropping off before seeing the key message.
Measuring flow effectiveness
Conversion goals are the most direct way to answer the question: "Is this flow actually working?"
Use them to:
- Compare flow variants -- if you are running experiments, conversion goals let you measure which variant drives better outcomes.
- Justify flow investment -- show stakeholders that an onboarding flow increased feature adoption by a measurable percentage.
- Identify underperforming flows -- flows with high views but low conversion rates are candidates for redesign.
- Track time-sensitive campaigns -- set shorter conversion windows for urgent prompts (e.g., a flash sale announcement) and longer windows for educational flows.
Conversion goals require your app to send tracking events via the Setgreet SDK. Make sure the event names in your goal configuration match the event names your app sends exactly.
Managing goals
You can create, update, and deactivate conversion goals from the Path Analytics panel:
- Activate / Deactivate -- toggle a goal on or off without deleting it. Deactivated goals stop recording new conversions but retain historical data.
- Edit -- update the goal name, event name, property filter, or conversion window at any time. Changes apply to future conversions only.
- Delete -- permanently remove a goal and its conversion data.
Next steps
- Flow Analytics -- review overall flow performance alongside conversion data.
- Experiments -- A/B test flow variants and measure conversions per variant.