Facebook Pixel (Meta Pixel) and Conversions API Setup

What the Facebook Pixel and Conversions API do

The Facebook Pixel, now officially called the Meta Pixel, is a small piece of code on your website that tells Meta what visitors do after they click your ad: whether they viewed a product, added it to the cart, filled in a form or bought something. The Conversions API does the same job from your server instead of the visitor’s browser. Together they are how Meta knows which ads actually lead to sales.

That information is used in three places, and all three matter for your results:

• Reporting. The purchases, leads and costs per result you see in Ads Manager come from these events. If the events are wrong, every report is wrong.
• Optimisation. When you run a sales or leads campaign, Meta looks for people similar to those who completed the event. Feed it the wrong event, or a broken one, and it optimises for the wrong people.
• Audiences. Website visitors, cart abandoners and past buyers can only be retargeted or excluded if the Pixel recorded them.

A Pixel setup service makes sure the right events are sent, with the right values, from the right places, once each, and that you can prove it.

Why broken tracking quietly costs you money

Tracking problems rarely announce themselves. Ads keep running and numbers keep appearing, so nobody notices that the numbers are wrong. These are the patterns we see most:

• Purchases counted twice because a theme, a plugin and a manually pasted code all send the same event. Ads look twice as profitable as they are, and budgets are raised on false results.
• Purchases not counted at all because the thank-you page changed, a checkout runs on another domain or an ad blocker stops the browser Pixel. Good campaigns are switched off for “not converting”.
• Wrong values such as every order reported as 1 dollar, or values sent in the wrong currency. Return on ad spend becomes meaningless.
• Events firing on every page load instead of when the action happens, so a lead is recorded each time someone opens the contact page.

Each of these leads to a real decision being made on fake data. That is why we treat tracking as part of the foundation, alongside a secure Facebook account and a properly built ad account, rather than as a technical extra.

Pixel or Conversions API: do you need both?

For most businesses the answer is yes. They complement each other, and Meta recommends using them together.

Meta’s Conversions API documentation explains the technical side in detail. In practice, platforms such as Shopify and WooCommerce offer official integrations that handle most of it, and our job is to choose the right one, configure it and check that it really works.

Which events your business actually needs

More events are not better. A clean setup tracks the few actions that matter for your business, with accurate values. Meta lists all available standard events; these are the ones we use most.

Each event should fire exactly when the action is completed, not when a page loads, and purchase events should always carry the real order value and currency.

How setup differs by platform

The goal is the same everywhere, but the route depends on where your site runs.

Shopify

Shopify’s official Facebook and Instagram sales channel can send both browser and server events. The most common problem we find is that an older Pixel code or a third-party tracking app is still installed alongside it, so purchases are sent twice. We keep one source, set the data sharing level and check that checkout events arrive with the correct values.

WooCommerce and WordPress

WordPress sites usually collect tracking from several places over the years: the theme, a page builder, a caching plugin that inlines scripts and one or two marketing plugins. We choose one integration, remove the rest and make sure caching does not stop events from firing on the order confirmation page. For server events we use the official integration or a well-maintained plugin that supports the Conversions API.

Other site builders

Wix, Squarespace and similar builders have built-in Meta integrations with fewer options. They are usually fine for browser events; server events depend on the plan you are on. We tell you honestly what your platform can and cannot do before you pay for more than it supports.

Custom sites

For custom-built sites we install the browser Pixel through a tag manager and write a short specification for your developer covering which server events to send, with which parameters and event IDs. We then test their work exactly as we test our own.

How we set up your Pixel, step by step

1. Audit what is already there

We check how many Pixels exist, who owns them, which tools on your site already send events and what Events Manager currently receives. Many sites have two or three sources sending the same purchase, and finding them is often half the fix.

2. Ownership in your Business Manager

Your Pixel, also shown as a dataset in newer menus, must belong to your own business, not to an agency or a former developer. If it does not, we help you set up or move ownership before anything else, because tracking history stays with whoever owns it.

