Meta Conversions API in 2026: what it is and how to set it up

The Meta Conversions API is a server-to-server connection that sends conversion events from your own systems to Meta. The Meta Pixel runs in the visitor's browser and fires when a page loads. The Conversions API runs on your server, in your shop platform or in a tool connected to your CRM, and fires when your system records the purchase or lead.

Both feed the same dataset in Meta Events Manager (your pixel ID is also your dataset ID). Meta calls the combination a redundant setup: the same event arrives twice, Meta keeps one copy and uses the extra customer information from each source for matching (Meta Business Help Center).

Why bother? Meta's delivery system learns from the conversions it sees. When it sees fewer purchases than you actually made, it optimises on a thinner and more skewed sample. In its announcement of 15 April 2026 Meta wrote that advertisers with a Conversions API setup for web events saw an average 17.8% lower cost per result than those without (Meta for Business, 15 April 2026). That is Meta's own average across advertisers, not a promise for your account.

The pixel only reports what a browser allows it to report, and more browsers allow less every year. The causes stack up, and they hit different audiences differently.

Be clear about what the Conversions API fixes. It recovers events lost to blockers, storage limits, closed tabs and redirects, and it adds offline and CRM events. It does not recover visitors who declined consent, because in the EU you should not send their data either. Consent is a legal question, not a tracking bug.

Pick the option that matches your shop system and your technical resources, not the most powerful one. A clean partner integration beats a half-finished custom build.

One limit of the one-click option matters: it mirrors events the browser pixel already produced. If a blocker stops the pixel, the mirror has nothing to send (WeltPixel analysis, 3 September 2026). It improves delivery reliability, it does not add events the browser never created. For the Gateway, Meta states that the only cost is the cloud resources or partner fees (Meta for Developers). For server-side GTM, Meta provides an official tag template (Meta for Developers).

Lead-gen businesses get the most from a CRM connection. A form fill is only a hint; the qualified lead or the signed contract two weeks later is the event you want Meta to optimise for.

For most online shops the fastest route is the official shop integration, then a test in Events Manager. Here is the path for Shopify, which covers a large share of small and mid-sized stores.

1. In Shopify admin, open Settings, then Apps and sales channels, then Facebook & Instagram.
2. Connect your Meta business account and select the ad account and the pixel (dataset) you already use.
3. Open the data sharing settings and set them to Maximum. Shopify then sends events through both the pixel and the Conversions API (Shopify Help Center).
4. Remove any second pixel you added manually in the theme or through another app, otherwise you send each purchase twice from the browser.
5. In Meta Events Manager, open the dataset and check that Purchase shows both Browser and Server as sources within a day.
6. Check deduplication and Event Match Quality on the Purchase event details (see the next sections).

Not on Shopify? In Events Manager, open your dataset, go to Settings and look for the Conversions API section. There you choose between a partner integration, the Gateway, the one-click option and a manual setup with an access token. WooCommerce stores install Meta's official plugin and enable the Conversions API in its settings.

Meta merges a browser event and a server event when both carry the same event_name and the same event_id. Meta generally keeps the event it received first and discards the duplicate. Deduplication only works when the two arrive within 48 hours of each other (Meta for Developers).

The simplest event_id is your order number or lead ID, because both the thank-you page and the server know it. The pixel passes it as eventID, the server as event_id:

// Browser: Meta Pixel on the thank-you page
fbq('track', 'Purchase',
  { value: 89.90, currency: 'EUR' },
  { eventID: 'order-10482' }   // same ID as the server event
);

{
  "data": [{
    "event_name": "Purchase",
    "event_time": 1791187200,
    "event_id": "order-10482",
    "action_source": "website",
    "event_source_url": "https://shop.example.com/thank-you",
    "user_data": {
      "em": ["<SHA-256 hash of the lowercased email>"],
      "ph": ["<SHA-256 hash of the phone number>"],
      "fbp": "fb.1.1791180000000.123456789",
      "fbc": "fb.1.1791180000000.AbCdEf",
      "client_ip_address": "203.0.113.7",
      "client_user_agent": "Mozilla/5.0 ..."
    },
    "custom_data": { "currency": "EUR", "value": 89.90 }
  }]
}

