Practical agency guide
Read the report with the records behind it.
Use dates, original sources and recorded outcomes together to understand the results and identify what still needs checking.
1. Start with the submission period.
Periods group leads by original submission timestamps in UTC. Outcomes are the currently recorded results for those leads, even when updated later.
- A March lead won in April belongs to the March submission cohort.
- April submissions do not represent all jobs won in April.
- Sale-date reporting and previous-period comparisons are not available.
2. Separate outcomes from missing results.
Read open, won, lost and mapped stages according to the client’s workflow. An estimate or appointment is not automatically a won job.
- A missing result may not have been recorded or matched.
- Open a campaign to inspect leads with identical dates and scope.
- Resolve unmatched or stale records before drawing a conclusion.
3. Check the amount and currency.
Won contract value sums recorded contract amounts on won leads. It does not establish collected revenue, profit or return on ad spend.
- Missing amounts differ from recorded zero.
- Currencies stay in separate totals; no conversion is implied.
- Report layouts do not add payments, spend or ecommerce data.
4. Follow the original source and campaign.
Attribution connects the source and campaign captured at intake to the currently recorded outcome.
- Unknown attribution stays visible rather than receiving assumed credit.
- Matching leads and campaign CSV retain the same scope.
- This is not multi-touch attribution or proof that one campaign caused the result.
5. Read exclusions and missing-data notes.
Authorized exclusions remove selected records from report totals without deleting the lead. Reasons and missing-data notes explain differences from an unfiltered lead list.
- Check selected dates and source/campaign before comparing counts.
- Review exclusions instead of assuming every stored lead is included.
- Missing territory data does not establish an outside-area lead.
6. Check CRM freshness separately.
Fetch time tells you when recorded data was retrieved. Health and last successful sync describe the CRM path. A recent fetch can contain stale or incomplete outcomes.
- Investigate failed or stalled syncing with the owner.
- Report CSV is available according to workspace permissions.
- PDF, scheduled reporting and public unauthenticated sharing are not available.
See the report with an example.
The public preview uses illustrative data.