D-Tools conversion tracking: know which ads turn into signed proposals
Your ads produce inquiries, but the money shows up weeks later as a Won opportunity in D-Tools Cloud, after the site visit, design and proposal. By then nobody knows which click started it, so Google and Meta keep optimizing for cheap form fills. We tie each opportunity back to its ad and send site visits and signed proposals, at real quote value, to the platforms you pay.
Free30 minutesNo obligation
D-Tools · what breaks
What goes wrong when your pipeline lives in D-Tools
- 01
"The lead goes cold the second we type it into D-Tools"
D-Tools' docs describe no website lead form, so most inquiries get re-keyed into a new opportunity by hand. The gclid and UTMs stay behind in the form tool, and Google Ads never learns which of its clicks became a project.
- 02
"Lead source says Google, but which Google?"
Lead source on the opportunity is whatever the salesperson selects from the list. Paid search, Local Services, organic and a builder referral blur together, so you can't tell which budget is buying real jobs.
- 03
"Ads treat a doorbell camera like a whole-home theater"
A doorbell camera add-on and a whole-home media room look like the same lead to Meta and Google. Bidding chases the cheapest inquiries because it never sees the budget or quote total stored in D-Tools.
- 04
"Signed proposals never make it back to the ad accounts"
Winning the opportunity creates the project inside D-Tools and stops there. Months of design work end in a signature the ad platforms never hear about, so the campaigns that close big jobs look like they don't work.
D-Tools · the fix
What changes after we fix it — D-Tools
Every opportunity traced to its click
The inquiry's click ID and source are linked to the D-Tools opportunity ID, so a proposal signed in month three still credits the ad that started it.
Bidding learns from site visits and signatures
Google and Meta get your qualified stage and your Won opportunities, valued from the accepted quote, instead of raw form fills.
Lead source you can actually report on
Paid search, Local Services, Meta, referral and organic split by the click that started each opportunity, not by whatever got picked from the Lead source list.
D-Tools · architecture
What D-Tools actually lets you hook into
D-Tools Cloud documents an API, webhooks and CRM syncs, but no native Google Ads, GA4, GTM or Meta connection. Everything below comes from its own help docs.
- 1
Cloud API for opportunities and clients
Documented GET, POST and PUT for Opportunities and Clients, plus GET and PUT for Projects. Invoices and payments are not in the listed endpoints.
- 2
Webhooks
Created in the app with "New Webhook", using API key, basic or bearer authentication. The public docs don't list which events fire, so we confirm stage and Won events on your account.
- 3
Zapier, through an API request
No native Zapier app; D-Tools documents calling its API from Zapier's Webhooks API Request action.
- 4
Salesforce, HubSpot and Zoho CRM
Salesforce syncs client and opportunity fields, including budget and amount, and needs identical stages on both sides. The HubSpot article covers companies and contacts and doesn't mention deals.
- 5
Accounting and payments
QuickBooks Online, QuickBooks Desktop and Xero integrations, Stripe, Clover Connect and ProPay payment integrations, plus D-Tools Payments for deposits, which is Cloud-only.
D-Tools · diagnose
Where D-Tools tracking breaks, in the order we check
On D-Tools the click is usually lost before the opportunity even exists, so we start at the hand-off.
- 01
Follow one test inquiry from an ad-tagged URL
Into your form or call tool, then into D-Tools. Note where the click ID disappears.
- 02
Audit the Lead source list
Compare its values with where Won projects really came from over a closed quarter.
- 03
Check that stages are kept current
If opportunities jump from New Lead straight to Won, there is no qualified signal to send.
- 04
Look for duplicate accounts from CRM sync
A HubSpot contact and a hand-typed account can split one client into two opportunities.
- 05
Compare Won values with reported conversion values
Per opportunity, so quote totals and ad platform revenue agree.
D-Tools · prove
The QA evidence — D-Tools
Tested on a real inquiry that travels all the way to a Won opportunity in your D-Tools Cloud account, not on a sandbox record.
Source of truth
D-Tools Cloud opportunities: created date, Lead source, stage history, Won date and accepted quote total
- One inquiry from an ad-tagged URL, its click ID linked to the matching D-Tools opportunity ID.
- A move to your qualified stage received once in Google Ads and once in Meta Events Manager.
- A Won opportunity reported at the accepted quote value, with one shared event ID.
- A Lost opportunity confirmed absent from every conversion.
- Won opportunities reconciled one by one per platform over a closed window, then again 30 days later.
D-Tools · free audit
What we check in the free audit
- Follow one test inquiry from an ad-tagged URL
- Audit the Lead source list
- Check that stages are kept current
- Look for duplicate accounts from CRM sync
- Compare Won values with reported conversion values
Checked against
D-Tools Cloud opportunities: created date, Lead source, stage history, Won date and accepted quote total
Free30 minutesNo obligation
D-Tools · when not to buy
When you don't need this on D-Tools
Plenty of integrators use D-Tools happily without any ad tracking work.
- If your projects come from builders, designers and past clients and you don't buy ads, D-Tools reporting already tells you what you need.
- If you only run Local Services Ads, you pay per lead and track those leads inside your LSA account, and a D-Tools link adds little.
- If you close a handful of large projects a year, there aren't enough conversions for bidding to learn from; a monthly manual review is enough.
- If salespeople don't keep opportunity stages current, fix that habit first, because tracking can only read the pipeline you keep.
D-Tools · what we deliver
The event map on D-Tools
Website inquiry or tracked call
Captured on your site or call tracking with gclid, fbclid and UTMs stored, because D-Tools' docs describe no public web form.
Opportunity created in D-Tools Cloud
Matched to that inquiry by opportunity ID, with Lead source updated from the click where your account's API access allows it.
Site visit completed
Or your own qualified stage name. The first signal worth bidding on, sent when the stage changes.
Proposal accepted, opportunity Won
The primary conversion, valued from the accepted quote you select when marking it Won, with any subscription value split out.
Deposit collected
Optional confirmation, read from D-Tools Payments or your QuickBooks or Xero sync once we confirm where payment data is reachable.
Excluded from acquisition
Lost opportunities, change orders, service contracts for existing clients and recurring monitoring or service payments.
Written guarantee
95%+ tracking accuracy
Measured against D-Tools Cloud opportunities: created date, Lead source, stage history, Won date and accepted quote total. Miss it and we keep working at no cost.
From $400 · See packages
FAQ
D-Tools questions, answered
Not natively. Its help docs list an API, webhooks, Zapier through an API request, CRM and accounting integrations, and that's the route we use to send opportunity stages and Won values to Google and Meta.
Its docs don't describe a public web lead form; opportunities are created in the app, through a CRM sync, or through the API. So the click ID gets captured on your site or call tracking first, then carried into the opportunity.
Yes. We send your qualified stage, such as a completed site visit, as soon as it happens, and the Won opportunity later against the same click. The platform gets an early signal and the real outcome.
D-Tools' own article describes syncing HubSpot companies and contacts and doesn't mention deals. The Salesforce integration does sync opportunity fields, as long as your stages match on both sides.
System Integrator is documented separately from the Cloud API. We check what your SI setup exposes, and whether you also run the SI integration with Cloud, before quoting anything.
More on D-Tools
- 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 D-Tools, and what their bookings feed
- DripJobsDripJobs conversion tracking: stop counting taps, see which ads sign proposals
- Contractor ForemanContractor Foreman knows which estimates got approved. Your ads don't.
- JobNimbusGoogle Ads counts form fills. JobNimbus knows which jobs sold.
- CompanyCamYour ads count inspections. CompanyCam knows which jobs sold.
- KnowifyKnowify conversion tracking: the contract gets signed, the job goes active, and your ads never find out
- Invoice2goClients tap Approve estimate in Invoice2go, and Google Ads is none the wiser
- BuildingConnectedYou win the bid in BuildingConnected. Google Ads never hears about it.
- BuildBookYour BuildBook pipeline shows signed remodels. Google and Meta never find out.
Free · 30 min
Find out which ads are filling your D-Tools pipeline
WhatsAppFree30 minutesNo obligation
