Conversion
A conversion is the outcome a flow records: a sale, an appointment, a sign-up. It is counted in reports, its value is totalled, and it can start a rule.
Last updated: September 30, 2026
Loading…
A conversion is the outcome a flow records: a sale, an appointment, a sign-up. It is counted in reports, its value is totalled, and it can start a rule.
Last updated: September 30, 2026
A conversion is the point where a flow says "something happened here": the sale closed, the appointment was booked, the form was completed. Put a Conversion step in a flow and that moment is recorded against the contact; it is counted in reports, its value is totalled, and it can trigger a general rule.
💡 A conversion step sends the customer nothing and does not branch the flow. It has a single output and the flow carries on from there.
Seeing how many messages an automation sent is easy; the real question is how many of them worked. A conversion answers that. You decide where in a flow to place it, and everyone who reaches that point is counted.
Typical uses:
The step has three fields:
{{field.order_total}}. A value that cannot be read as a number counts as empty, and the conversion is recorded without an amount.Conversion recorded is one of the general-rule events. Type the conversion's name in the filter and the rule fires only for that conversion; leave it blank and it fires for every conversion.
A common arrangement: when the sale conversion is recorded, a rule closes the conversation, adds the customer tag and enrols the person in the "After delivery" sequence. That way you handle the outcome in one place instead of appending a long chain of actions to the end of the flow.
For the concept, see General rules.
Both say "something happened", but they do different jobs:
That is why the answer to "how many sales did we make" lives in conversions, not tags: counting tags tells you only who carries that tag right now, whereas counting conversions tells you every sale that happened over the period.
In practice the two work together: the conversion records the outcome and a rule bound to it updates the person's tags.
Place the conversion at the step where the outcome is actually confirmed. A common mistake is putting it right after the message that sends the quote; nothing has happened at that point and your report looks better than reality.
The right places are usually:
A single flow can hold several conversion steps; each is recorded under its own name and appears as its own row in reports.
⚠️ Note: if the same person enters the flow more than once, the conversion is recorded more than once. To count a person only once, narrow the automation's re-entry rule on the Settings tab (Only once or Once a day), or add a tag condition before the conversion.
An online course seller uses this flow:
paid_amount field.{{field.paid_amount}}, currency TRY.At the end of the month, reports show how many sales there were, the total value, and which automation produced them.
A conversion name is a column heading in your report, and consistency pays off. A few suggestions:
A conversion is the single number that measures whether an automation is working; placed in the right spot, your reports tell you the truth.
Was this article helpful?