Free Consultation

Digital Marketing · 4 min read

What Are the Meta Pixel and Conversions API?

The Meta Pixel tracks visitor actions in the browser and the Conversions API sends them from your server. Learn why both are used, events and privacy.

The Meta Pixel is code on your website that runs in the visitor's browser and reports their actions, called events, such as viewing a product or filling in a form, to Meta. The Conversions API does a similar job, but sends the data directly from your server instead.

Together they measure your Facebook and Instagram ad results and help Meta's ad system find people likely to be interested. This guide covers how they work, key terms and privacy basics.

Key points

  • The Meta Pixel sends events from the browser, the Conversions API from a server.
  • Using both keeps your data more complete when the browser pixel is blocked.
  • Events sent through both paths must be deduplicated to avoid double counting.
  • Tell visitors what you collect and ask for consent where required.

How the Meta Pixel Works

The Meta Pixel is a JavaScript snippet, code that runs in the browser, placed on your web pages. When a visitor loads a page or takes certain actions, it reports this to Meta, and the data appears in Events Manager, Meta's event dashboard.

This shows which ads lead to orders or inquiries, lets you show ads to past visitors (retargeting), and helps Meta optimize who sees your ads.

How the Conversions API Works

The Conversions API, or CAPI, sends events from your server, the computer running your website or business system, straight to Meta. Because it bypasses the browser, it keeps working when visitors use ad blockers or strict privacy settings.

CAPI can also send events from outside your website, such as an order confirmed in your system or an offline sale.

Why Use Both Together

The pixel is easy to install and captures many on-page actions, but ad blockers, cookie limits or dropped connections can make it miss events. CAPI is more reliable but needs server-side setup, so Meta recommends running both.

When one action arrives through both paths, Meta must recognize it as one event. Sending the same event name and event ID (a unique code per action) from the pixel and CAPI lets Meta discard the duplicate. This is deduplication.

What Are Events?

An event is a record of one visitor action. Meta offers standard events with fixed names, and you can add custom events for your business. Common ones are listed below.

  • PageView: a visitor opens a page.
  • ViewContent: a visitor views a product or service page.
  • Lead: a visitor submits a form or contact details.
  • Purchase: an order is completed, usually with its value and currency.

Related terms

Event
A record of one visitor action, such as opening a page or submitting a form.
Deduplication
Removing duplicate events so an action sent twice is counted only once.
Hashing
Turning data such as an email address into a fixed code that cannot be reversed.

Frequently asked questions

Is the Meta Pixel enough on its own?

The pixel works alone, but ad blockers and browser restrictions can make it lose events. Adding the Conversions API makes your data more complete, and Meta recommends using both.

Is the Conversions API only for online stores?

No. Any business advertising on Meta can use the Conversions API, including B2B companies that collect inquiries through forms. Leads or orders confirmed in an internal system can be sent too.

Where can I check that events are coming in?

Open Events Manager in your Meta business account to see incoming events, whether each came from the browser or server, and any warnings. The Test Events tool shows events live as you use your site.

Related services

More explainers

Start a project

Tell us the problem.We'll build the fix.

Free consultation on WhatsApp. Tell us about your business, what you want to build, and what is getting in the way.