3. Install the Pixel

We use your platform’s official integration where one exists, or a tag manager or direct code where it does not. We remove duplicate or outdated installations so only one source sends each browser event.

4. Connect the Conversions API

In the Standard and Pro packages we connect the Conversions API through your platform’s integration or, for custom sites, guide your developer through it. We make sure browser and server events share an event ID so they are deduplicated.

5. Configure events and values

We set up the core events for your business type, with correct values, currencies and content IDs. In the Pro package we add custom events, such as a qualified lead, and set event priorities.

6. Domain verification

We verify your website domain in your Business Manager, which confirms that you control the site sending the events.

7. Test and hand over

Every event is tested, as described below, and you receive screenshots of each one firing plus a short guide to reading Events Manager yourself.

How we test every event

A setup is only finished when we can show it works. For each event we:

1. Trigger it ourselves on your live site, using a real or test product, form or booking.
2. Confirm it arrives in Events Manager’s Test Events view from the browser, the server, or both.
3. Check that browser and server copies are deduplicated into one.
4. Check the parameters: value, currency, content IDs and customer information where you collect it with consent.
5. Review the event match quality score and tell you what would improve it.

You receive screenshots of each step, so you have proof of what was working on the day we handed over.

How accurate tracking grows your sales

Better tracking does not make a weak offer sell. What it does is let you see which ads and audiences actually produce buyers, and let Meta find more of them.

When purchase events are reliable, sales campaigns learn faster, because the system receives real signals instead of noise. Retargeting reaches the people who added to cart and left, instead of everyone who ever visited. Lookalike audiences are built from real customers. And your decisions about budget, creative and products rest on numbers you can trust.

The cost of not fixing tracking is harder to see but usually larger: money moved away from campaigns that were working, or into campaigns that only looked good because of double counting. For a business spending a few thousand dollars a month on ads, one wrong decision based on bad data costs more than the setup.

Pros and cons of a professional setup

Who this service is for

• Stores whose Ads Manager purchases do not match their sales, in either direction.
• Businesses about to start sales or lead campaigns and wanting tracking right first.
• Anyone who changed theme, checkout or platform and suspects tracking broke.
• Businesses whose Pixel was installed by an agency or developer they no longer work with.

If your ads cannot run at all, tracking is not the first problem. Check your ad account setup or, if the account was stopped, our help for disabled ad accounts.

Common Pixel mistakes

1. Several installations at once: a plugin, a theme setting and pasted code all sending the same events.
2. Purchase on the wrong page: firing when the checkout opens rather than when payment is confirmed.
3. Missing value or currency on purchase events, or a hard-coded value.
4. No event ID, so browser and server events are counted twice.
5. A Pixel owned by someone else, such as a past agency.
6. Sending sensitive information, such as health details, in URLs or event parameters, which Meta’s terms do not allow.

Privacy and consent

Tracking has to respect the law where your customers live. In many regions, including the European Union and the United Kingdom, visitors must agree before marketing tracking runs. We work with your existing consent banner, or recommend you add one, so the Pixel only fires when it is allowed to. We do not give legal advice; if you are unsure what applies to your business, a local privacy professional is the right person to ask. Whatever the law, we never send personal data that your customers did not provide, and we keep sensitive categories of information out of every event.

How long it takes and what we need from you

A standard setup on a common platform usually takes two to three working days. Custom sites, multiple domains or complex funnels take longer and sometimes need your developer. To start, we need:

1. Your website address and the platform it runs on.
2. Temporary access to the site or store, through a staff account you create and remove.
3. Partner access to your Business Manager, or a call where you share your screen.
4. A list of the actions that matter to your business: purchases, leads, bookings or sign-ups.

Before you launch new campaigns on top of fresh tracking, it is worth running your ad text through our free ad policy checker, so a rejected ad does not hide how well your tracking now works.