E-commerce integrations

Shopify

The most popular integration. Connects via OAuth with real-time webhooks + Web Pixels.

Setup

1. Go to Settings → Data Pipes → New → Shopify
2. Click Connect — you’ll be redirected to Shopify to authorize the Active Reach app
3. After authorization, select what to sync:
   • Customers — new customers, profile updates
   • Orders — order placed, fulfilled, refunded, cancelled
   • Products — product created, updated, deleted
   • Cart events — cart created, updated (via Shopify Web Pixels)
4. Field mapping is automatic for standard fields. Map custom metafields if needed.
5. Click Activate

What syncs

Web Pixels

Shopify Web Pixels provide real-time browser-side event tracking (page views, product views, add-to-cart) without installing the Active Reach SDK separately. Enabled automatically during setup.

Liquid bridge — extra customer fields

Shopify’s Liquid customer object exposes additional fields that the Web SDK forwards to Active Reach so segments and journeys can target them: phone, accepts_sms_marketing, locale, and default_address. Combined with Web Pixels this gives the SDK enough context to identify the contact without requiring a separate identify() call on every page.

Back-in-stock waitlists

The back-in-stock (BIS) pipeline turns “notify me” intent into a fan-out send when a product restocks:

1. The customer taps the <BackInStockButton> rendered on the PDP (cashier-portal) or the equivalent DOM-injected button on a native Shopify theme
2. The SDK fires aegis.ecommerce.productWaitlisted() (Web SDK 1.13.0+) carrying the product_id + contact identifiers
3. On a Shopify product_restocked webhook, the cell-plane stock_event_handler_worker invokes _fanout_waitlisted_contacts and emits a catalog.back_in_stock event per waiting contact (older waitlist signups expire per the platform’s retention window)
4. Operators wire that event into a journey to deliver the actual notification (no default template ships)

productWaitlisted must include a contact_id (the SDK reads it from the identity stash) — if it’s missing, the journey trigger consumer drops the event silently.

WooCommerce

Setup

1. Go to Settings → Data Pipes → New → WooCommerce
2. Enter your WooCommerce store URL
3. Generate REST API keys in WooCommerce (Settings → Advanced → REST API → Add key)
4. Enter the Consumer Key and Consumer Secret
5. Select what to sync and activate

What syncs

Same events as Shopify: customers, orders, products. Cart events require the Active Reach Web SDK installed on your WooCommerce frontend.

Meta Pixel plugin

Tenants who already run a Meta Pixel (Facebook Pixel) for ad attribution can pair it with Active Reach without double-instrumenting events. The Web SDK ships a first-party Meta Pixel plugin that registers through the SDK’s typed PluginRegistry and adds two capabilities:

• _fbp / _fbc cookie management — first-party match keys Meta uses for Event Match Quality (EMQ). The plugin writes _fbp on init (90-day TTL), captures _fbc from ?fbclid=<id> on landing, and persists both across page loads. Consent-gated: when the customer denies marketing consent the cookies are neither written nor stamped onto events.
• aegis.lastEventId(eventName) — returns the messageId of the most recent track(<name>) call. Pass this as event_id into your client-side Meta Pixel call so Meta dedups the client event against the cell-plane’s server-side Conversions API send.

Operator setup:

1. Enable the plugin in your Active Reach workspace at Settings → Integrations → Meta Pixel (toggle, paste your Pixel ID).

2. The Web SDK pulls the Pixel ID from the bootstrap response and registers the plugin automatically.

3. In your existing Meta Pixel snippet, replace static eventID strings with the SDK’s aegis.lastEventId(...):

   <script>
     fbq('track', 'Purchase', { value: 49.99, currency: 'INR' }, {
       eventID: window.Aegis.lastEventId('order_completed'),
     });
   </script>

Mobile parity ships as MetaPixelCompanion on the iOS / Android / React Native / Flutter SDKs (Phase 4.5). The mobile companions persist _fbp / _fbc equivalents to local storage and stamp them onto every outgoing event’s metadata so the cell-plane’s Meta CAPI service has matching keys without needing a parallel mobile-side Pixel install. Cross-SDK wire contract pinned by libs/mobile-sdk/tests/drift/meta-pixel-companion-contract.json.

Magento

Setup

1. Go to Settings → Data Pipes → New → Magento
2. Enter your Magento store URL
3. Create an Integration in Magento (System → Integrations → Add New)
4. Enter the OAuth credentials
5. Activate

What’s next

• CRM integrations — sync contacts with your CRM
• Import contacts — alternative data import methods