Facebook Conversions API: Setup and Pixel Guide for Australian Businesses
Facebook Conversions API: Setup and Pixel Guide for Australian Businesses

The Conversions API (CAPI) sends your conversion events from your own server to Meta, instead of relying only on the visitor’s browser. For most Australian advertisers the right setup is both: keep the Meta Pixel running, add the Conversions API alongside it, and make sure every event is deduplicated so each sale or lead is counted once.
I’m Jesse, a senior paid media specialist at Senior Ad Managers. Below is how it works, how to choose a setup method, where it goes wrong, and what Australian privacy rules mean for the data you send.
TL;DR
- The Meta Pixel records events in the browser. The Conversions API sends them from your server. Meta recommends running both for the same events.
- Deduplication depends on matching event names and event IDs. If they don’t match, Meta can count one purchase twice.
- Meta’s one-click option works for many sites that already have a Pixel, with no code and no setup fees. Custom builds suit sites with unusual checkouts or CRM-based events.
- Sending CRM outcomes such as booked jobs or closed sales gives Meta a better signal than a form fill alone.
- Australian businesses should check what they send against the OAIC’s guidance on tracking pixels, especially in health and other sensitive sectors.
Table of Contents
- What the Conversions API does
- Conversions API vs Pixel: which one do you need?
- Setup methods and how to choose
- Deduplication: the step that decides whether your numbers are right
- Send what happens after the lead
- Why Meta’s numbers and your sales still differ
- Australian privacy and consent
- Our perspective
- What a good setup looks like on Meta
- How we can help
- FAQ
- Sources
What the Conversions API does
Meta describes the Conversions API as a way to send multiple event types, from web, app and offline sources, through one integration. In a direct integration, that means a connection between your server and Meta’s Conversions API endpoint.
The Pixel works differently. It is a snippet of code that runs in the visitor’s browser and reports what that browser does. If the browser blocks the script, the visitor declines cookies, or the page closes before the event fires, Meta never hears about the conversion. A server does not have those problems, because your website or CRM already knows when an order was placed or a form was submitted.
That matters because Meta’s delivery system learns from the events you send. Fewer events reach it, and it has less to learn from. Campaigns optimise on a thinner picture of who actually buys.
Conversions API vs Pixel: which one do you need?
You need both for most accounts. The two are not rivals. Each one covers gaps in the other, and Meta’s own guidance describes a redundant setup that uses the Pixel and the Conversions API to send the same events, with deduplication stopping the double count.
| Meta Pixel | Conversions API | |
|---|---|---|
| Where it runs | Visitor’s browser | Your server, CRM or platform |
| Affected by browser blockers | Yes | No, the event leaves from your server |
| Good for | Page views, add to cart, on-site behaviour | Purchases, leads, booked jobs, offline outcomes |
| Setup effort | Low | Low to high, depending on method |
| Deduplication needed when used together | Yes | Yes |
A Pixel-only account is not broken. It just sees less than your website does. A CAPI-only account loses the browser signals that help Meta match an event to an ad click, such as the browser identifiers the Pixel collects. Running both gives the widest coverage.
Setup methods and how to choose
There are three practical routes. The right one depends on your website platform, who maintains it, and what you want to send.
One-click setup from Events Manager
If your site already has a Meta Pixel, Meta says you can set up the Conversions API for website events in one click from Events Manager, with no code, configuration or setup fees. For a typical local service business or a small online shop, this is where we would start.
The limit is scope. A one-click setup mirrors your website events. It will not know that a lead became a paying customer three weeks later in your CRM.
Platform and partner integrations
Shopify, WooCommerce, and many CRMs and booking tools offer a built-in Meta connection. These are quick, and the platform usually handles event IDs and customer data hashing for you. Check the event list after you connect. Confirm that Purchase or Lead fires once per real action, not once per page reload of a thank-you page.
Direct or server-side GTM builds
A direct integration or a server-side Google Tag Manager container gives you the most control. You decide exactly which events go to Meta, what data goes with them, and when. It also costs developer time and a server to host it. This route makes sense when your checkout is custom, when you run several ad platforms from the same data, or when you want to send CRM stages.
What does it cost? Meta does not charge for sending events. The cost sits in the method: nothing extra for one-click, a plan or app fee for some partner tools, and hosting plus developer hours for a custom server-side build. Get a quote for those before you commit.
Deduplication: the step that decides whether your numbers are right
When the Pixel and the Conversions API both report the same purchase, Meta needs to know they are one purchase. Meta’s documentation says the recommended approach is to pass the same event name and the same event ID from both the browser and the server.
In practice that means:
- Generate one ID per action, such as the order number for a purchase.
- Send that ID with the Pixel event.
- Send the same ID, with the identical event name, with the server event.
- Open the Test Events tool in Events Manager, run a test purchase, and confirm that the event shows as received from both sources and deduplicated.
The common failures are easy to spot once you know them. The event ID is missing on one side. The event name is spelled differently, for example “Purchase” in the browser and “purchase” on the server. Or the ID is regenerated each time the page loads, so the same order gets two IDs.
If your Meta results suddenly show far more purchases than your shop or CRM, deduplication is the first thing to check. The reverse can also happen. If you turned on a server integration and switched off the Pixel without thinking, reported numbers can drop. Neither number is yet a verdict on performance. Compare Meta’s count against your orders or CRM records for the same week.
Send what happens after the lead
The most valuable use of the Conversions API for many businesses is not the website purchase. It is the outcome that happens later. Meta’s documentation covers sending web, app and offline events, so a sale closed by phone or in a showroom can be reported back against the ad that started it.

