Linux 软件免费装
Banner图

CapiFlow – Conversions API (CAPI) Tracking for WooCommerce

开发者 capiflow
更新时间 2026年5月13日 23:06
PHP版本: 7.4 及以上
WordPress版本: 6.9
版权: GPLv2 or later
版权网址: 版权信息

标签

woocommerce facebook pixel meta pixel server-side tracking conversions api

下载

1.0.0

详情介绍:

CapiFlow sends supported WooCommerce events from your server to Meta's Conversions API (CAPI) — helping reduce the impact of browser-side tracking limitations like ad blockers, Safari ITP, and Firefox ETP. Why Server-Side Tracking Matters When the Meta pixel is blocked, event data may not reach Meta — affecting ad optimization. CapiFlow complements the browser pixel by sending events server-side with a matching event_id for deduplication. How It Works
  1. Install & Activate — Setup wizard launches automatically
  2. Enter Pixel ID + Access Token — From Meta Events Manager
  3. Click Test Connection — Events start flowing
No theme edits. No GTM server container required. No separate server-container subscription needed for the built-in Meta CAPI workflow. Core Features Server-Side Event Tracking Event Match Quality Supportfbc, fbp, external_id, client IP, user agent, and hashed customer data (email, phone, name) for logged-in users. Analytics & Monitoring Data Quality & Control Developer Tools CapiFlow Pro CapiFlow Pro is a separate addon that extends the free plugin with: Learn more on the CapiFlow website. Compatibility Requirements External Services This plugin connects to the following third-party services: Meta (Facebook) Conversions API CapiFlow sends WooCommerce event data to the Meta Conversions API via: https://graph.facebook.com/ This connection is made from your server to Meta's servers when a configured tracking event occurs. No data is sent until a valid Pixel ID and Access Token are configured. Data transmitted includes: All personal data is SHA-256 hashed before transmission. Meta Pixel JavaScript SDK This plugin loads the Meta Pixel SDK from: https://connect.facebook.net/en_US/fbevents.js Loaded on frontend pages when a Pixel ID is configured. The SDK is hosted by Meta. Privacy For server-side events, all personal data is SHA-256 hashed before transmission. For browser events, the Meta Pixel SDK handles hashing via Advanced Matching. This plugin does not store raw PII in its own tables. See Meta's privacy policy. Cookies All cookies are first-party and contain no personally identifiable information. Data Storage Consent By default, events fire once configured. Enable "Consent Enforcement" in Settings to respect CMP signals for both browser and server events. Supported CMPs: CookieYes, Complianz, CookieBot, GDPR Cookie Consent. Custom integration via capiflow_has_tracking_consent filter. When Consent Enforcement is enabled, browser and server-side events are blocked until valid tracking consent is detected. Store owners are responsible for lawful consent configuration where required by privacy regulations.

安装:

  1. Install from WordPress plugins screen or upload capiflow to /wp-content/plugins/.
  2. Activate through the Plugins menu.
  3. Setup wizard launches — enter Pixel ID and Access Token.
  4. Click Test Connection — check CapiFlow → Dashboard to monitor.
Getting an Access Token
  1. Meta Events Manager → Select Pixel → Settings → Conversions API
  2. Click Generate Access Token or create a System User
  3. Paste into CapiFlow → Settings → Pixel Settings

屏幕截图:

  • **Settings Page** — Pixel ID, Access Token, and connection test
  • **Analytics Dashboard** — Event tracking overview
  • **Event Configuration** — Per-event browser and server toggles
  • **System Health** — Token validity and queue status
  • **Debug Console** — Event log with API responses
  • **Order Columns** — CAPI sync status in order list
  • **Pixel Helper** — Browser and server event verification
  • **Event Test Tool** — All events delivery status
  • **Purchase Event** — Server-side Purchase with API response

升级注意事项:

1.0.0 Initial public release.

常见问题:

Does this replace the Meta browser pixel?

No. CapiFlow works alongside the browser pixel using Meta's recommended redundant setup — both share a matching event_id for deduplication.

Will this cause duplicate events?

No. Matching event_id values ensure Meta deduplicates browser and server events automatically.

Do I need a GTM server container or a service like Stape.io?

No. CapiFlow sends events directly from your WooCommerce server to Meta — no separate GTM server container, third-party service, or monthly subscription needed.

How does this support Event Match Quality?

CapiFlow sends fbc, fbp, external_id, client IP, user agent, and hashed customer data — additional signals that can improve event matching vs browser-only tracking.

How is privacy handled?

All PII is SHA-256 hashed before transmission. Consent Enforcement toggle blocks events until CMP consent is granted. Privacy policy content auto-added to your WordPress Privacy Policy page.

Which order storage is supported?

Both traditional posts-based and HPOS (High-Performance Order Storage). Auto-detected, no configuration needed.

Does this work with my payment gateway?

Yes. CapiFlow uses WooCommerce's standard order status hooks. Compatible with bKash, Nagad, SSLCommerz, Stripe, PayPal, COD, and all standard gateways.

What happens with COD orders?

Purchase event is held until admin confirms the order, preventing unverified COD orders from reaching Meta.

Do I need Google Tag Manager?

No. CapiFlow works standalone. If you need GTM or other scripts, a built-in code injection feature is included.

What is CapiFlow Pro?

A separate addon that adds fraud protection, negative Purchase events for cancellations, multi-pixel routing, courier integration, and real-time EMQ scores. Learn more.

更新日志:

1.0.0 — 2026-05-01