Meta Ads conversion tracking for paving and asphalt contractors
Paving has a hard physical constraint that most trades do not: asphalt cannot be laid below a certain temperature, so the working season is fixed and capacity within it is finite. What Meta Ads adds on top of that is a mechanical requirement: fbclid and _fbc have to reach the record that holds the money, because Meta can only credit a conversion it can tie back to a click it recognizes. This page covers both halves — what a conversion is in paving and asphalt contractors, and what Meta specifically needs to accept it.
Free30 minutesNo obligation
Specific to Meta × Paving and asphalt
Meta for paving: residential driveways only, judged on signed jobs
Track paving on Meta by sending a Schedule event when a site visit is booked and the signed residential job with its contract value, both through the Conversions API from your estimating system. Store fbclid as _fbc on the estimate record and pass hashed email, phone and job address. Commercial lot buyers are rarely reached here.
Meta reaches homeowners, which makes it a residential driveway channel. Property managers and facilities buyers who commission lot work are on Meta too, but not in a buying frame of mind, and you cannot target them there with any precision. Treat Meta as the residential half of the business and keep commercial expectations at zero unless your own reconciliation says otherwise.
The site visit is the right optimization event for this trade. It costs a truck and an hour, it happens within days of the click so it fits inside Meta's default 7-day click window, and sending it as Schedule tells Meta to find people who will let an estimator come out rather than people who fill in forms. Send the signed job later with its contract value, and check how many days late Meta accepts the event, because estimate-to-signature for homeowners collecting three quotes can run past a week.
Where it breaks on paving: the estimator writes the job up on a tablet or in an estimating tool that never sees the website session, so the signed-job event goes out with a name and phone number but no _fbc. Write fbclid into the lead record at first contact and carry it onto the estimate, or match quality on the event you care most about will be the lowest in the account.
Meta · Paving and asphalt · what breaks
Why Meta under-reports for paving and asphalt contractors
- 01
Commercial and residential pooled
One lot job can be worth fifty driveways and counts as one conversion.
- 02
A fixed weather window capping capacity
Once the season is booked, further leads have nowhere to go.
- 03
Quote-heavy sales with real site-visit costs
Every estimate is a truck, a person and an hour.
- 04
Fbclid and _fbc never reaches the record
fbclid arrives on the landing URL and is normally written into the _fbc cookie. If it isn't captured on landing, _fbc never exists — and _fbc is the strongest click signal Meta has, so its absence caps your match quality regardless of what else you send. Forward _fbp too, from the browser rather than regenerating it server-side.
Meta · Paving and asphalt · the fix
What working looks like — Meta · Paving and asphalt
Signed jobs as the conversion
At contract value, tagged commercial or residential.
Job type carried on the conversion
So bidding does not optimize toward the cheap half.
Capacity stated in the report
So spend stops when the season fills.
Meta · Paving and asphalt · architecture
How Meta and paving and asphalt contractors actually connect
- 1
The conversion in paving and asphalt contractors
The money event is a signed job at contract value. An issued estimate is a cost you have already paid, not revenue you have earned.
- 2
Meta Ads needs a click to match
event_name from the standard set with exact casing, event_time in seconds, a shared event_id, an action_source, and hashed user_data that was normalized before hashing. Purchase additionally requires value and currency.
- 3
The identifier: fbclid and _fbc
fbclid arrives on the landing URL and is normally written into the _fbc cookie. If it isn't captured on landing, _fbc never exists — and _fbc is the strongest click signal Meta has, so its absence caps your match quality regardless of what else you send. Forward _fbp too, from the browser rather than regenerating it server-side.
- 4
Where it gets sent from
The estimating system — signed jobs by date, at contract value, tagged commercial or residential.
- 5
Deduplication and window
This is the mechanism that decides whether adding CAPI helps or doubles your conversions. Both the Pixel and the server event must carry the same event_id — the order or booking reference works best, because both sides can produce it without coordinating. A case difference in the event name alone produces two events even with a matching ID. Read the Deduplicated indicator in Events Manager over a full week, not one session. Meta's default attribution is a 7-day click and 1-day view. View-through is included by default, which is a large part of why Meta claims more conversions than your other platforms — that overlap is expected rather than a fault.
Meta · Paving and asphalt · events
The conversion map for paving and asphalt contractors
Five events across a season with a hard end date.
| Event | What it means here |
|---|---|
| Enquiry | Residential arrives steadily; commercial arrives in procurement cycles. |
| Site visit and measurement | A real cost, incurred before any commitment. |
| Estimate issued | Frequently one of three the buyer is collecting. |
| Job signed | The money event, at contract value. |
| Job completed and invoiced | Where deferrals and weather changes finally settle. |
Meta · Paving and asphalt · diagnose
Diagnostic order — Meta · Paving and asphalt
- 01
Count records carrying fbclid and _fbc
- 02
A tenfold value gap between job types
Pooling them makes cost per job meaningless and biases bidding toward driveways.
- 03
Season capacity reached mid-summer
Leads after that point cost money and produce next-year work at best.
- 04
Three-quote buyers
A high estimate count with a low signature rate is normal and needs saying, not fixing.
- 05
Read the Deduplicated indicator and the per-event match quality score, both read over seven days
Match quality is where most Meta accounts lose attribution, and it's almost always normalization rather than coverage. An email hashed with a capital letter, or a phone hashed with brackets, produces a perfectly valid hash that matches nobody and errors nowhere. Normalize first, then hash, and read the score per event rather than overall.
Meta · Paving and asphalt · prove
How it gets proven — Meta · Paving and asphalt
Source of truth
The estimating system — signed jobs by date, at contract value, tagged commercial or residential
- Signed jobs reconciled per record against what each platform reports.
- Job type present on every conversion.
- Deferred jobs excluded from the season they were sold in.
- Estimate volume reported as a cost, not only as a lead count.
- The Deduplicated indicator and the per-event match quality score, both read over seven days read directly, not inferred from an upload succeeding.
Meta · Paving and asphalt · free audit
What we check in the free audit
- Count records carrying fbclid and _fbc
- A tenfold value gap between job types
- Season capacity reached mid-summer
- Three-quote buyers
- Read the Deduplicated indicator and the per-event match quality score, both read over seven days
Checked against
The estimating system — signed jobs by date, at contract value, tagged commercial or residential
Free30 minutesNo obligation
Meta · Paving and asphalt · when not to buy
When you don't need this — Meta · Paving and asphalt
- If Meta already reports conversions that reconcile against the estimating system within a few percent, this is working and there is nothing to buy.
- Measure identifier coverage yourself first — pull your last hundred records and count how many carry fbclid and _fbc.
- If you're advertising a business type Meta restricts data collection for — health being the obvious one — the parameters you can legitimately send are narrower, and that constraint should shape the build rather than be worked around.
Meta · Paving and asphalt · what we deliver
What gets built — Meta · Paving and asphalt
Click identifier captured and persisted
Through a quote cycle that runs weeks for commercial work.
Carried into the estimating system
Onto the customer record.
Signed job fires the conversion
At contract value, with the job type attached.
Cancelled and weather-deferred jobs handled
A job pushed to next season is not this season's revenue.
Dispatch via the Conversions API
Server events go through CAPI with an action_source describing where the conversion happened. Offline outcomes flow through the same API rather than a separate product. Verify current field names against Meta's documentation before building — this surface changes.
Written guarantee
95%+ tracking accuracy
Measured against The estimating system — signed jobs by date, at contract value, tagged commercial or residential. Miss it and we keep working at no cost.
From $400 · See packages
FAQ
Meta · Paving and asphalt questions, answered
A booked site visit, sent as Schedule, because it happens quickly enough to be attributed and it costs you real time. Send signed jobs with their value as well, for reporting.
Rarely, and not predictably. Use Meta for residential driveways and reach commercial buyers through search and professional channels.
No. The value gap is roughly tenfold and the buying processes have nothing in common — one is a homeowner collecting three quotes, the other is a procurement cycle. Shared bidding will chase the cheaper conversion every time.
Only deliberately, to build next season's pipeline, and the report should label it that way. Otherwise you are paying for leads you will disappoint.
Probably not. Homeowners collect three quotes as standard, so a third is a reasonable ceiling. What matters is whether the rate differs by campaign, because that difference is real signal.
fbclid arrives on the landing URL and is normally written into the _fbc cookie. If it isn't captured on landing, _fbc never exists — and _fbc is the strongest click signal Meta has, so its absence caps your match quality regardless of what else you send. Forward _fbp too, from the browser rather than regenerating it server-side.
Server events go through CAPI with an action_source describing where the conversion happened. Offline outcomes flow through the same API rather than a separate product. Verify current field names against Meta's documentation before building — this surface changes.
By reading the Deduplicated indicator and the per-event match quality score, both read over seven days and reconciling against The estimating system — signed jobs by date, at contract value, tagged commercial or residential. An upload that succeeds is not an upload that matched.
More on Meta · Paving and asphalt
- Paving and asphaltConversion tracking for paving contractors, measured in signed jobs
- Google Ads · Paving and asphaltGoogle Ads conversion tracking for paving and asphalt contractors
- TikTok · Paving and asphaltTikTok Ads conversion tracking for paving and asphalt contractors
RELATED GUIDES
More for paving and asphalt: other angles on the same outcome
- Paving and asphaltConversion tracking for paving contractors, measured in signed jobs
- Meta · Self-storageMeta Ads conversion tracking for self-storage facilities
- Meta · Pressure washingMeta Ads conversion tracking for pressure washing companies
- Meta · Quote → closed jobHow to track quote request to closed job for Meta Ads
- Meta × Job SystemHow to reconcile Meta Ads against your job management system
- Meta · Air duct cleaningMeta Ads conversion tracking for air duct cleaning companies
- Meta · Drywall contractorsMeta Ads conversion tracking for drywall contractors
- Meta · Home securityMeta Ads conversion tracking for home security companies
Free · 30 min
Get Meta reporting what paving and asphalt contractors actually earn
WhatsAppFree30 minutesNo obligation
