How does Datahash ensure user privacy with the CAPI Gateway?

How does Datahash ensure user privacy with the CAPI Gateway?

All data is encrypted at the user browser itself whenever the pixel fires. None of it flows to Meta in raw format. Only when a customer gives consent to “Accept cookies”, this data get one-way encrypted and passed across in real-time to the Meta Ads platform. No data is stored or retained within Datahash servers.

    • Related Articles

    • 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 ...

    • Data Privacy : We can’t share sensitive user level PII with any third-party platform for CAPI.

      Datahash’s CAPI solution DOES NOT read or store any user level PII data, but only sends consented, one-way encrypted (SHA256) PII such as Name, Email & Phone with website events for Snap to match them against their ad-impressions. With one-way ...

    • 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 ...

    • Source setup as Leadsquared for Meta CRM CAPI

      Prerequisites A LeadSquared account that is set-up to capture leads from Meta Lead Ads (Instant Forms) A custom field created in LeadSquared leads detail page that captures Meta Lead ID from Meta Lead Ads (Instant Forms). The Meta Lead ID field in ...

    • Pre-requisites for Meta CRM CAPI

      Lead Id should be stored in your CRM that is generated from the lead ad campaigns. Refer to this article Minimum 3 events need to be passed back to META so that META can create a funnel and optimize better Ensure a conversion of min 1% from the ...