If you use Meta Pixel tracking in ESC Hub and have been migrating to the new Events tab, this update reduces the risk of losing tracking on events you have not yet fully migrated.

What's changed

Legacy event suppression now operates at the individual event level rather than as a global switch. Previously, enabling the Events tab could unintentionally suppress legacy events across the board - even ones that had not yet been replaced by a new configuration. That is no longer the case.

Now, a legacy event is only suppressed when its direct replacement has been configured. For example, SubmitApplication is suppressed only when InitiateCheckout or AddPaymentInfo is configured. OrderFormPurchase is suppressed only when Purchase is configured. Any step left unmapped continues firing its legacy event, so there are no attribution gaps while you work through the migration.

PageView and ViewContent events now pass a privacy-safe external_id on both the browser pixel and Conversions API, improving event matching and deduplication. Richer order data - including value, currency, and product IDs - is now sent for both Purchase and InitiateCheckout events.

If you have not started migrating to the Events tab, nothing changes. All legacy events continue firing exactly as before.

Why it matters

Partial migrations to a new tracking setup should not mean losing data on the events you have not touched yet. This update ensures your tracking stays intact at every stage of the migration, with fewer silent drops and better match quality across your Meta Pixel events.