There is a fallback that matches on fbp or external_id instead, but Meta documents its limits: it only works when the browser event arrives first, and it does not remove duplicates within one source. Use event_id whenever you can.

• Same spelling of the event name on both sides: Purchase is not purchase.
• Same ID format: order-10482 in the browser and 10482 on the server do not match.
• One source per channel: if a plugin and a GTM container both send server purchases, Meta sees two server events and cannot merge them.

Event Match Quality (EMQ) is Meta's score from 0 to 10 for how well the customer information in your server events matches Meta accounts. Events Manager shows it per event, calculated from the last 48 hours of data. Better matching means more of your events get tied to a person who saw your ad, which Meta links to more reported conversions and a lower cost per result (Meta Business Help Center).

Meta does not publish a target number. Practitioners usually treat Purchase events above 8 as good, because the buyer has typed an email and a phone number by then. PageView events score lower by nature, since the visitor has not told you anything yet. If your Purchase EMQ sits below 6, check first whether email and phone are sent at all.

Use the Test events tab in Events Manager before you trust any number. It shows incoming browser and server events in near real time (Meta Business Help Center).

1. In Events Manager, open your dataset and click Test events.
2. For the pixel, enter your shop URL and place a test order. For server events, copy the test code shown there and add it as test_event_code to the server payload.
3. Check that Purchase appears twice, once from the browser and once from the server, and is marked as deduplicated.
4. Compare value and currency on both events. A purchase of €89.90 should not arrive as 8990.
5. Remove the test_event_code afterwards. Meta still processes events that carry it, so a forgotten code leaves test traffic mixed into your data.
6. A few days later, open the Diagnostics tab and the event overview for warnings about missing parameters or low deduplication.

Server-side sending does not remove the need for consent. This section is general information, not legal advice. Talk to your data protection officer or a lawyer about your setup.

• Setting or reading the pixel cookie on a device in Germany needs consent under § 25 TDDDG (gesetze-im-internet.de). Austria and the rest of the EU have equivalent rules based on the ePrivacy Directive.
• Sending personal data such as a hashed email to Meta needs a legal basis under the GDPR. For advertising purposes this is usually the visitor's consent. Hashing is pseudonymisation, it does not make the data anonymous.
• The European Court of Justice ruled in Fashion ID (C-40/17, 29 July 2019) that a website operator who embeds a Facebook tool is a joint controller for collecting and transmitting the data (CURIA). Accept Meta's business tools terms and describe the processing in your privacy policy.
• Transfers to the US currently rely on the EU-US Data Privacy Framework, adopted by the European Commission on 10 July 2023 (European Commission).
• Switzerland applies its revised Data Protection Act, in force since 1 September 2023 (Federal Office of Justice).

In practice: pass the consent status from your consent banner to whatever sends server events, and only send events for visitors who agreed. Send the fields you need for matching and nothing more.

• No event_id, so every purchase counts twice and reported ROAS doubles overnight.
• Two server sources at once, for example the Shopify integration plus a server-side GTM tag.
• Value sent in cents or without currency, which breaks ROAS and value-based bidding.
• Unhashed email or phone numbers in fields that require SHA-256 hashing.
• Old events: event_time may be at most 7 days in the past, so a nightly batch job that falls behind loses events.
• An expired or revoked access token after a team member leaves. Server events stop without an error on your website.
• Server events sent for visitors who declined consent.
• Optimising for a form submit when the CRM already knows which leads became customers.

Once tracking is clean, the next question is what the numbers are worth. Meta's reported revenue still overlaps with Google and TikTok, so compare it with your shop revenue using true ROAS and MER, and check your break-even with the ROAS calculator. If you are still planning your first campaigns, start with how to run Facebook ads.

Marketing AIgency's AI agents review Meta ad accounts, work through the numbers and put every suggested change with its reasoning into an approval queue. The Attribution add-on sends your conversions back to Meta through the Conversions API, so Meta's delivery learns from the purchases and leads your business actually recorded. The agents themselves steer on that company number instead of platform ROAS.

Plans have fixed monthly prices with no percentage of ad spend. Add-ons such as Attribution can be booked on any plan, see pricing.