In this article
- What does lead-to-revenue tracking prove?
- Which records must stay separate?
- How does the arithmetic work in a small example?
- What happens to unmatched or late records?
- How do attribution and privacy affect the report?
- What should a buyer request before approving delivery?
- Who builds the tracking behind the report
Which records must stay separate?
An accepted request, qualified opportunity, booked appointment, won deal and payment answer different questions. Give each stage a definition, responsible system and recorded time. A business can win work before receiving money, receive a deposit before completion or issue a refund later. The report should preserve those differences.
| Stage | Evidence | Does not establish |
|---|---|---|
| Inquiry received | Accepted record | Commercial qualification |
| Booking | Confirmed reference | Attendance |
| Won opportunity | Sales outcome | Collected cash |
| Settled payment | Transaction and currency | Net profit |
| Refund | Original payment | Another sale |
How does the arithmetic work in a small example?
Consider fictional payments of USD 600 and USD 400 for one opportunity, followed by a USD 100 refund. Collected payments total USD 1,000; net collected cash after that refund is USD 900. Keep the invoice and opportunity value outside this total so importing them does not count the same business again.
These amounts explain arithmetic only. They are not AI Growth Systems prices, customer outcomes or forecasts. Keep the source currency and settlement status. Another currency needs an explicit conversion policy before totals can be combined.
| Record | Amount | Treatment |
|---|---|---|
| Payment A | 600 | Count once |
| Payment B | 400 | Count once |
| Refund of A | 100 | Subtract once |
| Net collected | 900 | 600 + 400 - 100 |
What happens to unmatched or late records?
Leave an outcome unmatched when the required identifier or relationship is missing. Assign an owner to investigate it without guessing the source. A late payment or corrected status may change a prior report; preserve the original reporting version and explain the update. Treat missing data as unavailable.
Replay an event and check that no total changes. Include an unavailable source, restored delivery and a correction after the report date. Receiving a provider notification does not prove that every source record has arrived.
How do attribution and privacy affect the report?
Retain a source only when a permitted record supports it, and state the attribution model and time window. Keep unattributed outcomes visible. A customer can describe how they discovered the business, but that answer differs from an observed referral. Search and AI visibility observations should not become invented person-level browsing histories.
What should a buyer request before approving delivery?
Request the event definitions, source-to-report map, exception list and a reproducible test record. Confirm who corrects mismatches and who reviews the next period. Use a fictional demonstration to inspect the method, then require separate authorized evidence for a client deployment. Agree costs before starting ongoing work.
Who builds the tracking behind the report
AI Growth Systems connects website forms, call tracking and CRMs for service businesses, with Javier Socarras leading the work from Deerfield Beach. We set up the shared IDs that make this reconciliation possible, test them with sample inquiries and leave unmatched records visible in the report. You'll see what the data proves and, just as clearly, what it can't.
Sources and further reading
Read the original guidance alongside the practical examples in this article.