One owner signs off the proof
Operations owns the source match, reconciliation state, portal boundary, and client-safe summary.
Revenue attribution
First Touch Revenue Attribution Guide
First Touch Revenue Attribution Guide for connecting ZartsAlgo source data, leads, booked jobs, QuickBooks records, payments, ROI, lifetime value, and client-safe proof reporting.
Attribution contract
What this proof must protect before it reaches a client.
Use this guide before connecting Search Console, QuickBooks, Thumbtack, Angi, call tracking, CRM, campaign spend, booked jobs, invoices, or payment records.
Make attribution uncertainty visible
The main risk is mixing booked value, invoiced value, collected value, and projected value in one unclear number.
Summarize accounting data
Raw invoices, payment rows, customer details, and provider payloads stay internal unless a summary is explicitly approved.
Use rollups before raw tables
Large client volume should read period rollups, attribution summaries, confidence scores, and approved proof notes first.
Baseline controls
Checks that apply to every attribution workflow.
- Confirm source label, client, service, market, campaign, period, and owner before linking revenue.
- Separate lead volume, qualified opportunities, booked jobs, invoiced revenue, and collected revenue.
- Use QuickBooks or payment data only after customer matching, invoice matching, and duplicate checks pass.
- Store confidence score, reconciliation status, source freshness, and known caveats with every proof item.
- Keep raw accounting payloads, CRM payloads, and provider rows out of the client portal.
- Compare current results with the baseline period before writing a since-joining improvement note.
- Pause publication when source, invoice, payment, or booked-job attribution is disputed.
- Use prepared MySQL reads for runtime reports and summarized fields for portal proof.
- Attach each ROI claim to an internal audit trail, report period, and approval state.
- Retest admin, portal, mobile, and generated report pages after attribution changes.
Topic checks
Specific checks for this reporting topic.
- Retest admin, portal, mobile, and public pages after report changes.
- Match lead source, client, service, market, campaign, and report period before calculating revenue.
- Separate booked value, invoiced value, paid value, and projected value in every report.
- Confirm provider freshness and source coverage before publishing an ROI claim.
- Use confidence scores for manual overrides, fuzzy matches, and missing-source records.
- Reconcile QuickBooks, CRM, call tracking, marketplace, and admin states before portal proof.
- Keep raw accounting payloads and payment details out of client-facing cards.
- Attach every metric to a baseline period, current period, owner, and approval state.
- Pause proof when a source, invoice, payment, or attribution link is disputed.
Checkpoints
Turn the topic into an admin review checklist.
Each checkpoint can become a QA step, reconciliation task, report approval rule, or portal proof gate.
Attribution checkpoint
Retest admin, portal, mobile, and public pages after report changes.
Attribution checkpoint
Match lead source, client, service, market, campaign, and report period before calculating revenue.
Attribution checkpoint
Separate booked value, invoiced value, paid value, and projected value in every report.
Attribution checkpoint
Confirm provider freshness and source coverage before publishing an ROI claim.
Attribution checkpoint
Use confidence scores for manual overrides, fuzzy matches, and missing-source records.
Attribution checkpoint
Reconcile QuickBooks, CRM, call tracking, marketplace, and admin states before portal proof.
Attribution checkpoint
Keep raw accounting payloads and payment details out of client-facing cards.
Attribution checkpoint
Attach every metric to a baseline period, current period, owner, and approval state.
Attribution checkpoint
Pause proof when a source, invoice, payment, or attribution link is disputed.
Data hooks
Tables and runtime sources to connect later.
Public pages remain static; admin and portal runtime should use prepared reads, rollups, and approved summaries.
audit_trail
Use this source for summarized admin and portal runtime only after reconciliation and privacy review.
data_quality_checks
Use this source for summarized admin and portal runtime only after reconciliation and privacy review.
leads
Use this source for summarized admin and portal runtime only after reconciliation and privacy review.
incoming_logs
Use this source for summarized admin and portal runtime only after reconciliation and privacy review.
data_sources
Use this source for summarized admin and portal runtime only after reconciliation and privacy review.
traffic_conversions_daily
Use this source for summarized admin and portal runtime only after reconciliation and privacy review.
source_coverage
Use this source for summarized admin and portal runtime only after reconciliation and privacy review.
projects
Use this source for summarized admin and portal runtime only after reconciliation and privacy review.
Client proof
What can become a clear, safe ROI story.
The strongest client reporting shows what changed since joining while preserving attribution confidence and privacy boundaries.
Lead source volume
Publish this proof only with a period, source, confidence status, owner approval, and short client-safe explanation.
Qualified rate
Publish this proof only with a period, source, confidence status, owner approval, and short client-safe explanation.
Booked job count
Publish this proof only with a period, source, confidence status, owner approval, and short client-safe explanation.
Booked revenue
Publish this proof only with a period, source, confidence status, owner approval, and short client-safe explanation.
Collected revenue
Publish this proof only with a period, source, confidence status, owner approval, and short client-safe explanation.
ROI
Publish this proof only with a period, source, confidence status, owner approval, and short client-safe explanation.
LTV
Publish this proof only with a period, source, confidence status, owner approval, and short client-safe explanation.
Since-joining delta
Publish this proof only with a period, source, confidence status, owner approval, and short client-safe explanation.