Book a call

Conversions API · Meta CAPI, LinkedIn CAPI and Google Enhanced Conversions

Conversions that
reach the platform.

Browser pixels lose conversions to ad blockers, browser restrictions and declined cookies. With the Conversions API, conversions are also sent server-side and deduplicated, so Meta, LinkedIn and Google optimise on more complete data.

Meta CAPILinkedIn CAPIEnhanced ConversionsServer-side GTMDeduplication
4.9 from more than 100 reviews across several platforms
01

More conversions attributed

Server events close part of the gap left by the browser pixel.

02

Better optimisation

Bidding algorithms learn from more complete conversion data.

03

Consent respected

Server events are only sent where consent and legal basis allow it.

Guide · Conversions API

Conversions API: setup for Meta, LinkedIn and Google

The Conversions API sends conversion events directly from a server to the ad platform. Combined with the browser pixel and deduplication, it is today’s standard for reliable conversion tracking.

How the Conversions API works

When a purchase or lead happens, the browser pixel and the server send the same event with the same event_id. The platform recognises the duplicate and counts it once. If the pixel is blocked, the server event still arrives.

Ways to implement it

Which way fits depends on your systems and requirements.

Server-side GTM

Flexible and vendor-independent, on your own subdomain. See server-side tracking.

Partner integrations

Shop systems and CRMs often offer native integrations, quick to start but less control.

Direct API

For custom backends and offline conversions from the CRM.

Event match quality and data protection

Platforms match server events using hashed customer data such as email or phone number. We only send this data with consent and a legal basis, hash it before transfer and document the setup for your data protection officer.

Frequently asked questions

Do I still need the pixel?

Yes. Pixel and Conversions API work best together, with deduplication via event_id.

Is the Conversions API GDPR compliant?

It can be, if consent and legal basis are in place, data is minimised and hashed and the setup is documented.

How long does implementation take?

Typically two to four weeks including testing, depending on systems and platforms.

Can offline conversions from the CRM be sent?

Yes. Closed deals from the CRM can be sent back to Meta, LinkedIn and Google so campaigns optimise on real revenue.

How many conversions
is your pixel missing?

Request a free tracking check →
How we work

From the first message to ongoing support.

  1. 01Enquiry

    Book a call or send a short message. We usually reply within a few hours, and always within 24 hours on working days.

  2. 02Introduction

    30 minutes, free of charge: your goals, your starting point and whether we are a good fit.

  3. 03Project scoping

    We review your setup, agree on scope and priorities and tell you honestly what is worth doing.

  4. 04Proposal

    Broken down by services, effort and timeline, as a fixed price, time and materials or a monthly retainer.

  5. 05Delivery

    One dedicated contact with a deputy during holidays, regular updates and documentation that belongs to your team.

  6. 06Support or handover

    Ongoing with fixed check-ins, or a handover with training so your team can take over.

Why is there no price here?

Because no two projects are alike. A serious proposal requires that we understand your goals, setup and needs. That is why you receive a price after the introduction and scoping call, transparent and without hidden items.

For procurement and data protection

Data processing agreement, TOMs, NDA, terms and company profile are ready, so that approval on your side is quick.

View documents →

Book a 30-minute call

Open at Calendly ↗ · Send a message instead · Privacy settings