Guide
Meta Conversions API
Configure, verify, monitor, replay and disconnect optional event forwarding.
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
Read the actual outcome
| State | Meaning |
|---|---|
| Disabled | No new forwarding for the disabled destination. |
| Testing | Uses the saved test event code; not production attribution evidence. |
| Queued / processing | Work exists but provider acceptance is not yet established. |
| Accepted | Provider accepted the request; inspect Meta separately for event visibility and attribution. |
| Failed / canceled | Inspect the safe explanation. Replay is limited to recent retained failures at the same destination/configuration, with at most three replays. It cannot bypass suppression or expiry. |
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
Implementation
SoundSync
Configure the measurement destination
Actual settings before configuration. No provider acceptance or conversion is implied.