
Facebook ads UTM parameters and GA4
How to tag Facebook and Instagram ads with UTM and dynamic parameters, see them as Paid Social in GA4, and why Ads Manager and analytics never match.
Facebook & Instagram ads · Tracking
The Meta Pixel reports sales and leads from the visitor’s browser, and the Conversions API sends the same events from your server, so fewer go missing. Use both, give each event the same name and ID so Meta counts it once, and test it in Events Manager. We check this on every Meta ads account we take on.
Want it done for you? See Facebook ads Malta: management from €1,249 a month plus ad spend, in an ad account you own, reported in euro every month.
Use both. The Pixel reports from the browser, which blockers and cookie settings can stop. The Conversions API reports from your server, so you still see those sales. Send the same event name and event ID from both, and Meta counts each sale once.
The short answer
Meta does not just report your results. It learns from them. Every purchase, lead or booking your website reports tells Meta what kind of person converts, and it uses that to find more people like them. If half your sales never reach Meta, the campaign learns from half the data. It looks worse than it is and spends your budget less well.
The Meta Pixel and the Conversions API are the two ways your website reports those results. The Pixel runs in the visitor’s browser. The Conversions API, often shortened to CAPI, runs on your server or platform. Meta recommends using both, because each covers gaps in the other.
In Events Manager, the Pixel and the Conversions API now sit together in what Meta calls a dataset: one place that receives events from your website, server, app or CRM. If you see “dataset” where you expected “pixel”, it is the same thing with a broader name.

More than you might think. Eurostat’s 2025 survey found that 41% of people in Malta aged 16 to 74 had changed their browser settings to limit cookies. That is above the EU average of 36.5%. Another 26.6% used software that limits tracking, against 19.9% across the EU. Every one of those visitors can buy from you without the Pixel seeing it.
Here is what that does to your numbers. Say a shop in Sliema spends €1,000 on Meta ads in a month and takes 50 orders worth €3,000 from them. If the Pixel only sees 35 of those orders, worth €2,100, Ads Manager shows a return of 2.1 instead of 3.0. The campaign looks weak, and Meta learns from 35 buyers instead of 50. Add the Conversions API and most of the missing 15 come back.
The opposite mistake is just as costly. Send both without deduplication and the same 50 orders can show as nearly 100. A return of almost 6 looks great, so you raise the budget, while the real figure is still 3.
The Pixel
The Pixel is a small piece of JavaScript on your website. When someone views a page, adds to cart, submits a form or buys, it sends an event to Meta. For a purchase it also sends the value and currency. Meta uses those events to report results, build retargeting audiences and find more people likely to do the same.
The standard events most businesses need are PageView, ViewContent, AddToCart, InitiateCheckout and Purchase for shops, and Lead, Contact, Schedule or CompleteRegistration for service businesses. Use Meta’s standard event names where they fit, because Meta understands them, and add custom events only for things the standard list does not cover.
The Pixel has a weakness: it depends on the browser. Ad blockers, browser privacy features, iOS settings and cookie choices can stop events reaching Meta. Each missed purchase is a sale your campaign cannot learn from.
| Your business | Main event | Fire it when | Send with it |
|---|---|---|---|
| Online shop | Purchase | The order confirmation page loads after payment | Order value, currency (EUR), order number as event ID |
| Clinic, salon or service with a form | Lead | The form is sent successfully, not when the form page opens | A unique ID for that enquiry |
| Restaurant, tour or class with bookings | Schedule | The booking is confirmed | Booking reference as event ID |
| Business that sells by chat or phone | Contact | Someone taps the chat or call button | Later, the real sale from your CRM through the Conversions API |
The Conversions API
The Conversions API sends events from your server, your shop platform or a gateway directly to Meta. It does not depend on the visitor’s browser, so it fills many of the gaps the Pixel leaves. It can also send events that never happen on a website at all, such as a lead from your form that later became a paying customer in your CRM.
Events sent through the Conversions API can include customer details such as an email address or phone number, which Meta hashes and uses to match the event to a person on Facebook or Instagram. The better the match, the more useful the event. Events Manager shows this as Event Match Quality for each event, and it is worth checking.
The Conversions API does not get around consent. If a visitor has not agreed to marketing tracking under your cookie and privacy setup, the server should respect that choice too. Agree with whoever runs your website how consent is passed to both the Pixel and the server.
| Meta Pixel | Conversions API | |
|---|---|---|
| Where it runs | In the visitor’s browser | On your server, platform or a gateway |
| Blocked by | Ad blockers, some browser privacy settings, consent choices | Not by the browser; still subject to consent and Meta’s data rules |
| Setup | A code snippet or platform integration | A platform integration, the Gateway, or a developer |
| Offline and CRM events | No | Yes, for example a lead that became a customer |
| Deduplication | Sends event name and event ID | Sends the same event name and event ID |
Setup
Shopify and WooCommerce: use the official Meta integration for your platform. It installs the Pixel and sends server events through the Conversions API, with deduplication built in. Choose the strongest data-sharing setting your consent setup allows. Our guide to Facebook ads for online shops covers the rest of the shop setup.
WordPress, Wix and other builders: use the official Meta integration or a well-supported plugin where one exists, connect it in Events Manager, and check that the events you need are actually sent. Custom websites: add the Pixel to your pages and send server events through the Conversions API from your backend, or use the Conversions API Gateway, which Meta offers as a simpler hosted option.
Whatever the platform, fire the conversion on the right step: a Purchase on the order confirmation, a Lead when the form is successfully submitted, not when the page loads. And send the value and currency correctly, deciding once whether values include VAT and delivery, so your return on ad spend means what you think it means.
Deduplication
When the Pixel and the Conversions API both report the same purchase, Meta needs to know it is one purchase, not two. That is deduplication. It works when the browser event and the server event carry the same event name, such as Purchase, and the same event ID, usually the order number or a unique ID generated when the action happens.
If deduplication is missing, purchases can be counted twice, your ROAS looks better than it is, and Meta optimises on wrong data. If the IDs never match, Events Manager will show a deduplication warning. Platform integrations handle this for you; custom setups need a developer to pass the same ID to both.
Meta calls this a “redundant setup” and recommends it. Its rule is simple: the Pixel’s eventID must match the Conversions API’s event_id, and the event names must match too. If both arrive at the same dataset within 48 hours, Meta keeps the first one and drops the copy.
The easiest ID to use is one that both sides already know. For a shop that is the order number. For a form it is an ID created the moment the form is sent.
Apply now and send us your website. We’ll check your Pixel, Conversions API and deduplication and tell you what we’d fix first. Free, no obligation.
Proof
This is an online store we ran Facebook and Instagram ads for, from 1 May to 25 July 2025. Meta Ads Manager tracked 3,717 website purchases worth $150,527.84 from $28,130.74 of ad spend, an average purchase ROAS of 5.35.
Numbers like these only mean something when every purchase reaches Meta once, with its value. That is why we check the Pixel, the Conversions API and deduplication before we spend a euro of a client’s budget.

