Attribution for Home Service Contractors — What Actually Works in 2026.

Meta doesn't charge for it. The cost is setup: many website builders, form tools and CRMs have a built-in Meta integration that sends server events, and Meta's Conversions API Gateway is an option if yours doesn't. Otherwise it's a developer job.

No. Since June 2025 Meta aggregates eligible events automatically. There's no 8-event list to rank and no AEM tab to configure. Domain verification is no longer required for event setup, though it's still worth doing to prove you own your site.

Submit a test lead and check Events Manager: the event should show as received from both the browser and the server, marked as deduplicated. Check the Diagnostics tab for flagged issues and the Event Match Quality score for your Lead event. Then compare Meta-reported leads with what your CRM received from Meta each week. The two won't match exactly, but a sudden jump in the gap means something broke.

Use three layers. Track taps on your tel: link as a Contact event. Use call-tracking software with dynamic number insertion, which shows visitors from Meta a unique number so calls can be traced to the source. Ask every caller how they found you and log the answer in your CRM. The last one catches people who saw your ad days earlier and called without clicking.

It's the most honest measure of what Meta adds, and a simple version costs little. Pick a normal week that isn't peak season or a holiday, pause Meta while every other channel runs as usual, and compare total leads and booked jobs with your recent average. Expect a few days of settling when you switch back on. If you spend enough, Meta's own Conversion Lift studies do a controlled version of the same test.

They answer different questions. Meta counts people who clicked or saw an ad and later converted, including on other devices it can link. GA4 only sees visits to your site, credits whichever channels led to the conversion, and can't see ad views at all. So Meta tends to credit itself more, and GA4 tends to credit Meta less. Use your CRM's lead-source field, backed by 'how did you hear about us?', to settle it.

Use 7-day click to judge campaigns, because it's the least noisy, and glance at Meta's default (7-day click, 1-day engage-through and 1-day view) for context. Emergency trades can check 1-day click too. Whatever you choose, compare like with like week to week.

Make 'How did you hear about us?' a required dropdown on every form, with options such as Facebook/Instagram, Google search, Google Local Services, referral, yard sign and other. Have whoever answers the phone ask the same question and log it. Each week, tally leads and booked jobs by source against spend by source. It's crude, but it's yours and it doesn't depend on any platform's tracking.

Treat it as a sign of more than one touchpoint, not of none. Many people see an ad, check reviews, then search your name or get a referral before calling. Watch the share of 'don't remember' answers over time. If it rises when Meta spend rises and falls when you pause, Meta is doing more than its click-through numbers show.

Combine call tracking with dynamic number insertion, a lead-source question on every call, and sending closed jobs back to Meta through the Conversions API from your CRM. The last step matters most: when Meta can see which leads became paid jobs, it can optimise toward those customers instead of anyone who fills in a form.

A growing number of US states have passed comprehensive privacy laws, browsers keep tightening tracking, and platforms keep adjusting. Expect the gap between what Meta sees and what really happened to widen slowly. The resilient setup is the one on this page: first-party data you collect with consent, sent server-side, checked against your own records.