Unique Lead Reference
An authorized match connects activity to a particular inquiry and service.
One homeowner asks for a roof replacement estimate. Follow that single lead from the company that generated it to the buyers who received it and the outcomes they reported.
A buyer seeing this request for the first time can check its earlier purchases, conversations and estimates before deciding whether to buy.
Generators record the inquiry and its distribution. Buyers report purchases, contact attempts, estimates and sales. Permitted events connect what happened before a buying decision with what happened after it.
Connect the inquiry to a protected source.
Follow confirmed activity in the right time window.
Apply buying rules and measure later results.
A persistent internal identifier lets the registry recognize a participating organization across transactions. It can distinguish six buyers from one repeat buyer without disclosing their identities to a competitor.
An authorized match connects activity to a particular inquiry and service.
A persistent internal reference lets the registry recognize a generator across transactions.
Roofing, HVAC, plumbing and remodeling histories describe different requests.
The date helps distinguish a fresh request from activity on an earlier project.
Count distinct recipients using permitted references or aggregate totals.
An offer, delivery, acceptance and confirmed purchase each describe a separate event.
One homeowner in Palm Beach County asked for a roof replacement estimate. Six roofing companies purchased that same inquiry. The internal record shows who generated it, when each buyer purchased it, and what each buyer reported afterward.
Roofing Buyer 1 · Purchased
Roofing Buyer 2 · Purchased
Roofing Buyer 3 · Purchased
Roofing Buyer 4 · Purchased
Roofing Buyer 5 · Purchased
No outcome reported.
Roofing Buyer 6 · Purchased
No outcome reported.
· Already Hired a Contractor. Reporting buyer not provided.
Only authorized LeadRegistry staff and systems can link these network IDs to company names.
These counts all belong to one roof replacement inquiry. The buyer sees permitted activity and outcomes while company names stay private.
Buyer minimum: 70/100
Distribution, contact and outcome patterns retain their value when buyers see only the evidence their relationship permits.
Six purchases by six companies imply wider distribution than six transactions with one company. Internal references distinguish the two.
Protected source records support analysis of contact rates, conversions and recurring distribution patterns across authorized reports.
Participants can share permitted dispositions while keeping supplier lists, customer identities and competitors’ transaction details private.
The same confirmed service inquiry can arrive through several sellers. LeadRegistry keeps their submissions and transactions separate, while combining the history you have permission to see.
Seller 1 reaches Buyers 1, 2 and 3. Seller 2 reaches Buyers 1, 4 and 5. Buyer 1 appears twice, so six purchases represent five distinct buyers—not six. Each chargeable purchase remains a separate transaction.
Automatic checks flag possible cross-seller matches even when seller lead IDs differ. History shows the matching evidence and review status. Unconfirmed flags keep their histories, buyer counts and scores separate. Confirmed shared references link the same service and original inquiry, with agreeing identifiers and active permissions. Contact details alone do not merge different projects. Seller labels protect identities; circulation through two sellers does not prove a resale between them.
Try the multi-seller lead example Try possible-match reviewSix prior purchases tell you how widely an inquiry traveled. Add three estimates and a recent report that the homeowner already hired someone, and the same six purchases can support a different decision.
Count distinct participating companies with a recorded delivery or purchase. Check which event the count represents.
Compare circulation over 7, 30, 90, 180, 365 or 730 days. Six purchases last month have a different meaning from six over two years.
Distinguish a reported conversation from an unanswered call or a message left.
Look for quotes or proposals from multiple providers and how recently they were issued.
Not Interested, Already Hired a Contractor, Project Completed, No Longer Looking, Appointment Scheduled, Estimate Provided, Sale Completed, Unable to Contact and Invalid Inquiry each tell a different story.
Read the date and available verification, dispute or correction status. A new HVAC inquiry can still be worth pursuing after a declined estimate three months ago.
The generator recorded the original inquiry on Oct 27, 2026. Each entry below belongs to that same lead. Follow a label such as Roofing Buyer 1 to see when that buyer purchased the lead and what it reported later.
Palm Beach County, Florida · Protected Source Reference
6 confirmed purchases, 4 reported contacts, 3 reported estimates and one reported hiring decision in 30 days.
Each purchase is confirmed separately. An offer proposes a transaction, a delivery records a handoff, and a pre-ping checks the rules. Only a confirmed purchase counts as a purchase here.
Multiple providers have worked this inquiry. Its distribution, score and recent hiring report trigger this buyer’s rules today. Try changing those rules in the existing roofing demo.
Explore a Windows timeline in the authorized workspace. See example history →
A roofer might cap previous buyers. An HVAC installer might care more about a recently completed installation. Configure the policy around the service and the work your team can still win.
Set the maximum number of previous buyers your team will accept.
Choose how far back a delivery, purchase or disposition should count.
Set a score floor and decide how to handle opportunities near it.
Flag or reject a recent unfavorable report within its applicable window.
Identify inquiries already worked or quoted by several providers.
Evaluate roof replacements and HVAC installations against the rules for each trade.
Meets this buyer’s rules. An offer, current interest and a conversion each need separate confirmation.
The buyer may verify current interest and choose to buy. The roofing demo calls this result “Review.” Track the purchase separately for analysis.
A hard rule or score cutoff rejects this opportunity under the buyer’s policy.
The timeline above follows one inquiry. This report groups purchases across many inquiries so a buyer can see how its rules performed.
Report conversations, appointments, estimates and completed sales after the purchase.
Compare clear accepts with on-the-margins leads your team chose to purchase.
Compare outcomes across score cutoffs, distribution limits and policy versions.
Compare contact and conversion rates, average lead cost, cost per customer and estimated avoided spending.
Use permitted source-level aggregates to identify patterns in distribution and sales.
Imagine your company purchases 1,000 roofing leads. You divide them into two groups based on their LeadRegistry scores and purchasing criteria.
| Performance Metric | Clear Accepts | Borderline Purchases |
|---|---|---|
| Leads Purchased | 700 | 300 |
| Average Cost per Lead | $85 | $85 |
| Total Lead Spending | $59,500 | $25,500 |
| Customers Acquired | 105 | 15 |
| Conversion Rate | 15% | 5% |
| Customer Acquisition Cost | $567 | $1,700 |
Clear accepts converted at 15%, compared with 5% for borderline purchases.
Clear-accept leads generated customers at roughly one-third the cost of borderline leads.
By analyzing your own results, you could adjust your minimum acceptable quality score, reduce the maximum number of previous buyers allowed, or tighten rules concerning recent unfavorable dispositions. Over time, this creates a more informed purchasing process.
The cohorts show an association. Isolating the effect of a single rule requires further analysis.
Inspect distribution and earlier work, screen recent unfavorable dispositions and apply your buying rules. Compare conversions, acquisition cost and estimated avoided spend as you refine those standards.
Explore Solutions for Lead BuyersPre-ping connected buyers against their own requirements. Use authorized source and routing results to reduce unsuccessful deliveries and focus on partners likely to accept the inquiry.
Explore Solutions for Lead GeneratorsCross-network views use permitted counts, summaries or scoped labels. A buyer can see its own authorized transactions. A generator name may appear where disclosure is permitted; an anonymous source is shown as “Not provided.”
Duplicate detection answers whether an inquiry has appeared before. Lead history also shows how widely it circulated, the work providers reported, and how that evidence fits a buyer’s purchasing rules.
A newly verified inquiry may change the evaluation. Consider the service, dates, freshness of the request and any corrections to earlier reports.
Participating buyers contribute authorized outcomes through supported imports, their CRM or lead-management integration, or the API.
Ordinary generator access covers its own authorized relationships. Other participants’ identities and supplier networks stay outside that view.
The score describes a purchasing opportunity under one buyer’s rules. It makes no judgment about the person who made the inquiry.
Yes. Buyers choose distribution limits, lookback windows, relevant outcomes and minimum scores for their business.
A passing check is a purchasing signal. Consumer interest, acceptance of an offer and the eventual sale each need their own evidence.
See where an inquiry has been, what participating providers reported and whether it meets your standards before you commit your budget.
Know the History. Evaluate the Opportunity. Buy With Confidence.