Overview:
This update makes Meta Pixel tracking more reliable for accounts migrating to the new Events tab. Legacy event suppression now works at the individual event level instead of acting like an all-or-nothing switch. This helps prevent newly configured events from unintentionally disabling tracking elsewhere. External_id coverage has also been expanded, along with several reliability improvements.
What’s new
- Event-level suppression: Legacy events are now suppressed only when their direct replacement has been configured, rather than when the Events tab is enabled globally.
- SubmitApplication is suppressed only when InitiateCheckout / AddPaymentInfo are configured.
- OrderFormPurchase is suppressed only when Purchase is configured.
- Any step left unmapped continues firing its legacy event, helping avoid attribution gaps.
- external_id on PageView and ViewContent: These events now pass a privacy-safe customer identifier (no personal information) on both the browser pixel and Conversions API to improve event matching and deduplication.
- Legacy behavior remains the default: If the Events tab is left empty, the system continues using legacy behavior. All legacy events continue firing as before for accounts that have not started migrating.
- Richer order details: More complete order data (value, currency, product IDs) is now sent for both Purchase and InitiateCheckout.
- No silently dropped pixels: Pixels that have not yet been migrated to the Events tab will continue firing correctly, even when partial suppression rules are active.
Why it matters
- Accounts that are partially migrated to the new Events tab can keep tracking on legacy events until replacements are configured.
- Improved deduplication and match quality through external_id on more events.
- Fewer silent tracking drops and fewer backend retry failures.
Good to know
Add events exclusively through the Events tab. Combining Events tab tracking with manually added custom scripts may lead to inconsistent results.
A visitor’s external_id represents their current contact identity and may change during a session if they submit a form or place an order while browsing. This is expected and does not impact server-side identity stitching or deduplication.
