Add the step to a workflow

Send conversion is the step Ledion adds to HubSpot workflows. When a record reaches it, Ledion sends that record as a conversion to every network the conversion goes to, with its real value, and hands the workflow a result for each network.

Before you start

• Ledion installed in HubSpot (Install Ledion), with at least one network connected.
• A conversion created in Ledion (Create a conversion).
• A contact or deal workflow. The step works in both. Other workflow types (companies, tickets, custom objects) don’t offer it.

1. Add the step

1. In HubSpot, open the contact or deal workflow that should send the conversion, or create one. Its trigger is the moment you want to count: a contact becoming an SQL, a deal reaching Closed won, a custom event.
2. Add an action and choose Send conversion. The app is Ledion.
3. Fill in the fields below and save the workflow.

Screenshot to come: HubSpot workflow editor, deal workflow: the Send conversion step (Ledion) open, with Conversion set to Closed won, Value mapped to the deal's Amount and Currency mapped to the deal's Currency

2. Fill in the fields

Each field starts with its help text in HubSpot, in quotes.

Conversion

“Pick a conversion you created in Ledion. It decides which networks receive this event.”

Required. The list shows your conversions that are turned on, each with the networks it goes to. With none yet, it shows “No conversions yet: create one in Ledion”.

Value

“Usually the deal’s Amount. Leave empty to use the conversion’s default value.”

Map a number property, like the deal’s Amount. It has to be 0 or more. For the same value every time, leave it empty and set the conversion’s default value in Ledion.

Currency (ISO code, e.g. USD)

“Usually the deal’s Currency. Leave empty to use the conversion’s default, then your account currency.”

A 3-letter ISO 4217 code. When this field is empty, Ledion takes the conversion’s default currency, then the default currency in Ledion’s Settings, then your HubSpot account currency. So if all your deals use one currency, leave it empty.

Occurred at (optional)

“Leave empty to use the time this step runs.”

Map a date property only if the step runs well after the event. The time can’t be earlier than the ad click, and Meta and Reddit take events up to 7 days old (windows).

Dedupe key (advanced)

“Only for repeat events. Ledion sends once per record and conversion unless this changes.”

Most workflows leave it empty. Map a property that’s different for each event you want counted, like a contract ID: Ledion then sends once per record, conversion and key. It overrides the conversion’s repeat policy. Ledion keeps only a hash of the key, never the value.

3. What happens when it runs

• Ledion answers HubSpot at once and holds the record at this step until every network has answered, usually within 2 minutes. Then the workflow moves on.
• Ledion holds a record for 24 hours at most. After that, it completes the step with the results it has and marks the rest failed.
• The step never stops the workflow, even when a network fails. Its outputs say what happened.
• If HubSpot retries the step, Ledion still sends once.
• Each run shows up on Ledion’s Activity page within seconds, with a result per network.
• A run where at least one network takes the conversion counts as one send toward your plan.

4. Use the results

The outputs

Later steps in the workflow can use these.

Output	Values
Ledion status (status)	sent, partial, failed, skipped
Google Ads result (google)	sent, failed, skipped, expired, no_match, not_configured
Meta result (meta)	The same as Google Ads result
Microsoft Ads result (microsoft)	The same as Google Ads result
Reddit result (reddit)	The same as Google Ads result
LinkedIn result (linkedin)	not_configured until LinkedIn ships
Ledion send ID (send_id)	The send’s ID, as Activity shows it
Ledion message (message)	Up to 250 characters, one part per network, like “Google Ads sent · Meta sent · Reddit: no click ID, email or phone on the contact.”

Ledion status

• sent: every network the conversion goes to has it. A network that already had it for this record counts.
• partial: at least one network got it and at least one didn’t.
• failed: no network got it, and at least one failed.
• skipped: nothing was sent and nothing failed. Either no network could take it (no match keys, too old, not in your plan), or the whole run was skipped: plan limit reached, conversion turned off, no connected network.

Each network’s result

• sent: the network accepted it. Google Ads accepts first and judges later: Activity shows Google’s final verdict.
• failed: the network refused it, or stayed unreachable through Ledion’s retries. The message says why (Troubleshooting). After you fix a broken connection, Retry failed sends resends these, but the workflow keeps the result it already got.
• skipped: not sent again, because the network already has this conversion for this record.
• expired: older than the network accepts, so Ledion didn’t send it.
• no_match: the record had none of the details that network matches on, so Ledion didn’t send it.
• not_configured: the conversion doesn’t go to that network, or your plan doesn’t include it.

When a conversion goes to two accounts of one network, that network’s result is the worse of the two, in this order: failed, expired, no_match, not_configured, skipped, sent.

Branch on a result

1. After the Send conversion step, add a branch of the type “One property or action output (value equals)”.
2. Choose the step’s output, like Google Ads result, and the value to catch, like failed.
3. Put the follow-up in that branch. For example: if Google Ads result is failed, create a task for your ops owner.
4. Leave everything else to the None met branch, including runs without a result.

To use an output in a later action instead, pick it from HubSpot’s data panel, under Action outputs.