Meta pixel enhancement with suppression logic for legacy event tracking

Overview

EveryCatch now handles Meta Pixel tracking more reliably when you move to the new Events tab. Instead of turning off all legacy events at once, suppression now works at the individual event level, so new event setups do not accidentally stop tracking in other parts of your funnel. We have also expanded external_id coverage and added several behind-the-scenes improvements to keep event delivery stable.

What changed

• Event-level suppression – Legacy events are now suppressed only when their specific replacement event is configured in the Events tab, instead of being controlled by a single global switch for the entire tab.

1. SubmitApplication is suppressed only when InitiateCheckout and/or AddPaymentInfo are configured as its replacements in the Events tab.
2. OrderFormPurchase is suppressed only when Purchase is configured in the Events tab.
3. Any step that you do not map to a new event keeps sending its original legacy event, which helps you avoid attribution gaps while you complete your migration.

• external_id on PageView and ViewContent – These events now include a privacy-safe customer identifier (no personal information) for both the browser pixel and the Conversions API. This improves how Meta matches events to people and how duplicate events are handled between browser and server.
• Legacy behaviour remains unchanged by default – If you leave the Events tab empty, EveryCatch continues using the previous legacy event setup. All legacy events keep firing exactly as they did before, so nothing changes for accounts that have not started migrating yet.
• Richer order details – When Purchase and InitiateCheckout fire, EveryCatch now sends more complete order data, including value, currency, and product IDs, which helps Meta report and optimize with better accuracy.
• No silently dropped pixels – Pixels that you have not migrated into the Events tab continue firing correctly, even if some events are already using the new suppression rules, so you can transition in stages without unexpected gaps.

Why it matters

• If your account is only partly migrated to the new Events tab, your remaining legacy events keep tracking correctly instead of stopping early.
• external_id on more events improves Meta’s ability to deduplicate browser and server events and to match them to the right contact.
• You should see fewer invisible tracking failures and fewer backend retry errors when sending events to Meta.

Good to know

Add and manage your Meta events only through the Events tab in EveryCatch. Mixing Events tab configuration with separate custom pixel scripts can create overlapping or inconsistent tracking results.

A visitor’s external_id reflects their current contact identity in EveryCatch and can change during a single session if they submit a form or complete an order while browsing. This behaviour is expected and does not interfere with server-side identity stitching or event deduplication on Meta’s side.