Read a lead timeline
This article shows how to open a lead and read its timeline so you can see who was tried, who won, and why someone rejected or was skipped. The timeline is the fastest truth source during testing and early go-live.
This article shows how to open a lead and read its timeline so you can see who was tried, who won, and why someone rejected or was skipped. The timeline is the fastest truth source during testing and early go-live.
Use it for single-lead diagnosis. Switch to Rejection Reasons when the same cause repeats across many leads.
What is the lead timeline?
Every lead has a detail view with a timeline of processing and delivery events. Operators use it to answer:
- Did the lead enter the campaign?
- Did a rule or validation reject it?
- Which buyers were eligible?
- Who was tried, in what order?
- Who won?
- What reject or skip reasons appeared?
Dashboard totals cannot replace that story for a single failure.
Prerequisites
- Permission to open Leads
- At least one lead in the campaign (test or live)
- Rough knowledge of which buyer and supplier you expected
Open a lead and read the timeline
- Open Leads from the sidebar.
- Filter by campaign, date, status, buyer, or supplier if the list is long.
- Click the lead row to open detail.
- Confirm header basics: campaign, status, supplier, traffic source if present, and timestamps.
- Scroll the timeline from the first event to the last.
- Note validation or rule outcomes before distribution events.
- Read the strategy panel to see how the lead was routed and sold.
- Note each buyer attempt: tried, skipped, rejected, or won.
- Read reject reasons in plain language when shown.
- Compare the winner and final status with what you expected from distribution and delivery setup.
- Only after you understand the named cause, change configuration and re-test.
The strategy panel
Above the buyer attempts, a short panel explains the run. It names the strategy that sold the lead, with a one-line hint, then adds rows for whatever applies:
| Row | What it tells you |
|---|---|
| Routed by | Which step on the How leads get sold card matched. It names the step, or says Campaign default — no rule matched when the lead fell through to Everything else. On a ping/post lead the step is pinned from the ping leg, so bids are ranked by the strategy that produced them. |
| Winning tier or Quoting tier | The tier that won, on an Advanced or Tiered Bidding run |
| Reach | Who was actually contacted, which is rarely every buyer listed. Inactive buyers never enter, and a direct-post buyer on a ping/post campaign is priced from its contract with no outbound call. |
| Outcome | How the run ended |
| Post leg | On a ping/post lead whose post was rejected before any buyer was ranked, the stage it died at |
If the panel says the step was forced or overridden, something bypassed normal routing. A buyer integration test always runs waterfall, and a redistribute can force the strategy.
Filter steps
Where a rule decided a buyer's fate, the timeline writes it as a sentence naming the field, the condition, and the value the lead actually sent, for example state is one of TX, OK, NM. Every buyer shows a filter step, including buyers no rule turned away.
If a redistribute waived a buyer's rules, the step says so rather than reporting a verdict that never ran.
Retries and earlier attempts
A redistributed lead has more than one attempt against the same buyer. The current attempt reads first, and earlier ones collapse behind a toggle that counts them, for example 2 earlier attempts. Open one and you get the same detail as the current attempt: full request, response, and rule outcome.
How to use the timeline with other tools
| Goal | Use |
|---|---|
| Debug one bad lead | Lead timeline |
| Confirm a dry run | Lead timeline after a test post |
| Give a lead another run at the buyers | Redistribute, from the lead's row menu on Leads |
| Find a repeating cause | Rejection Reasons overview |
| See which party drifted this week | Dashboard and analytics |
The redistribute drawer lists every buyer with the reason it refused the lead the first time, so you can see what would need to change before you retry. A buyer that already returned the lead is shown as blocked rather than hidden. Each retry appears on the timeline as a new attempt.
Common timeline readings
| What you see | Likely meaning |
|---|---|
| Reject before any buyer | Fields, lead filter rules, or duplicates |
| Buyer skipped | Inactive, outside schedule, capped, or turned away by a delivery rule |
| Buyer rejected | Buyer delivery response or buyer rules refused the lead |
| Clear winner | Distribution and delivery completed for that buyer |
| Stored or emailed outcome | Delivery method did not use a standard HTTP post path |
| Routed by naming a step you did not expect | An earlier step on the How leads get sold card matched first |
| Campaign default — no rule matched | The lead fell through every step to Everything else |
| An attempt marked as a retry | The lead was redistributed. Open the earlier attempts to compare. |
Exact labels vary by status and method, but the sequence still tells you where the path stopped.
Tips and gotchas
- Read top to bottom. Later delivery events make no sense without earlier eligibility context.
- A reject reason on one buyer is not always the campaign-level outcome if another buyer still won.
- Check Routed by before you touch distribution settings. A surprising winner is often the right buyer for the wrong step.
- Reach is the honest count of who was contacted. Do not read a listed buyer as a buyer that received a request.
- After hours, check schedules before rebuilding rules.
- On a redistributed lead, read the current attempt first. The earlier ones are collapsed for a reason.
- For tests, keep the lead id or timestamp in your notes so you reopen the same record after a fix.
- When five leads share one cause, stop sampling timelines and open Rejection Reasons.
Expected result
You can open any lead and explain its outcome from the timeline without guessing, and you know when to escalate from one lead to pattern tools.
Related articles
Frequently asked questions
Comments
No comments yet — be the first to share your thoughts.