Full Answer

Traditional tracking architectures require separate configuration for each destination. GTM needs a tag for GA4, a tag for Facebook, a tag for Google Ads — each with its own triggers, variables, and Data Layer requirements. Changing one destination risks breaking another because they share the same container configuration space.

The outPIPE model decouples these concerns. The inPIPE plugin captures a WooCommerce event once, at the PHP hook level, with all available data — order value, product details, customer identifiers, attribution parameters. That single event payload reaches the server-side processing layer, which passes it to every configured outPIPE simultaneously.

Each outPIPE is responsible for one destination and handles that destination's specific requirements independently. The Facebook CAPI outPIPE SHA256-hashes email, phone, and name fields, constructs the correct event payload with event_id for deduplication, and sends via Meta's API. The GA4 outPIPE formats the same event for Google's Measurement Protocol with the correct client_id and session parameters. The BigQuery outPIPE writes the raw event with full schema to your warehouse.

The architectural advantage is isolation. When Meta changes its CAPI payload requirements — which happens regularly — only the Facebook outPIPE needs updating. GA4, BigQuery, and every other destination continue operating unchanged. When you add a new destination like TikTok Events API, you add one outPIPE without touching the existing pipeline. The inPIPE captures once. The outPIPEs deliver everywhere.