Meta’s Conversions API

Meta's Conversions API offers an alternative to traditional pixel tracking. It lets you send conversion events directly from your backend to Meta Ads, giving you more control over your data sharing. You can send important events like purchases and leads directly to Meta, which helps optimize your Facebook Ads campaigns.

Why use Meta’s Conversions API

Respond to tracking limitations

Browser tracking prevention and ad blockers reduce Meta Pixel's reliability. The Conversions API provides a more reliable way to track conversions by bypassing these browser-based limitations.

Control your data sharing

You get direct control over data sharing scope using customer consent. You decide what information to send to Meta based on your consent management framework settings.

Capture more events

The API captures offline and deep-funnel events that pixels might miss. This gives you a more complete picture of customer behavior and events that traditional pixel tracking can't reach.

How the Conversions API works

With Bloomreach Engagement, you collect customer data through the JavaScript SDK and control exactly what gets shared with Meta based on your consent management settings.

Process

You collect customer data through Bloomreach's JavaScript SDK.
Your consent management framework determines what data you can share.
Bloomreach Engagement sends only approved data directly to Meta's servers.
Meta receives conversion events without relying on browser pixels.

This gives you control over the data sharing process while maintaining campaign effectiveness.

Data privacy and hashing

Meta’s Conversions API uses hashing to protect customer privacy, offering a more privacy-friendly way to track customer interactions:

Email addresses are hashed using SHA-256 before sending.
Phone numbers are normalized and hashed.
Personal identifiers are converted to irreversible codes.