Take a plumbing business that gets 60 form fills in a month. Perhaps 20 become booked jobs and 12 are paid. Meta, left to itself, optimises toward whoever fills in forms. If you send “booked” or “paid” back through the API, it can start looking for people who resemble the ones who paid. Whether that improves your results depends on volume and data quality, and we never promise a specific outcome. But it gives the system the right target.
A few practical rules for sending CRM events:
- Send them promptly. A stage change reported weeks later is harder for Meta to connect to the original ad.
- Keep event names consistent with the ones you use in campaigns.
- Only send stages with enough volume. If three jobs a month reach “paid”, a higher stage such as “booked” is a better optimisation event.
- Keep the click identifier from the ad visit stored in your CRM record, so the event can be matched back.
This is also the point where a post-click experience matters. If you want to see how the sale itself is structured after the click, the thinking in this guide to selling on social media is a useful companion to the tracking work, because a clean checkout gives you cleaner events to send.
Why Meta’s numbers and your sales still differ
Setting up the Conversions API narrows the gap between Meta’s reports and your own records. It does not remove it. Several things continue to cause differences.
- Attribution windows. Meta credits a conversion to an ad based on a set window after a click or view. Your bank account does not use windows.
- View-through conversions. Meta can count someone who saw an ad and bought later without clicking. Your analytics may count that sale as direct.
- Duplicate or test events. Leftover test purchases and double-firing thank-you pages inflate counts.
- Lead quality. A form fill is not a customer. Reported cost per lead can look strong while cost per paying customer is much higher.
- Different time stamps. An order placed on the 31st and paid on the 2nd lands in different months in different systems.
We find the cleanest check is simple. Pick one month, count customers in your CRM or shop who came from Meta, divide the spend by that count, and compare it with the cost per result in Ads Manager. The difference is the number to understand before you scale the budget.
Australian privacy and consent
Sending customer data from your server to Meta is still a collection and disclosure of personal information, and the Privacy Act applies. The OAIC’s guidance says the Privacy Act does not prohibit tracking pixels, but organisations should do due diligence to make sure their use complies with the Act and the Australian Privacy Principles.
The same OAIC page points to several principles that apply in practice:
- Collect only what you need (APP 3).
- Have a clear privacy policy (APP 1) and tell people at the point of collection (APP 5).
- Give people a simple way to opt out of targeted advertising (APP 7).
- Take reasonable steps when disclosing information overseas (APP 8), which is relevant because Meta processes data outside Australia.
The point that catches businesses out is sensitive information. If your site is a clinic, a telehealth service, a legal practice or anything where a page visit reveals health or similar details, a generic cookie banner may not be enough. Commentary from law firm Clayton Utz on a June 2026 Privacy Commissioner determination involving Medmate and Monash IVF says the Commissioner found information was collected through tracking pixels even though it was not held in the organisations’ own records. If you operate in health, speak to a privacy lawyer before you send event data to Meta, and review which events and parameters you send.
For everyone else, a sensible baseline is to list what each event sends, remove fields you do not need, and put your tracking and data sharing in plain language in your privacy policy.
Our perspective
Most of the Meta accounts we open have the same problem. The Pixel is installed, Meta says leads are coming in, and the owner can’t match that to jobs or sales. Adding the Conversions API is a sound move, but it is not the finish line.
We set tracking up first because every other decision depends on it. If Meta is told that a form fill is a customer, it will find more form fills. If it is told what became a paid job, it has a better target. That is why we check deduplication, event naming and CRM matching before we touch creative or budgets.
We also keep the setup proportionate. A small Australian business with a standard website rarely needs a custom server build. Start with the one-click or platform route, verify it in Test Events, and add CRM events once the basics hold. Our Meta management is run by senior specialists, not juniors learning on your budget, and we compare results with the sales in your CRM rather than only the numbers Ads Manager reports.
Jesse Lees
What a good setup looks like on Meta
Here is the checklist we use when we review an account:
- The Pixel and Conversions API both send the key events, such as Purchase or Lead.
- Event names and event IDs match, and Events Manager shows the events as deduplicated.
- Customer details such as email and phone are hashed before sending, which most platform integrations do for you.
- Each key event fires once per action, not on every refresh.
- Campaigns optimise for the event that best reflects value, not the cheapest one to get.
- Monthly, someone compares Meta’s count with the CRM or shop.
If you also run Google Ads, the same thinking applies there. Account for what each platform counts, and use the CRM as the referee.
Budget matters too. The data a Conversions API sends is only useful if there are enough events to learn from. A very small account with a handful of purchases a month will gain more from tightening the offer, landing page and audience than from an elaborate server build.
How we can help
If your Meta reports don’t match your sales, the fix usually starts with tracking and then with what you ask Meta to optimise for. Our Meta Ads management covers prospecting and retargeting campaigns, from $1,725 AUD a month per platform, with no setup fee, no percentage of ad spend and a 3 month minimum. If tracking is the main issue, our website tracking service covers setup and reconciliation. It has no published price, so ask us for a quote.
To see where your own account stands before you commit to anything, start with our $99 AUD Google Ads audit. We review your account, tracking and search terms, and tell you what we would fix first. Book the $99 AUD Google Ads audit.
FAQ
Is the Facebook Conversions API free?
Meta does not charge to send events. Its one-click setup from Events Manager comes with no code, configuration or setup fees. Costs only appear with some partner tools, hosting for a server-side build, or developer time, so ask for a quote before you start.
Do I still need the Meta Pixel if I use the Conversions API?
Yes, in most cases. Meta’s guidance describes using the Pixel and the Conversions API together to send the same events, with deduplication preventing double counts. The browser side still contributes matching signals that a server event may lack.
How do I know if the setup is working?
Open Events Manager, use the Test Events tool and complete a test purchase or form fill. You should see the event arrive from both the browser and the server, and Meta should show it as deduplicated. Then compare a full week of Meta results with your orders or CRM.
Is server-side tracking allowed under Australian privacy law?
The OAIC says the Privacy Act does not prohibit tracking pixels, but you must comply with the Australian Privacy Principles, including notice, minimal collection and an opt-out of targeted ads. Health and other sensitive sectors should take legal advice first.
Sources
- Conversions API, Meta for Developers
- Handling Duplicate Pixel and Conversions API Events, Meta for Developers
- Tracking pixels and privacy obligations, OAIC
- OAIC determines the use of tracking pixels, Clayton Utz
- 7 Steps to Sell on Social Media and Own the Post Click Experience
Keep reading
How we can help
Next step
Find out where your ad spend is going.
Get a $99 AUD Google Ads audit. We'll show you where money is being wasted and which leads you're missing out on.
Show me my current ad mistakes →