Meta Pixel and Conversions API Setup Checklist for Service Businesses

If your CRM has one estimate request and Meta reports two leads from the same test, the first job is to find out what fired. The Meta Pixel sends events from a visitor’s browser. The Conversions API can send events from your server or an integration. Both can describe the same action, so they need a shared definition of success.

Decide exactly when a visitor becomes a lead

For an estimate form, use the moment a valid submission is accepted. A click on “Request an estimate” shows intent. Someone can click, leave a required field empty and walk away. Counting that click as a lead would teach your team to celebrate a request the estimator never received.

Write a short event map before installation. For each action, name the event, the system that confirms success and the record a staff member can check. A form acceptance can map to Lead. A confirmed booking can map to Schedule. If your calendar sits on a separate domain, test the handoff before promising appointment reporting.

Connect the browser and server paths

• Confirm which business controls the Meta dataset, website, form and booking integration. Check for an existing Pixel in a website plugin or tag manager before adding another.

• Choose a supported integration that can observe the actual success event. A server integration needs a reliable way to know the form was accepted.

• Send the corresponding browser and server events to the same dataset. Document who can change each integration and where the test results appear.

• Review the data you intend to share, why you need it and what people are told. Keep free-text form responses and sensitive information out of marketing event payloads. Apply the appropriate consent choices to both paths. Canadian guidance on meaningful consent

Meta distinguishes retrieving a lead into a CRM from sending conversion information back to Meta. A working CRM notification confirms delivery to your team. It does not establish that a server event reached the right dataset. Meta’s integration guide (PDF)

How do you stop one submission from counting twice?

Give both copies of the same action the same event name and unique identifier. For example, the browser can send Lead with eventID “estimate-1842” and the server can send Lead with event_id “estimate-1842”. Generate a new identifier for the next genuine submission. Preserve the original identifier if the server retries the first delivery. Meta’s SDK documents the role of both event name and event ID in deduplication. Meta Business SDK event reference

Keep the identifier independent of personal details. A customer’s email makes a poor event identifier because the same person can make another legitimate request. Also check which layer owns the identifier. Independently generating a random value in the browser and another on the server gives the platform two different IDs.

Run these acceptance tests before judging results

• Invalid form. Leave a required field empty and submit. Expect no CRM lead and no Lead event.

• Valid form. Submit one labelled test request. Find its record in the CRM. In Events Manager’s test view, inspect the event name, delivery sources and matching identifier where both are enabled.

• Refresh and retry. Reload the confirmation page and test the integration’s retry behaviour. A reload should not record another inquiry.

• Second request. Submit a second valid inquiry. Verify it receives a distinct identifier and remains distinguishable from the first.

• Consent choice. Exercise the choices offered on the site and confirm each integration behaves as described to visitors.

Event matching helps the platform associate an event with an account. Deduplication addresses duplicate reports of the same event. Neither tells you whether the homeowner booked a visit. Reconcile CRM records first, then review attributed results over comparable time windows. Attribution and raw submission counts answer different questions.

Review your lead tracking with Torred if you can see conversion totals but cannot trace a single estimate request through the setup.

Sources

• Canadian guidance on meaningful consent

• Meta’s integration guide (PDF)

• Meta Business SDK event reference