LeadMove Docs
Buyers

Buyer health

What the healthy, degraded and paused badges mean, what trips them, and how to clear them.

Health is LeadMove watching your deliveries to a buyer and reacting when its endpoint stops accepting them. The badge sits next to the buyer's name, and a banner appears on the buyer page as soon as it isn't healthy.

BadgeWhat it means
HealthyThe last delivery succeeded. Nothing to do.
Degraded3 deliveries in a row failed. Deliveries keep being attempted and retried.
Paused5 deliveries in a row failed. Deliveries to this buyer are blocked for 30 minutes, then it resumes on its own.
No dataNo delivery has been attempted yet.

A failure counts once per lead, after LeadMove has exhausted its retries — not once per attempt. One successful delivery resets the counter to zero and clears any pause.

What trips it

Delivery failures, and only those: a webhook returning errors, an email bouncing, a sheet or endpoint refusing the row. It's a symptom of the buyer's destination, so fix it there — see Delivery methods.

A lead the buyer's endpoint rejects in its 2xx response (see Reading the buyer's response) is not a failure: the endpoint answered, so it counts as healthy. Rejections show up in the Acceptance rate instead, below.

Health has nothing to do with lead quality, disputes or the buyer's own status. A buyer can be Active and Paused at the same time: Active is your decision, Paused is the failure counter.

Don't confuse it with a temporary closure either. Paused by the circuit breaker means the buyer's endpoint is failing and LeadMove stopped trying; Closed until means someone declared the buyer away until a date. One is a symptom to fix, the other is a plan that expires on its own.

What a paused buyer does to distribution

A paused buyer is taken out of the draw: distribution skips it and the lead goes to another eligible buyer, in the same tier or a lower one. The lead page's routing trace names the buyer and says Paused by circuit breaker, with the time it comes back.

A pause shrinks your reach, it doesn't burn leads

Leads keep flowing while a buyer is paused — to everyone else. If it was the only buyer that matched, the lead ends up unrouted rather than failed. Either way, fix the endpoint: a paused buyer buys nothing.

On the pipeline canvas, the health summary counts paused and degraded buyers so you can see at a glance that your effective reach is smaller than your buyer list suggests.

Resetting health

Fix the endpoint first, then hit Reset health in the banner on the buyer page. It sets the buyer back to healthy and clears the failure counter immediately, instead of waiting out the 30 minutes.

If the endpoint is still broken, the next failures will trip it again — the reset isn't a fix, it's a "try again now".

Common questions

A buyer went paused overnight. What happened to its leads? They went to your other eligible buyers. Any that had nowhere else to go are sitting unrouted in your leads list, and deliveries that failed before the pause tripped are on the lead pages — fix the endpoint, then retry the delivery or assign the lead to another buyer.

Why does it say degraded when the buyer is receiving leads fine now? Degraded is set on 3 consecutive failures and cleared by the next success. If the badge is stale, one successful delivery — or Reset health — clears it.

Does a deferred or held lead count as a failure? No. Only a delivery that actually failed after retries counts. See Lead statuses explained.

Can I turn health off for a buyer? No. It's automatic, and the pause is short by design.

Acceptance rate

When a buyer's webhook delivery method reads their response, the buyer's page swaps its Success rate card for an Acceptance rate as soon as one of their deliveries has been rejected: the share of leads their system took, among the leads it answered. Failed deliveries (no answer) stay out of it. The sub-line counts the leads rejected by the buyer over the selected period, and the leads list filter Delivery status → Rejected by buyer lists them.

A low acceptance rate is a data conversation, not an endpoint problem: open a few rejected leads, read the buyer's reason on the delivery, and fix the source or the mapping.

On this page