Last updated: March 2026 Category: Flows
Overview
Goal nodes let you define what "success" looks like for a flow. When a user reaches a Goal node, that event is recorded as a conversion. BeyondCart then tracks conversion rates and attributes revenue to the flow, giving you clear data on which automations drive real business results.
Prerequisites
An active or draft flow with at least one action node
Familiarity with the flow editor (see Creating a Flow)
Step-by-Step Guide
Adding a Goal Node
Open your flow in the editor.
Click the "+" button below the node where you want to track conversions.
Select "Goal" from the node type menu.
The Goal node appears on the canvas.
[Screenshot: Goal node placed after a push notification action on the flow canvas]
Configuring the Goal
Click the Goal node to open its configuration panel:
Goal Name — A descriptive label such as "Purchase Completed" or "App Reopened." This name appears in your flow statistics.
Conversion Event — The event that counts as achieving the goal. Common options:
purchase — The user makes a purchase.
app_open — The user opens the app.
page_view — The user views a specific page.
add_to_cart — The user adds a product to their cart.
Custom event — Any tracked event relevant to your business.
Attribution Window — The time period after the user reaches the Goal node during which the conversion event is counted. Typical values: 24 hours, 3 days, 7 days.
[Screenshot: Goal configuration panel with name, conversion event, and attribution window fields]
Where to Place Goals
The position of a Goal node determines what you are measuring:
After a push notification — Measures whether the notification drove the desired action.
At the end of a multi-step sequence — Measures the effectiveness of the entire journey.
On a condition branch — Measures conversion for a specific segment of users (e.g., only VIP users).
You can place multiple Goal nodes in a single flow to track different conversion points.
How Revenue Attribution Works
When a user who is in the attribution window of a Goal node makes a purchase:
The purchase amount is recorded as revenue attributed to the flow.
This revenue appears in the flow's statistics on the flows list page and the flow detail stats.
If the user is in multiple flows with active goals, each flow receives its own attribution.
Revenue attribution helps you understand which flows directly contribute to your bottom line.
Viewing Conversion Data
Open the flow from the flows list.
Click the "Statistics" tab.
You will see:
Total conversions — The number of users who triggered the goal event within the attribution window.
Conversion rate — Conversions divided by the total number of users who reached the Goal node.
Attributed revenue — The total dollar amount from purchases attributed to this goal.
See Flow Statistics for a detailed breakdown of all available metrics.
Key Concepts
A Goal does not stop the flow. Users continue to the next node after the Goal. It is a tracking checkpoint, not an exit point.
Attribution windows are per-goal. Each Goal node has its own window, so you can set a 24-hour window for one goal and a 7-day window for another in the same flow.
Multiple goals per flow are supported. This lets you track micro-conversions (e.g., app_open) and macro-conversions (e.g., purchase) in the same journey.
Tips and Best Practices
Always add at least one Goal to every flow. Without goals, you cannot measure whether the flow is effective.
Choose attribution windows carefully. A 24-hour window is appropriate for time-sensitive flows like abandoned cart reminders. A 7-day window works better for welcome series or re-engagement campaigns.
Place goals strategically. If you want to know which specific action drives conversions, place the Goal immediately after that action — not at the very end of a long chain.
Compare goals across flows. Use the flows list page to compare conversion rates and revenue across all your flows to identify top performers.
FAQ
Q: Can I change the goal configuration after the flow is active? A: Yes. Changes apply to users who reach the Goal node after the update. Historical conversion data is not recalculated.
Q: Does the Goal node count conversions that happen before the user reaches it? A: No. The attribution window starts when the user arrives at the Goal node. Actions taken before that point are not counted.
Q: What if a user converts multiple times within the attribution window? A: Only the first conversion event within the window is counted toward the conversion metric. However, all revenue from purchases within the window is attributed.
Q: Can I use Exit nodes to end a flow early if a goal is reached? A: Yes. A common pattern is to place a Goal node followed by an Exit node. This way, once the user converts, they leave the flow and do not receive further messages.
Related Articles