Revenue proof layer

Manual booked-job and revenue report for Desert Peak Heating & Air.

This report shows how campaign pages can be judged by booked jobs and revenue, not only form fills. It uses local demo outcome rows and keeps invoice/payment matching API-gated until authorization exists.

Review campaigns
Mode
manual-demo
$36,780
demo attributed revenue
81
leads
53
booked
65.4%
rate

Campaign page outcomes

AC repair in Phoenix landing page

manual proof
/ac-repair-phoenix
campaign
48
leads
31
booked jobs
$28,640
demo revenue
64.6%
booking rate
Mapped objects
AC RepairResidential HVACSummer AC DemandPhoenix MetroAC DiagnosticPageToJob appointment request
Proof source

Demo outcome row / supplied export stand-in

Use supplied exports or customer-reviewed totals until API-backed matching is approved.

Comfort Club membership page

manual proof
/maintenance-plan
membership
33
leads
22
booked jobs
$8,140
demo revenue
66.7%
booking rate
Mapped objects
Maintenance Tune-UpResidential HVACMaintenance Member ReactivationComfort ClubSeasonal Maintenance VisitPageToJob appointment request
Proof source

Demo outcome row / supplied export stand-in

Use supplied exports or customer-reviewed totals until API-backed matching is approved.

Water heater repair legacy page

blocked
/water-heater-repair
service
0
leads
0
booked jobs
$0
demo revenue
0%
booking rate
Mapped objects
Water Heater RepairResidential PlumbingWest Valley
Proof source

No outcome row yet

Fix inactive or missing Titan Map references before using this page in revenue reporting.

Attribution eligibility

Lead and booking capture

manual proof

PageToJob can report website leads and demo booked-job rows manually before ServiceTitan API access.

Booked job matching

api gated

Matching to ServiceTitan booking/job IDs requires approved CRM/JPM scopes and customer authorization.

Invoice and payment revenue

api gated

Closed-loop revenue needs eligible accounting access or customer-supplied exports.

Campaign/source attribution

eligible

Campaign pages already carry explicit UTM/source bindings and Titan Map references.

Sync boundaries

  • - Do not call ServiceTitan synchronously from the lead form.
  • - Do not claim invoice/payment-backed revenue until scopes and customer authorization are approved.
  • - Use stable entity/export data before relying on arbitrary report definitions.
  • - Keep API-backed sync asynchronous, idempotent, and operator-visible.

Revenue reporting limits

  • - This report uses local/demo outcome rows and manual proof assumptions only.
  • - ServiceTitan booking, job, invoice, and payment matching requires customer authorization, eligible modules, granted scopes, approved app access, and durable private storage.
  • - Revenue shown here is demo data for product validation, not verified customer financial reporting.