Send your conversion events directly to Meta’s Conversions API (CAPI), now at the edge.
Find it on GitHub: /edgee-cloud/meta-capi-component
Meta Conversions API (CAPI) allows you to send web events directly to Meta from your server, ensuring reliable data tracking even with ad blockers or browser limitations. With Edgee’s edge integration, you can now send these events directly from the edge, improving both reliability and performance.
Here’s how Edgee events map to Meta CAPI events:
Edgee event | Meta CAPI Event |
---|---|
Page | PageView |
Track | Name of the event |
User | Lead |
When you make a user
call, Edgee stores the user’s data (user_id, anonymous_id, and properties) on the device. This enables proper attribution for subsequent page views and events.
To integrate Meta CAPI into your Edgee project:
edgee/meta-capi
from the list of available components.Meta Access Token
: Your Meta CAPI access tokenMeta Pixel ID
: Your Meta Pixel IDMeta Test Event Code
(Optional): For testing your implementationTo know how to get your access token and pixel ID, visit the Meta Marketing API documentation.
When configuring the component in your Edgee Data Layer or within SDK calls, use edgee/meta-capi
as the component name:
Use Meta’s Test Event Code during implementation to avoid affecting your actual data and ad campaigns.
For more details on Meta Conversions API implementation, refer to the official Meta CAPI documentation.