Check Activity and retry sends
Ledion’s Activity page lists every send, newest first. A send is one run of the Send conversion step for one record, or one Send test. It shows up within seconds of the step running, and Ledion keeps it for 90 days.
Read the list
Each row has the Time, the Record (Contact or Deal, with its ID: click it to open the record in HubSpot), the Conversion, the Value, a tag per network and the Message. Send test runs carry a Test tag.
Each network’s tag reads “[Network]: [status]”. The statuses are the step’s outputs in plain words:
| Activity says | Step output | What it means |
|---|---|---|
| Sending | (not final yet) | Ledion is sending it now |
| Retrying | (not final yet) | The network was busy or down. Ledion tries again later (how Ledion retries) |
| Sent | sent |
The network took it |
| Failed | failed |
The network refused it, or stayed unreachable through every retry |
| Skipped | skipped |
Not sent again: the network already has this conversion for this record |
| Too old | expired |
Older than the network accepts, so Ledion didn’t send it |
| No match | no_match |
The record had nothing that network matches on |
| Not set up | not_configured |
The conversion doesn’t go there, or your plan doesn’t include that network |
A send that reached no network at all (the conversion is turned off, the plan limit, no connected network) shows one tag for the whole send, with the reason in the Message. The Troubleshooting page has every message.
Screenshot to come: Ledion, Activity: the list with its filters, one send Failed for Google Ads and one with Reddit: No match
Filter
- Status: All statuses, Sent, Partly sent, Failed, Skipped or In progress.
- Network: one of your networks, including ones you removed.
- Conversion: one of your conversions.
- From and To: days in your HubSpot account’s time zone. Both days count.
The list shows the newest sends first. Load more adds older ones. When nothing matches, click Clear filters.
Open one send
Click a send’s time. The send’s page shows its time, record, conversion, value, status and message, then one panel per network:
- the network’s status and the number of Attempts;
- the Error code and Error, when it didn’t go through (look them up in Troubleshooting);
- the Request ID the network gave back, for when you ask its support about a conversion;
- the Network verdict, for Google Ads (below);
- the Match keys: which details the record had for that network, like Email ✓ or Microsoft click ID (msclkid) ✗. Ledion records only whether each was there, never the value.
Google’s later verdict
Google accepts an upload first and judges it later, sometimes hours later. Ledion checks back 30 minutes after the upload, then about once an hour, for up to 24 hours, and shows what Google said as the Network verdict:
| Network verdict | What it means |
|---|---|
| Processing | Google hasn’t judged it yet |
| Confirmed | Google processed it |
| Duplicate | Google already had this event, so it counts once |
| Retrying | Google asked for it again later, usually because the click is too recent. Ledion sends it once more, 1 to 12 hours later, and checks again |
| Rejected | Google refused it after accepting it |
| Unknown | No verdict within 24 hours, or Ledion couldn’t ask |
The send’s status stays Sent either way: Google took the upload. Activity doesn’t show why Google rejected one. When Google rejects more than 20% of a conversion action’s checked events in a day (at least 5), Ledion emails your alert recipients with the main reason (Alert emails). The usual causes are a click ID from another Google Ads account and missing consent (Troubleshooting).
Retry failed sends
Fixed a connection that needed reconnecting, or gave Ledion its access back? Then resend what failed in the meantime. On the Activity page, click Retry failed sends. The button shows while at least one connection is Active.
Ledion resends a network’s result when all of these hold:
- it failed because the connection needed reconnecting or lost access (“[Network] connection needs reconnecting.” or “Ledion can’t access [account] in [Network]…”);
- the send is from the last 7 days, and isn’t a Send test;
- the connection is Active again, the conversion is still on, and it still sends to that account;
- the conversion is still inside the network’s window: 7 days for Meta and Reddit, 90 days from the click for Google Ads and Microsoft Ads.
The page says “Retrying [count] failed sends. Their status updates here.” Each one shows as Retrying, then Sent or Failed. If nothing qualifies, it says “Nothing to retry.” A retry doesn’t count as another send on your plan, and it doesn’t change what the workflow already got from the step.
Other failures aren’t retried this way. Fix the cause, and the next time the step runs for that record, it sends.
Something missing or wrong? Email santi@ledion.io.