What MIQAS sends back to Meta (CAPI, explained)

The Conversions API (CAPI) is Meta's server-to-server channel: instead of the browser reporting events, MIQAS's servers do. Nothing to install beyond the pixel, and ad blockers or browser privacy features cannot interfere.

What is sent

• PageView on every visit, ViewContent on product pages
• AddToCart and InitiateCheckout as they happen
• Purchase with the order value and currency

All under Meta's standard event names, which is what lets them count in your reporting and feed ad delivery optimization. Lead businesses send their pipeline stages the same way; see What MIQAS sends back for lead businesses.

Identity signals

Each event carries the signals Meta matches people with: the browser IDs (fbp, fbc), the click ID when the visit came from an ad, IP and user agent, and hashed email or phone where the order includes them. Hashing is one-way, and only hashes ever reach an ad platform. If you switch on the built-in CRM, MIQAS keeps your contacts' details in encrypted form for your workspace alone; what leaves MIQAS is still the hash.

Deduplication

Every event travels with a stable event ID (purchases use your order ID), so if the same event ever reaches Meta twice, from two channels or a retry, Meta keeps exactly one copy.