Meta Conversions API
Meta Conversions API
Configure and inspect permission-aware server-side storefront measurement.
Connect eligible storefront events to Meta
An optional Meta Conversions API destination can forward supported PageView, ViewContent, AddToCart, InitiateCheckout and authoritative Purchase events. Configure the destination, event set and test code, verify the connection, then inspect redacted event outcomes.
Destination readiness, queued work, provider acceptance, Events Manager visibility and advertising attribution are different states. A configured worker or successful HTTP request alone does not prove an event reached Meta or produced a conversion.
SoundSync
Verify before activating
-
Configure
Save the destination and encrypted access token with forwarding disabled. Choose supported events.
-
Test
Use an Events Manager test code and queue a synthetic connection test. This sends an external test event.
-
Inspect
Read verification, readiness and event status. Correct destination, token or provider errors before activation.
-
Activate and monitor
Choose the intended mode, inspect accepted/failed/canceled work and replay only eligible retained failures.
Advertising measurement is separate from email enrollment
Meta forwarding uses its existing advertising-measurement permission and respects the supported Global Privacy Control, Do Not Track and visitor suppression checks. Purchasing or joining a developer email list does not supply that advertising permission. Declining measurement must not block ordinary browsing or checkout.
When enabled and permitted, events can include event/time/URL, product or order value, currency, browser matching identifiers and hashed customer matching fields. Hashing is not anonymization. Keep destination tokens private. A disconnect stops pending forwarding and removes saved destination credentials and supported checkout measurement snapshots; it does not erase history already held by Meta.
This integration does not change GA4 behavior or email preferences. Provider-side processing follows the developer destination and applicable provider terms. Use the existing privacy-request procedure for account-related requests; no new universal retention or delivery promise is made.
SoundSync
Configure the measurement destination
Actual settings before configuration. No provider acceptance or conversion is implied.