Summary view, cloned from a Claude Design artifact. For the full scoping doc — phasing, vendor decision, JobTread integration detail — see Revenue Attribution (full).
We can prove people find the website. We can't yet prove which of them become customers.
Why this matters: Everything we currently optimize against — rankings, clicks, form submits, calls tapped — is a proxy. Did the work produce sold jobs, and which ones?
We need a lead to be traceable from the moment it lands, through intake, through the quote, to a signed contract in JobTread — and back again to the channel that produced it.
GA4, 90 days (Apr 25–Jul 23, 2026)
Visit
4,771 sessions / 90 days
Channel known via GA4 (organic, paid, direct, referral).
Form submit
76 · 1.6% of visits
GA4 lead_form_success confirms a real submission, sitewide. Raw count runs high — bot/spam attempts inflate it; ~55–65 is the spam-adjusted estimate.
Phone tap
125 · 2.6% of visits
Only proof is a tel: click. GA4 can't tell us if the call connected, how long it ran, or who called — and this is the larger of the two lead channels.
Lead logged
No connection to the end job — nothing confirms the lead ever reached intake, or reached JobTread at all.
Automated updates
No automated sales communication between first contact and a signed contract — follow-up depends entirely on someone remembering.
Quoted → Sold
Lives in JobTread, with no field tying it back to the visit, channel, or lead that started it.
Post-sale sequence
No ongoing customer data — no newsletter, review, or referral follow-up once a project closes.
Visit
Channel known for every visitor, including Safari/Firefox — no privacy-browser blind spot in Ads attribution.
Form submit
Verified event + Lead ID minted + source, city, service captured.
Phone call
Tracked number confirms connect, duration, and source — same confidence as a form.
Lead logged
Every form and call posts straight into JobTread via its API, tagged with its Lead ID — nobody has to remember to key it in.
Automated updates
Status texts and reminders keyed to pipeline stage keep the customer in the loop between first contact and a signed contract, without relying on someone remembering to follow up.
Quoted → Sold
Tracked in JobTread as today, but the Lead ID rides along — a sold job traces cleanly back to the page and channel that produced it.
Post-sale sequence
Automated newsletter opt-in, timed review and referral requests — the same source/Lead-ID data carrying through so the team isn't relying on memory to follow up, and the customer's journey doesn't just stop at the signature.
Working hypotheses from what's documented and discussed so far — not settled facts. Flag anything below that doesn't match what you're actually seeing.
Analytics only tracks that someone clicked the phone number on the site. We don't know if the call was answered, it's duration, or if it became a lead.
If so: a tracked number, kept static and NAP-safe, so a tap becomes a real recorded call.
Our read is that form and phone calls can be worked entirely off email and voicemail without ever becoming a JobTread record — but this keeps analytics from matching the source to the outcome.
If confirmed: push every form submit and tracked call into JobTread automatically via its API.
As far as we know, even a lead that gets entered loses its source, city, and service on the way in — so a sold job can't be traced back to what produced it. Worth checking whether JobTread already has a field for this that just isn't being used.
If not: carry the Lead ID and source tag into the JobTread record, end to end.
No documented process for lead communication before the sale or customer data after it — some of this may already happen informally, just not written down anywhere.
If not: define a short sequence on each side of the sale — SMS/email keyed to pipeline stage before close, newsletter opt-in and timed review/referral requests after — built on the same source/Lead-ID data already flowing into JobTread.
One move per question above — each confirms the hypothesis before we build anything on top of it.
Answers the phone question: do we care about phone lead tracking? If so, a second decision follows — dynamic number insertion gets per-channel and per-page attribution but costs more; a single static number is cheaper and simpler but only gives aggregate call volume. Either way, layered with call recording, connect confirmation, and duration.
Decision neededAnswers the intake question: pull a month of form and phone calls and check them against JobTread — how many became a real record versus how many were worked off email or voicemail and never logged anywhere. Turns "we think leads are falling through" into an actual number.
This weekAnswers the CRM question: check whether JobTread already has an unused field for source/city/service before building around an assumption. Then push form and tracked-call leads into it directly via its documented API (app.jobtread.com/docs), carrying the Lead ID the website already mints — so nothing has to be re-typed to stay trackable.
Once 1 & 2 are settled