How Do You Set Up the Meta Conversions API for a Service Business?

The Meta Conversions API sends events such as leads, booked calls and sales to Meta from your server or CRM, instead of relying only on the browser. For most service businesses, the easiest setup is a built-in integration in your website platform or CRM, or Meta's Conversions API Gateway, which needs no coding. Then add the step that matters most: sending booked and won clients back from your CRM so Meta learns which leads turn into clients.

What is the Conversions API, in plain English?

The Meta Pixel is a piece of code on your website that reports what visitors do, such as submitting a form. It runs in the visitor's browser, so some events never reach Meta.

Meta describes the Conversions API as a connection between an advertiser's marketing data, such as website events and offline conversions, from a server, website platform or CRM, to the Meta systems that optimise ad targeting and measure outcomes. In other words, it is a second, more reliable pipe for the same information, plus a way to send things that never happen on your website at all, such as a signed proposal.

Meta's best practices recommend using the Conversions API alongside the Pixel and sharing the same events through both.

Why does it matter for a service business?

Because your real result happens offline. A clinic's result is a booked and attended appointment. A firm's result is a signed engagement. A tradie's result is an accepted quote. The Pixel cannot see any of those.

If Meta only hears "form submitted", it optimises for people who submit forms. Sending later stages from your CRM gives it a better picture of who your clients are. It also lets you see cost per client by ad, which we explain in what a good cost per lead is in Australia.

What are your setup options?

Option	Who it suits	Effort
Built-in integration in your website platform or CRM	Most small service businesses	Low; usually a settings screen and a connection to your Meta account
Conversions API Gateway	Businesses with their own website and no developer	Low to medium; set up in Events Manager
Direct integration built by a developer	Businesses with custom systems	Higher; needs code and ongoing maintenance
Conversions API for CRM (lead stages)	Businesses running Meta instant form lead ads at volume	Medium; usually via a CRM partner or developer

Meta describes the Conversions API Gateway as a self-serve configuration option in Events Manager that works without dedicated developer resources, so no coding is necessary. Meta's getting started guide focuses on direct integrations and notes that you need a Pixel ID and an access token.

How do you set it up, step by step?

Decide which events matter. For most service businesses: Lead (form submitted), Schedule (call or appointment booked), and a final event for a won client, such as Purchase with the value of the sale.
Check the Pixel is working. In Events Manager, confirm the Lead event fires once per form submission.
Choose your connection method. Look first in your website platform and CRM settings for a Meta Conversions API integration. If there is none, consider the Conversions API Gateway.
Connect and send the same events. Send Lead through both the Pixel and the Conversions API.
Set up deduplication. Meta's deduplication guide says it treats events as identical based on their ID and name: the Pixel's eventID must match the Conversions API's event_id, and the event names must match. Most built-in integrations handle this for you, but check.
Send customer details correctly. Meta's customer information parameters page says hashing is required for email and phone. Good integrations do this automatically. Send only what you need.
Add CRM events. When a lead books, attends or becomes a client, send that event back with the lead's details so Meta can match it.
Test. Submit a test lead, move it through each CRM stage, and confirm each event appears once in Events Manager.

How do you send booked calls and sales from your CRM?

This is the step most setups skip. There are two common paths.

If your leads come from a website form

Send booked and won events from your CRM as Conversions API events, using the same contact details the lead submitted. Many CRMs can do this through a native integration or an automation tool. Meta's offline events documentation says the Conversions API is its recommended integration method for sending offline and physical store events.

If your leads come from Meta instant forms

Meta has a dedicated Conversions API for CRM integration. Meta says it is a separate integration from your website Conversions API setup, because the data comes from your CRM. Key points from that page:

