Conversion events are the goals you care about — a purchase, a booked call, a sign-up. Create them under Settings → Automation → Conversion events with a name, a key (like purchase) and, optionally, a default value and currency.
Recording a conversion
- In a flow — add a Record a conversion step where the goal is reached.
- On a contact’s profile — Record a conversion, for a sale that happened in the DMs.
- Through the API — POST /api/v1/conversions from your store, booking tool or CRM.
Values and currencies
Values are whole numbers of the currency’s smallest unit — 1999 means $19.99. Leave the value out to use the event’s default. The value is saved with the conversion, so changing an event’s default later doesn’t rewrite past results. Totals are shown per currency and never added across currencies.
Which automation gets the credit
A conversion recorded by a flow step, or with an automation named in the API, is credited to that automation. Otherwise it goes to the last automation run or sequence that touched the contact in the 7 days before the conversion. One conversion has one owner, or none — it’s never split. This tells you what reached the person last, not proof of what made them buy.
Where you see them
Insights shows conversions by event, by automation and by sequence for the range you pick. In the Flow Builder, an automation’s Metrics shows its conversions too — keeping the ones recorded by its own steps apart from the ones credited to it afterwards, because only the first is a fact about the flow.
Archive an event you no longer use: it stops recording new conversions, and its history stays.
Didn’t answer your question?
A person reads every email. Tell us your workspace name and what you were trying to do.