Our contracts live in Sage. Google Ads has no idea which ads won them.
Commercial HVAC, electrical, roofing and tenant build-out firms run jobs and progress billing in Sage 100 Contractor, Sage 300 CRE or Sage Intacct Construction. The inquiry arrives by web form or phone and gets retyped into Sage weeks later, and Sage's construction docs show no Google Ads or Meta connection, so the click that started a job never reaches the contract. Fixed means the click ID rides into the Sage record, and Google and Meta hear about awarded work at contract value, once.
Free30 minutesNo obligation
Sage construction · what breaks
What goes wrong when the money lives in Sage
- 01
Google Ads counts form fills, not awarded contracts
A homeowner asking about a furnace and a property manager with a big build-out look identical to Smart Bidding, so budget drifts toward whoever fills in forms, not toward bids you win.
- 02
The lead gets retyped into Sage and the source vanishes
The office copies the contact from email or the CRM into 3-6 Receivable Clients, a 300 CRE job or an Intacct project. The click ID stays behind, so the contract never ties back to a campaign.
- 03
Our bids take months, the conversion window doesn't
Google caps the conversion window at 90 days. A contract signed five months after the click is invisible to bidding unless an earlier stage, like a bid submitted, was reported in time.
- 04
Every pay app looks like a new sale
Progress billing turns one job into a long run of monthly pay apps and cash receipts. If those reach the ad platforms, one tenant build-out counts many times and return on ad spend looks inflated.
Sage construction · the fix
What changes after the fix — Sage construction
Bidding learns from bids you win
Qualified leads, submitted proposals and awarded contracts reach Google Ads in order, so campaigns stop rewarding residential calls.
One award, one value
The contract counts once at its original value from Sage. Pay apps, retainage and change orders stay in your books.
A clear answer on which campaigns fill the backlog
Each awarded job in Sage carries its campaign, so you compare search, Meta and referrals on signed work, not lead counts.
Sage construction · architecture
What each Sage edition actually lets you hook into
Sage sells three construction systems with three data routes. These are the documented ones; anything else gets confirmed on your install.
- 1
Sage 100 Contractor: Receivable Clients, SQL Server, API
3-6 Receivable Clients tracks referrals, appointments and call-backs with custom lead-source lists. Data sits in SQL Server, Sage documents an API that needs a security group named API, and grids export to Excel.
- 2
Sage 300 CRE: Web API, SQL Replicator, ODBC
Its Web API runs on the accounting server and returns JSON, but the published endpoints cover jobs, job cost, contacts, field reports and payroll, under a developer partner license. SQL Replicator copies 300 CRE data into SQL Server; ODBC is documented.
- 3
Sage Intacct Construction: REST API and triggers
Intacct recommends its REST API over the legacy XML API. Project contracts carry customer, project, contract date and custom fields, AR payments are queryable, and Platform triggers can send HTTP requests to an outside app.
- 4
No ad platform connection
No native Google Ads, GA4 or Meta link appears in Sage's construction docs, so every route runs through an export, a database read or the API.
- 5
Where the click ID lives
A Custom Fields entry on the 300 CRE job record or a custom field on the Intacct project contract. On 100 Contractor, lead-source lists are pick lists, so we confirm which 3-6 client field can hold a unique ID on your version.
Sage construction · diagnose
Where Sage contract tracking breaks, in the order we check
The fault is rarely inside Sage. It's in the handoff from inquiry to the record accounting creates.
- 01
Is the click ID stored when the inquiry arrives?
A test form and tracked call from an ad-tagged URL, then a look for the GCLID in your CRM or inbox.
- 02
Does it survive into Sage?
We open the record for a recent award and look for any source field.
- 03
How long is click to award?
Last year's contracts against Google's 90-day maximum, which decides which stages report early.
- 04
Which value is being sent?
Original contract amount, revised amount or invoice totals. Only one belongs on the conversion.
- 05
Is repeat and service work separated?
Repeat GC bids and maintenance work orders checked for leaks into new-customer counts.
Sage construction · prove
The QA evidence — Sage construction
Checked against contracts your team actually entered in Sage.
Source of truth
Sage job, project and contract records: awarded contracts by date with original contract value, client and the stored lead source or click ID
- A test inquiry from an ad-tagged URL, with the click ID confirmed in the CRM and on the Sage record.
- Each award sent once, at original value, with its Sage job or contract number as the order ID.
- Each Meta lead counted once, with Pixel and Conversions API sharing an event ID and event name.
- Progress invoices and cash receipts absent from every ad platform.
- Awards reconciled job by job against Google Ads and Meta over a closed period, then 30 days later.
Sage construction · free audit
What we check in the free audit
- Is the click ID stored when the inquiry arrives?
- Does it survive into Sage?
- How long is click to award?
- Which value is being sent?
- Is repeat and service work separated?
Checked against
Sage job, project and contract records: awarded contracts by date with original contract value, client and the stored lead source or click ID
Free30 minutesNo obligation
Sage construction · when not to buy
When you don't need this — Sage construction
Plenty of Sage shops have nothing worth attributing yet.
- If your work comes from GC invitations, bid boards and relationships and you don't run ads, there's nothing to send back.
- If ads win you a handful of jobs a year, a monthly spreadsheet matching awards to inquiries is enough.
- If your CRM already stores the click ID and uploads stages to Google Ads, Sage only needs to confirm contract value.
- If nearly all revenue is repeat GCs and existing maintenance agreements, retention reporting matters more.
Sage construction · what we deliver
The event map from first click to Sage contract
Inquiry captured with its click ID
Website form or tracked call, with GCLID, UTM tags and a hashed email stored before anyone touches Sage.
Qualified commercial lead
Marked by your estimator once scope and project type fit. Homeowner and vendor inquiries excluded.
Bid or proposal submitted
From your CRM or proposal record, sent while the click is still inside the conversion window.
Contract awarded
The main conversion, valued from the original contract amount on the Sage job or project contract.
Service agreement signed
For service departments: the maintenance contract, not each on-call work order.
Excluded on purpose
Progress invoices, receipts, retainage, change orders and repeat GC work stay out of acquisition reporting.
Written guarantee
95%+ tracking accuracy
Measured against Sage job, project and contract records: awarded contracts by date with original contract value, client and the stored lead source or click ID. Miss it and we keep working at no cost.
From $400 · See packages
FAQ
Sage construction questions, answered
Not natively, going by Sage's documentation. Awarded contracts reach Google Ads through offline conversion import, fed by an export, a SQL read or your edition's API.
Partly, because Google's longest conversion window is 90 days. We report qualified leads and submitted bids inside it and send contract value whenever the award lands in time.
All three: Sage 100 Contractor usually via its SQL Server database or API, Sage 300 CRE via SQL Replicator or ODBC, and Sage Intacct Construction via its REST API.
No. The award is sent once at original contract value. Pay apps, retainage and change orders stay in Sage.
No. The feed reads client, job or contract number, award date, contract value and the source field.
Yes. Qualified leads and awards go to Meta through the Conversions API with a shared event ID, so a lead that also fired the Pixel counts once.
More on Sage construction
- ConstructionConversion tracking for construction, measured in signed contracts
- Dodge Construction NetworkYour ads are taking credit for jobs Dodge found
- Google Ads · ConstructionGoogle Ads conversion tracking for construction and general contracting companie…
RELATED GUIDES
Booking tools beside Sage construction, and what their bookings feed
- STACKSTACK conversion tracking: show Google and Meta which ad leads you actually bid and won
- D-ToolsD-Tools conversion tracking: know which ads turn into signed proposals
- Contractor ForemanContractor Foreman knows which estimates got approved. Your ads don't.
- Foundation SoftwareThe job gets set up in FOUNDATION. Your ad account never learns it was won.
- Invoice2goClients tap Approve estimate in Invoice2go, and Google Ads is none the wiser
- Estimate RocketEstimate Rocket conversion tracking: your ads see the form fill, never the signed proposal
- ProcoreA GC found us on Procore. We also ran Google Ads. Which one won the job?
- HoverHomeowners design their new siding in Hover. Your ads never hear about it.
Free · 30 min
Find out which ads actually won your Sage contracts
Free30 minutesNo obligation
