| 开发者 | capiflow |
|---|---|
| 更新时间 | 2026年5月13日 23:06 |
| PHP版本: | 7.4 及以上 |
| WordPress版本: | 6.9 |
| 版权: | GPLv2 or later |
| 版权网址: | 版权信息 |
event_id for deduplication.
How It Works
event_id to support Meta's deduplicationfbc, fbp, external_id, client IP, user agent, and hashed customer data (email, phone, name) for logged-in users.
Analytics & Monitoring
capiflow_proxy_url, capiflow_has_tracking_consenthttps://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:
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
cs_uid — Random visitor identifier for external_id deduplication. 180 days. No PII._fbc — Meta Click ID. Set by Meta SDK on ad click. CapiFlow reads/extends server-side. 180 days._fbp — Meta Browser ID. Set by Meta SDK. CapiFlow reads/extends server-side. 180 days.{prefix}_capiflow_events — Queued/sent event payloads. Auto-purged after delivery.{prefix}_capiflow_analytics — Daily aggregated analytics. Auto-purged by retention settings._capiflow_ prefix. Removed on uninstall if "Keep Data" is disabled.wp-content/uploads/capiflow-logs/ with .htaccess protection. Auto-cleaned daily.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.
capiflow to /wp-content/plugins/.No. CapiFlow works alongside the browser pixel using Meta's recommended redundant setup — both share a matching event_id for deduplication.
No. Matching event_id values ensure Meta deduplicates browser and server events automatically.
No. CapiFlow sends events directly from your WooCommerce server to Meta — no separate GTM server container, third-party service, or monthly subscription needed.
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.
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.
Both traditional posts-based and HPOS (High-Performance Order Storage). Auto-detected, no configuration needed.
Yes. CapiFlow uses WooCommerce's standard order status hooks. Compatible with bKash, Nagad, SSLCommerz, Stripe, PayPal, COD, and all standard gateways.
Purchase event is held until admin confirms the order, preventing unverified COD orders from reaching Meta.
No. CapiFlow works standalone. If you need GTM or other scripts, a built-in code injection feature is included.
A separate addon that adds fraud protection, negative Purchase events for cancellations, multi-pixel routing, courier integration, and real-time EMQ scores. Learn more.