Your BuildBook pipeline shows signed remodels. Google and Meta never find out.
Leads reach BuildBook because someone on your team types them in under + New Opportunity, or because a visitor used the contact form on your BuildBook Portfolio. Either way the ad click is gone by the time the client eSigns your proposal. We keep the click on your own website, link it to the opportunity, and send approved proposals back to your ad accounts at the estimate value.
Free30 minutesNo obligation
BuildBook · what breaks
What goes wrong when ads feed BuildBook
- 01
My ads say I got leads, but BuildBook has no idea where they came from
We found no documented lead source field on a BuildBook opportunity, so a Google Search lead and a neighbor's referral look identical, and you can't say which campaign paid for which remodel.
- 02
Somebody retypes every lead by hand
BuildBook documents no Zapier app, webhook or API for creating opportunities. Your office copies leads in by hand, and the ad data stays behind in the inbox.
- 03
Google keeps buying small jobs
Your ad accounts only see the form fill. A deck repair and a basement finish count the same, even though the Budget field on each BuildBook opportunity tells them apart, so smart bidding chases cheap form fills instead of the projects you'd actually sign.
- 04
The signature comes long after the click
A remodel can sit in Estimating while you publish a new estimate version after every round of changes. By the time the client eSigns and you move the opportunity to Won, nothing ties that approval back to the ad that started it.
BuildBook · the fix
What changes once your ads can see BuildBook
Every paid lead keeps its click
Captured on your website form and stored first-party, with a short reference your team pastes into the opportunity notes.
Bidding learns from approved proposals
When a client eSigns and the opportunity moves to Won, the approved estimate total goes back to Google Ads and Meta.
Your stages turn into ad reporting
New, Qualifying, Estimating and Won counts per campaign, built from the weekly stage update your team logs, so you see where paid leads stall.
BuildBook · architecture
What BuildBook actually lets you hook into
BuildBook's help center is short on integrations. These are the pieces it documents, plus what we check before relying on anything else.
- 1
Opportunities with stages
Created manually or from the Portfolio form, then moved by hand through New, Qualifying, Estimating, Won and Lost or Archived. Only the Team Owner and Team Admins can open them.
- 2
Proposal approval by eSignature
Clients approve from a shared link with a typed or drawn signature, and the owner is notified. That approval is the event worth sending.
- 3
Portfolio contact form
Opened from the Contact Us button on your buildbook.co/pro page. Each submission creates an opportunity whose title starts with Portfolio Submission. BuildBook documents no way to add your own tracking code there.
- 4
QuickBooks Online sync
Invoices push one way, from BuildBook to QuickBooks Online. Useful for checking revenue, not for sending ad data.
- 5
No ad, analytics or automation connectors documented
No Google Ads, GA4, GTM, Meta Pixel, Zapier or API docs turned up, so conversions go through our container and offline uploads. We confirm whether your plan can export opportunities.
BuildBook · diagnose
Where BuildBook tracking breaks, in diagnostic order
Start before BuildBook, because on this tool the click is usually lost before anyone opens an opportunity.
- 01
Submit a test lead from an ad-tagged URL
Check that your form stores the GCLID and fires exactly one conversion.
- 02
Find where ad traffic actually lands
Ads pointed at your BuildBook Portfolio send leads to a page you can't tag.
- 03
Check how the office enters leads
If the reference or email doesn't reach the opportunity, the later match fails.
- 04
Compare Won opportunities with uploaded conversions
Per opportunity, over a closed month, with the approved estimate amount.
- 05
Look for change orders counted as new sales
Added work on a running project isn't a new customer.
BuildBook · prove
The QA evidence — BuildBook
Run on a real inquiry through your live website and a real proposal approval in BuildBook, not a preview.
Source of truth
BuildBook opportunity records: stage history, approved estimate version and amount, and the eSignature date in the Approval section
- One test lead from an ad-tagged URL, with the click stored and the reference visible on the BuildBook opportunity.
- Exactly one lead conversion per inquiry in Google Ads and Meta, sharing an event ID across browser and server.
- An eSigned test proposal uploaded once, at the approved estimate amount.
- Lost and Archived opportunities confirmed absent from the money conversion.
- Portfolio Submissions without a click confirmed outside paid reporting.
- Won opportunities matched one by one against each ad platform over a closed window.
- The same check repeated 30 days later.
BuildBook · free audit
What we check in the free audit
- Submit a test lead from an ad-tagged URL
- Find where ad traffic actually lands
- Check how the office enters leads
- Compare Won opportunities with uploaded conversions
- Look for change orders counted as new sales
Checked against
BuildBook opportunity records: stage history, approved estimate version and amount, and the eSignature date in the Approval section
Free30 minutesNo obligation
BuildBook · when not to buy
When you don't need this on BuildBook
Plenty of BuildBook users run on referrals, and that's fine.
- If nearly every opportunity comes from past clients, referrals or your Portfolio, ad attribution won't change your decisions.
- If you spend a few hundred dollars a month on one campaign and sign a handful of projects a year, asking 'how did you hear about us' may be enough.
- If your website form already stores the click and someone uploads Won BuildBook opportunities to Google Ads every week at the signed estimate amount, you're doing the hard part already.
- If the only problem is your website form counting each inquiry twice before it ever reaches BuildBook, that's a quick fix and we'll tell you how to do it yourself.
BuildBook · what we deliver
The event map on BuildBook
Website inquiry submitted
Fired once from a confirmed submit on your site, browser and server sharing one event ID, with GCLID, fbclid and UTMs stored.
Opportunity created in BuildBook
Matched to the stored click by reference code, email or phone.
Qualifying
Sent when the opportunity leaves New, with the BuildBook budget field as a size signal.
Estimate sent
Logged when the opportunity reaches Estimating, so you see which campaigns produce bid-worthy projects.
Proposal eSigned, opportunity Won
The money conversion, valued at the signed estimate version and uploaded to Google Ads and Meta.
Excluded on purpose
Past-client opportunities, change orders, Lost or Archived opportunities and click-less Portfolio Submissions stay out of acquisition.
Written guarantee
95%+ tracking accuracy
Measured against BuildBook opportunity records: stage history, approved estimate version and amount, and the eSignature date in the Approval section. Miss it and we keep working at no cost.
From $400 · See packages
FAQ
BuildBook questions, answered
Not that we could find. BuildBook's help center documents a QuickBooks Online integration and nothing for Google Ads, GA4, the Meta Pixel or Zapier, so conversions have to come from your website and from offline uploads.
BuildBook doesn't document a place for tracking code on the Portfolio. Send paid traffic to your own website instead and keep the Portfolio for referrals and people who already know you.
Store the Google click ID when the lead fills in your website form, then upload it with the approved estimate amount once the client eSigns in BuildBook. Google calls this offline conversion import.
Only if the link to the ad gets lost. We give your team a short reference to paste into the opportunity, so the match survives manual entry.
The approved estimate version the client signed. Change orders and later invoices are better kept for revenue reporting, not for training acquisition bidding.
Yes. The same Won opportunities go to Meta's Conversions API as CRM events, so Meta can optimize toward homeowners who sign a proposal instead of ones who stall at Qualifying.
More on BuildBook
- Enhanced ConversionsEnhanced Conversions enrich the conversions that already fire. First we make sur…
- Meta CAPIA one-click CAPI integration sends thin events. That's why your Event Match Qual…
- Cross-Domain TrackingYour checkout provider is the best performing traffic source in your GA4 account…
RELATED GUIDES
Booking tools beside BuildBook, and what their bookings feed
- Estimate RocketEstimate Rocket conversion tracking: your ads see the form fill, never the signed proposal
- XactimateYour ads learn from every wet-carpet call. The paid claims sit in Xactimate.
- D-ToolsD-Tools conversion tracking: know which ads turn into signed proposals
- JoistYour Joist estimates get signed. Google Ads never finds out.
- HoverHomeowners design their new siding in Hover. Your ads never hear about it.
- Invoice2goClients tap Approve estimate in Invoice2go, and Google Ads is none the wiser
- Contractor ForemanContractor Foreman knows which estimates got approved. Your ads don't.
- KnowifyKnowify conversion tracking: the contract gets signed, the job goes active, and your ads never find out
Free · 30 min
Find out which ads actually sign BuildBook projects
WhatsAppFree30 minutesNo obligation
