Paying Angi, Thumbtack, Yelp and Google, with no idea which one books your jobs
Each platform's report makes its own spend look worth it, and none can tell you which leads became paid jobs, because the journey happens inside their app and on their phone numbers. We can't move where their visibility ends. We tag every lead by source when it reaches you, match it to the job in your records, and hand you one monthly sheet: cost per booked job for every source, next to your Google and Meta ads.
Free30 minutesNo obligation
Marketplace lead attribution · what breaks
Why marketplace spend is hard to judge
- 01
Every platform grades its own homework
Each dashboard counts leads its own way, so budget follows the best-looking report instead of the source that books the most jobs.
- 02
LSA leads arrive without a click ID
Calls run through Google's forwarding number and messages through anonymized proxy numbers. You pay per lead, yet no lead links to a job until someone matches it by hand.
- 03
One homeowner, three charges
The same person finds you on Yelp, calls from LSA and books through Angi. You may pay for that customer more than once, and every platform claims the job.
- 04
Credits you were owed and never claimed
Angi and Thumbtack take credit requests for bad or duplicate leads only within 45 days. Once nobody files in time, that money is gone.
Marketplace lead attribution · the fix
What changes — Marketplace lead attribution
One number per source that matters
Cost per booked job for Angi, Thumbtack, Yelp, LSA, Google Ads and Meta, from your own job records.
A clear line between tracked and reconciled
Own-site ad leads tracked click to paid job; marketplace leads matched by phone and date, with a stated match rate.
Clean signals for the ads you control
Booked jobs that started with a click to your own site feed Google Ads and Meta bidding. Marketplace jobs stay out of it.
Marketplace lead attribution · architecture
Which tracking methods reach which platform — Marketplace lead attribution
The methods differ by how much of the journey each platform lets you see. Where a method stops, the page says so.
- 1
Own-site events and offline conversions (M1, M4, M6)
Google Ads and Meta clicks to your site keep their click ID through to the booked job. Only this part carries the 95%+ guarantee.
- 2
Call tracking per source (M5)
A static number assigned to LSA, and to any other platform that allows one, shows which calls came from it. CallRail notes the LSA number has to be entered by hand in your LSA account, not through its API.
- 3
Integrations into your job software (M4)
Jobber tags Angi clients with "Angi" as lead source; ServiceTitan selects the Angi campaign by default. ServiceTitan's sync runs one way, and neither it nor Jobber's Thumbtack sync imports leads from before you connect.
- 4
Profile clicks and platform reports (M7)
Tagged links on profiles that accept them show visits to your site, and each platform reports its own leads. Visibility ends at the click or lead, never the paid job.
- 5
Monthly reconciliation (M8)
Lead exports matched to your job records by phone, name and date, with a stated match rate. LSA message leads come through proxy numbers, so they match on name and date. For health and legal practices, no names, symptoms or case details leave your systems.
Marketplace lead attribution · diagnose
Where marketplace attribution breaks, in checking order
Start with your job records: the one list every platform must agree with.
- 01
Count jobs with no source on file
Last quarter, by job. That share is the size of the blind spot.
- 02
Search five LSA lead phone numbers in your job software
If you can't find them, nothing is joining LSA leads to work.
- 03
Look for one phone under several sources
Overlap means double counting and, often, paying twice for one customer.
- 04
Check what each integration writes as lead source
A blank or default label breaks every report built on top of it.
- 05
Compare credit requests with eligible leads
Angi requires a call attempt within 24 hours and a lead under 45 days old.
Marketplace lead attribution · prove
The QA evidence — Marketplace lead attribution
Run on real leads from your own platforms.
Source of truth
Your field-service or CRM job records (booked, completed and invoiced jobs by date), joined to each platform's lead export and charge statement
- One test lead from each platform traced from first contact to its job record.
- Source label confirmed on every integration-created client.
- LSA leads matched by phone and date, with Booked or Completed status set in Google's Leads page.
- Duplicate contacts across sources resolved to one person.
- Own-site Google Ads and Meta conversions matched record by record over a closed window.
- Match rate per platform stated, unmatched leads listed.
- The whole match run again 30 days on, against fresh leads.
Marketplace lead attribution · free audit
What we check in the free audit
- Count jobs with no source on file
- Search five LSA lead phone numbers in your job software
- Look for one phone under several sources
- Check what each integration writes as lead source
- Compare credit requests with eligible leads
Checked against
Your field-service or CRM job records (booked, completed and invoiced jobs by date), joined to each platform's lead export and charge statement
Free30 minutesNo obligation
Marketplace lead attribution · when not to buy
When you don't need this — Marketplace lead attribution
Some businesses need a spreadsheet and an afternoon.
- One marketplace and a few leads each month: ask every caller how they found you and keep a tally.
- If your job software already shows source on every job, you need a monthly report, not a build.
- If you don't record what leads become, start there. Without booked and paid jobs, there is nothing to attribute.
- If all you need is to dispute bad leads, that is an account task, and we will tell you so.
Marketplace lead attribution · what we deliver
What we build, from first contact to paid invoice — Marketplace lead attribution
Source captured at first contact
A tracking number per platform where it lets you set one, including the LSA routing number, plus integration source labels.
One lead per person
Repeat contacts matched across sources by phone, first source kept, every platform that charged noted.
Connected and qualified, by source
Answered calls and qualification per platform, with out-of-area and duplicate leads flagged for credit.
Booked and attended
LSA lead status kept current as Booked or Completed in Google's Leads page; marketplace leads matched to scheduled jobs.
Job completed and paid
Invoice value per source from your field-service software, with cancellations and refunds subtracted.
The monthly cost-per-booked-job sheet
Spend, fees and credits set against booked and completed jobs for each source, with the match rate printed beside every marketplace row.
Written guarantee
95%+ tracking accuracy
Measured against Your field-service or CRM job records (booked, completed and invoiced jobs by date), joined to each platform's lead export and charge statement. Miss it and we keep working at no cost.
Pricing
Pick the package that fits your ad spend
Browser-side starter
$400One-time fee · lifetime ownership
Repairs and verifies the browser-side setup you already have, on a live conversion. Honest about its ceiling on this platform.
- Root cause fixed, not worked around
- Verified on a live conversion
- Reconciled against your own records
- Written handover
1st-party server-side
Recommended$800One-time fee · most popular
Money events sent from your own records through a first-party container on your subdomain, so the browser can no longer lose them.
- First-party server container on your own subdomain
- Money events from your records, not the browser
- Deduplicated on a shared event ID at every destination
- First-party cookies beyond Safari's 7-day cap
- 95%+ accuracy and 8+ Meta EMQ, guaranteed in writing
Full 1st-party stack
$1,800One-time fee · lifetime ownership
Every paid channel server-side plus the offline loop, with monitoring so the next break surfaces in days.
- Everything in 1st-party server-side
- Pinterest, Snapchat, Reddit and LinkedIn CAPI
- CRM and offline conversion loop
- Refunds and cancellations corrected wherever each platform allows it
- Monitoring on every destination
FAQ
Marketplace lead attribution questions, answered
No. The search, profile view and first message happen inside their apps. We capture the source when the lead reaches you, match it to the job, and report cost per booked job per platform.
They shouldn't be. Those jobs didn't come from a Google or Meta ad, so sending them would teach bidding the wrong customers. Only own-site leads with a click ID or matched customer data go back.
No. The lead record Google provides has contact details, lead type, charge status and call recordings, with no click ID field, so matching runs on phone and date. Message leads come through anonymized proxy numbers and match on name and date instead. You can mark leads Booked or Completed, which Google says helps its systems optimize.
Google says lead history, messages and older call recordings move to the new Leads page, but performance reports do not. Download them first, then confirm your tracking number is still the lead routing number.
No. It covers conversions we can match by click: forms and calls that start on your own site from a Google or Meta ad. Marketplace and LSA figures are a reconciliation, and every monthly sheet shows its match rate.
It's the fairest comparison available: jobs instead of leads, with fees, spend and credits included. Thumbtack Opportunities are customers who already started talking to other pros, so they get their own row.
Free · 30 min
Find out which lead source books your jobs
WhatsAppFree30 minutesNo obligation