Store the 15 to 17 digit Meta lead ID in your CRM. Meta says this gives the best results, and sending the lead ID with each event is recommended.
The Conversion Leads performance goal is currently only compatible with Facebook and Instagram lead ads using instant forms.
Meta lists fit criteria: at least 200 leads a month, uploading data at least once a day, a target lead stage that happens within 28 days of the lead, and a conversion rate for that stage between 1% and 40%.
Meta estimates time to value at about a month, including a learning phase of 2 to 4 weeks.

If you are below 200 leads a month, you can still send stages back for measurement. Just do not expect the Conversion Leads goal to perform well until volume grows.

Google Ads works the same way

If you also run Google Ads, offline conversion imports do a similar job: save the click ID with the lead, then send the outcome back later. See Google Ads vs Meta ads for service businesses.

What privacy rules apply?

The Conversions API sends personal information to Meta, so Australian privacy law applies. The OAIC's guidance on tracking pixels says organisations should limit collection to the minimum necessary, must generally make sure sensitive information is not disclosed to third-party platforms, and must explain their use of tracking in their privacy policies. The OAIC also notes that health service providers are covered by the Privacy Act regardless of turnover.

For clinics, that means never sending event names, page URLs or custom data that reveal a condition or treatment. Send a neutral event such as "Schedule", not the name of the service. If in doubt, get advice.

What we learned in our own business

Signals shape decisions, including automated ones. We once added an honest 100-seat limit to a live event funnel. When it filled, the form silently refused every new registration for about two days while roughly $450 to $500 of Meta ads kept sending clicks. Our automated ad tool saw zero leads and paused a new campaign as a "bad ad". The ads were not the problem; the signal was. Any tool that acts on your tracking data is only as good as the events you send it, so we check the funnel before judging the ads, and treat a sudden drop to zero leads while page views continue as something broken.

We also had one set of ads that produced leads at $9.63 each and $0 in sales. With only a Lead event, that looks acceptable. With booked and won events flowing back, it is obviously a loser. That is the case for sending CRM outcomes, not just form fills.

See what slow replies cost your business.

The free Lead Leak Calculator turns your own numbers into a monthly figure in about 60 seconds.

Try the calculator

Setup checklist

Pixel fires one Lead event per form submission.
Conversions API sends the same Lead event, with matching event ID and name.
Events Manager shows the events as deduplicated, not doubled.
Email and phone are hashed before sending (check your integration does this).
CRM sends booked, attended and won events back with the lead's details or Meta lead ID.
Every lead in the CRM also has the ad it came from. See how to track which ads bring clients.
Privacy policy explains your use of tracking, and no sensitive information is sent.
A test lead has been pushed through every stage and checked.

Frequently asked questions

Do I need the Conversions API if I already have the Meta Pixel?

Meta recommends using both and sending the same events through each, with deduplication. The Conversions API also lets you send events that never happen on your website, such as a booked call or a signed client.

Can I set up the Conversions API without a developer?

Often, yes. Many website platforms and CRMs have built-in integrations, and Meta says its Conversions API Gateway works without dedicated developer resources, so no coding is necessary.

What is deduplication in the Conversions API?

It stops Meta counting the same event twice when it arrives from both the Pixel and the server. Meta matches events on their ID and name, so both must be the same.

How do I send offline conversions to Meta?

Send them as Conversions API events from your CRM or server. Meta says the Conversions API is its recommended method for offline events. For instant form leads, use the Conversions API for CRM integration and store the Meta lead ID.

How many leads do I need for Meta's Conversion Leads goal?

Meta lists at least 200 leads a month as one of its fit criteria, along with daily uploads and a target lead stage that happens within 28 days of the lead.

Is it legal to send customer data to Meta in Australia?

It can be, if you follow the Privacy Act where it applies. The OAIC says to collect only what you need, explain tracking in your privacy policy, and generally not disclose sensitive information such as health information to third-party platforms.

Next step

The free scorecard shows whether your tracking connects ads to clients. To build tracking, CRM and follow-up as one system with our team beside you, see The AI Marketing Team Accelerator.