內容簡介
CapiFlow 是一款 100% 自我托管的伺服器端追蹤引擎，專為 WooCommerce 設計。它能直接將轉換事件從 WordPress 伺服器發送至 Meta Conversions API，無需雲端主機費用，並提供簡易的三步驟設置，幫助商家提升廣告優化效果。
【主要功能】
• 100% 自我托管，無雲端主機費用
• 三步驟簡易設置，無需 GTM
• 實時追蹤無限事件，無額外費用
• 防止假訂單影響廣告優化
• 提升事件匹配質量 (EMQ) 至 9.0+
• 支援 180 天 Safari ITP 第一方 Cookie 追蹤
外掛標籤
開發者團隊
② 後台搜尋「CapiFlow – Conversions API (CAPI) Tracking for WooCommerce」→ 直接安裝（推薦）
原文外掛簡介
CapiFlow is a 100% self-hosted, enterprise-grade server-side tracking engine for WooCommerce. Send conversion events directly from your WordPress server to the Meta Conversions API (CAPI) with zero cloud hosting bills, 3-click setup, and intelligent algorithm protection.
Unlike conventional tracking tools, CapiFlow eliminates the need for expensive external server containers (saving you $240+/year), ensures 0ms checkout speed impact, and prevents fake or unverified orders from corrupting your Meta ad optimization.
42% of online shoppers run ad blockers, and Apple Safari ITP silently wipes out 30%–40% of standard browser pixel conversions. CapiFlow restores your lost revenue attribution by bypassing browser restrictions completely — sending high-fidelity conversion events directly from your WordPress server to Meta Events Manager.
For Store Owners & Media Buyers
For WooCommerce Store Owners: Maximize real ROAS, stop fake Cash-on-Delivery (COD) orders from poisoning your ad optimization, and save $240–$1,200/year in cloud server bills.
For Media Buyers & Agencies: Achieve 9.0+ Event Match Quality (EMQ), 100% deterministic deduplication, and 180-day Safari ITP first-party cookie attribution without touching GTM.
💰 Save $240+/Year — 100% Self-Hosted ($0 Cloud Hosting Fees)
Why pay $20 to $100 every single month to third-party services like Stape.io, Google Cloud, or AWS just to run a server GTM container?
Zero Cloud Bills: CapiFlow runs 100% natively on your existing WordPress server.
Unlimited Events: Track unlimited page views, carts, and purchases without event tier limits or surprise overage charges.
No GTM Required (3-Click Setup): Completely removes web/server GTM container complexity, triggers, and dataLayer debugging. Simply paste your Pixel ID and Access Token, toggle on, and click Save. Setup takes under 3 minutes.
🚀 Zero-GTM Nightmare — Skip 25+ Tags, Containers & Hours of Debugging Hell
95% of store owners are not tracking engineers or programmers. You got into e-commerce to sell great products and grow your brand — not to spend your weekends configuring complex tracking infrastructure:
The 4-Layer GTM Nightmare (Designed for Coders): Traditional server tracking forces merchants through an excruciating technical gauntlet:
Build TWO Separate GTM Containers: Must create and juggle both a Web and a Server GTM container.
Write 25+ Custom DataLayer Variables (DLVs): Manually mapping ecommerce.items.price, currency, user_data.email, transaction_id, etc.
Configure Complex Triggers & Client Templates: Manually setting triggers for every event and configuring HTTP client request templates.
Connect Stape.io or GCP Custom Domains: Setting up DNS records, provisioning SSL certificates, and configuring transport URLs.
The Silent Attribution Killer (Zero Error Warnings): In GTM, a single missing comma, an event_id mismatch between web and server containers, or a tiny dataLayer discrepancy (like ecommerce.items vs. items) breaks tracking completely in silence. Your store shows ZERO error messages, yet data stops reaching Meta, Event Match Quality (EMQ) plummets to 3/10, Meta’s AI optimization flies blind, and your ad costs (CPA) double without warning! Most store owners end up spending $150–$300 hiring tracking freelancers just to debug the mess.
The CapiFlow 3-Click Freedom: Everything is 100% pre-engineered, native, and automated. No GTM containers. No dataLayer code. No tags or triggers to configure:
Paste your Pixel ID & Meta Access Token.
Toggle the events you want to track.
Click Save & Test Connection.
Setup takes under 3 minutes, saves you $150–$300 in agency setup fees, eliminates debugging headaches forever, and delivers a 9+ EMQ score straight out of the box!
🛡️ Confirmed Purchase Control (Ad Algorithm Anti-Poisoning)
The Competitor Flaw: Conventional tracking plugins (PixelYourSite, Conversios, GTM) prematurely fire the Purchase event the exact millisecond a customer clicks “Place Order”. If an order is a fake Cash-on-Delivery (COD) submission, entered with a wrong phone number, or cancelled an hour later — Meta’s AI algorithm has already marked it as a successful high-value buyer, actively training Meta Advantage+ to find more fake buyers and chronic returners!
CapiFlow Free (Confirmed Purchase Control): CapiFlow does NOT fire Purchase prematurely upon checkout placement. Instead, it holds the event until the store owner verifies the order and marks it as “Confirmed” or “Completed” in WooCommerce. Only 100% real, verified purchases reach Meta Events Manager!
CapiFlow Pro (Courier API Automation): Automatically verifies delivery status in real-time with courier networks (Pathao, Steadfast, REDX, DHL, FedEx) and auto-fires Purchase upon delivery confirmation. If an order is returned or cancelled, it dispatches Negative Purchase Signals to retrain ad algorithms away from chronic returners!
⚡ 0ms Checkout Speed Impact (100% Asynchronous Background Queuing)
Never sacrifice checkout conversion rates for tracking accuracy.
* Non-Blocking Architecture: CapiFlow offloads all server-side CAPI API dispatches to background workers using WordPress Action Scheduler.
* 0ms Latency: Your customers experience instant checkout confirmation with zero API timeout delays, perfectly protecting your Core Web Vitals.
🍪 180-Day Cache-Safe Persistent Server Cookies
Safari ITP & Ad Blocker Immune: While Apple Safari and browser privacy shields wipe JavaScript cookies (document.cookie) within 1 to 7 days, CapiFlow sets first-party HttpOnly server cookies that persist for up to 180 days.
Page-Cache Bypass: Cookies are delivered via uncacheable REST response headers, ensuring 100% functionality even on aggressive caching stacks (LiteSpeed Cache, WP Rocket, Varnish, Cloudflare).
Skyrocket Event Match Quality (EMQ): Matches returning customers months after their first ad click with full SHA-256 hashed customer parameters, achieving 9+ EMQ scores.
Core Features
Direct Server-to-Server Tracking
* 🎯 7 Standard Events Supported: Purchase, InitiateCheckout, AddPaymentInfo, AddToCart, ViewContent, Search, PageView.
* 🔄 Deterministic Deduplication: Browser and server events share the exact same synchronized event_id to guarantee Meta never double-counts conversions.
* 🛡️ First-Party Proxy Endpoint: Client tracking scripts can be routed through your own domain, bypassing ad-blocker domain blocklists.
* 🔐 SHA-256 PII Advanced Matching: Automatically hashes customer email, phone, first name, last name, city, and state before leaving your server.
WooCommerce Control & Monitoring
* 📈 Interactive Dashboard: Real-time event analytics, browser vs. server delivery ratios, and conversion trends.
* 🔍 Live Debug Console: Inspect exact server payloads, timestamp logs, and Meta Graph API response codes.
* 🏥 System Health Inspector: Instant verification of Meta Access Token validity, queue backlog, and cURL connectivity.
* 📞 Checkout Phone Validator: Automatically cleans and validates customer phone formatting at checkout.
* 📋 Order Column Badges: Per-order CAPI dispatch status badges directly inside the WooCommerce Orders screen.
Free vs Pro Comparison
Feature
CapiFlow Free
CapiFlow Pro
100% Self-Hosted (Zero Monthly Cloud Fees)
✅ Yes
✅ Yes
Meta Conversions API (CAPI) Core Events
✅ Yes
✅ Yes (All + Custom)
Multi-Platform Support (GA4, Google Ads, TikTok, Pinterest…)
Meta CAPI Only
✅ All 8 Platforms
Browser & Server Event Deduplication (event_id)
✅ Yes
✅ Yes
Purchase Event Firing Logic
Manual Confirmed Purchase Control
✅ Fully Automated via Courier APIs
Negative Purchase Signals (Ad Budget Optimization)
❌ No
✅ Yes (Automated on Returns)
0ms Async Background Queuing
✅ Yes
✅ Yes
Cache-Safe 180-Day Persistent Server Cookies
✅ Yes
✅ Yes
Category-Based Multi-Pixel Routing
❌ No
✅ Yes
3-Layer AI Fraud Defense & Phone OTP Verification
❌ No
✅ Yes (Full Suite)
Multi-Carrier Courier Auto-Booking (Pathao, Steadfast, DHL…)
❌ No
✅ Yes
Smart Cart Recovery with Dynamic Single-Use Auto-Coupons
❌ No
✅ Yes (SMS + Email)
CapiFlow Pro
Ready to automate your entire post-purchase pipeline? CapiFlow Pro upgrades your store into an automated powerhouse:
* 8-Platform Multi-CAPI: Track Meta, Google Analytics 4, Google Ads Enhanced Conversions, TikTok, Pinterest, Snapchat, LinkedIn, and X.
* Automated Courier Logistics: 1-click booking and real-time delivery status syncing with Pathao, Steadfast, REDX, DHL, FedEx, and custom webhooks.
* Negative Purchase Signals: Automatically signal ad platforms when orders are cancelled or returned to reduce your Cost Per Acquisition (CPA) by 20%–40%.
* Smart Cart Recovery & Dynamic Coupons: Recovers abandoned checkout drafts with single-use, time-limited auto-coupons sent via SMS & Email.
* 3-Layer AI Fraud Guard: Delivery success rate prediction and phone OTP verification to stop fake buyers before shipment.
Learn more on the CapiFlow Pro Website.
Compatibility
Payment Gateways: bKash, Nagad, Rocket, SSLCommerz, Stripe, PayPal, COD (Cash on Delivery), and all standard WooCommerce gateways.
Themes: 100% compatible with Classic themes, Block themes (FSE), Elementor, Divi, Bricks, and custom WooCommerce templates.
Storage Engines: Full native support for High-Performance Order Storage (HPOS) and legacy custom post types.
Consent Management Platforms (CMP): Seamless integration with CookieYes, Complianz, CookieBot, and custom hooks (capiflow_has_tracking_consent).
Requirements
WordPress 6.0+
WooCommerce 7.0+
PHP 7.4+ (PHP 8.0, 8.1, 8.2, 8.3 fully supported)
OpenSSL PHP extension
Meta Pixel ID & System User Access Token
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:
Hashed email, phone, first and last name (SHA-256)
Client IP address and Browser User Agent
Meta Click ID (_fbc) and Browser ID (_fbp) cookies
Order total, currency, and event metadata
All personal data is SHA-256 hashed before transmission.
Meta Terms of Service
Meta Privacy Policy
Meta Platform Terms
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.
Meta Terms of Service
Meta Privacy Policy
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.
All cookies are first-party and contain no personally identifiable information.
Data Storage
{prefix}_capiflow_events — Queued/sent event payloads. Auto-purged after delivery.
{prefix}_capiflow_analytics — Daily aggregated analytics. Auto-purged by retention settings.
Order metadata with _capiflow_ prefix. Removed on uninstall if “Keep Data” is disabled.
Logs in wp-content/uploads/capiflow-logs/ with .htaccess protection. Auto-cleaned daily.
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.