Want every sale counted before you spend more on ads? Apply now for Meta ads management
Health and finance
If your website is about health, wellness or financial services, Meta may restrict what your Pixel and Conversions API can share. Meta calls this Core Setup. In practice it removes custom parameters and most of the page address beyond your domain from events, which can limit how specific your conversion events and audiences can be. Sending events from the server does not avoid it.
You can check whether this applies in Events Manager, in your dataset’s settings, under data restrictions. If it does, keep conversion tracking simple, use standard events on clear thank-you pages, and never put health or financial details in a page address, event or parameter. Clinics in Malta should read our guide to Facebook ads for clinics alongside this.
Check it
Install the free Meta Pixel Helper extension for Chrome and browse your site: it shows which Pixel events fire on each page and flags errors. In Events Manager, open Test Events and watch browser and server events arrive in real time as you go through the site. Then place a real test order or submit a real enquiry and confirm it appears once, with the right value and currency.
After that, check Events Manager every week or two, and always after a website change. A new theme, a checkout update or a cookie banner change can quietly stop events. Look for warnings, falling event counts and Event Match Quality. In Ads Manager, the results column should roughly match the orders or enquiries you actually received.
For your own analytics, the Pixel is not enough. To see Meta traffic in Google Analytics, tag your ads with UTM parameters, as explained in our guide to Facebook ads UTM parameters.
Common mistakes
Purchases counted twice because deduplication is missing. Values sent including VAT and delivery without anyone realising. A Lead event firing when the form page loads instead of when it is sent. Two different Pixels on the same site sending events to two accounts. A cookie banner that blocks the Pixel with no server-side setup. And nobody checking Events Manager after a website update.
The most expensive one is optimising for the wrong event. If your campaign uses the Sales objective but the Pixel only reports page views, Meta has nothing useful to learn from. Our guide to Facebook ads objectives explains how the objective and the tracked event fit together.
A few straight answers
The Pixel sends events from the visitor’s browser; the Conversions API sends them from your server or platform. Meta recommends using both.
It is strongly recommended, because the Pixel alone misses events blocked by browsers, ad blockers and privacy settings.
Sending the same event name and event ID from the Pixel and the server, so Meta counts each purchase or lead once.
Use the Meta Pixel Helper extension and Test Events in Events Manager, then place a real test order or enquiry and check it appears once.
Use the platform’s official Meta integration where one exists, connect it in Events Manager, then check the events with Test Events and the Meta Pixel Helper.
Meta’s name for the place that holds your Pixel and Conversions API events, plus any app or offline events, in one source.
If Meta classifies your site as health, wellness or financial services, it may apply Core Setup, which limits what events can share. Check the data restrictions in Events Manager.
Not if both send the same event name and event ID. Meta keeps the first event and drops the copy when both arrive within 48 hours. Without matching IDs, sales can be counted twice.
In Eurostat’s 2025 survey, 41% of people in Malta aged 16 to 74 had changed browser settings to limit cookies. Another 26.6% used software that limits tracking. That is why the Pixel alone misses sales.
Yes. We check and fix tracking on every account we manage. Meta ads management starts from €1,249 a month plus ad spend.
A useful first step
We set up and check the Pixel and Conversions API, fix deduplication and keep an eye on Events Manager while we run your ads. Meta ads management from €1,249 a month plus ad spend.
Step 1 of 2
A few quick questions, about a minute. We usually reply within 2–3 hours.