How is customer data protected in the CAPI Gateway?
All data is encrypted at the user’s browser whenever the pixel fires; none of it flows to Meta in raw format. Data is only one-way encrypted and passed in real-time to the Meta Ads platform when a customer gives consent to “Accept cookies”. No data is stored or retained on Datahash servers.
Related Articles
Meta CAPI for CRM
Overview: The Meta Conversion API for CRM is a performance optimization tool designed specifically for lead ads. It enables businesses to send updated lead information back to Meta, allowing for more precise optimization for campaigns that you are ...
Setting up Data Source for Snapchat Offline Conversions API
Offline Conversions API can be set-up using any one of the below available data sources that can provide offline events or conversion data. The type of data sources enable reading of CSV files at regular frequency e.g. daily. Data automation can be ...
App CAPI (Conversions API for App) Integration Guide
Overview: App CAPI enables server-to-server (S2S) event tracking for mobile apps, improving measurement accuracy in privacy-restricted environments like iOS (post-ATT) or Android with limited advertising ID access. It ensures more reliable ...
How is the data sent through the Conversions API Gateway secured?
Answer: First Party data sent through the Pixel is used in Conversions API Gateway which is securely hashed using a one-way encryption algorithm called SHA-256. This ensures that sensitive information, such as customer details, is anonymized before ...
Does the CAPI Gateway support consent management?
Yes, it follows Pixel’s consent settings. Data is only one-way encrypted and passed in real-time to the Meta Ads platform when a customer gives consent to “Accept cookies”.