CAPIFLOW
CapiFlow – Conversions API (CAPI) Tracking for WooCommerce compatibility with REEID Translate
CapiFlow – Conversions API (CAPI) Tracking for WooCommerce compatibility with REEID Translate is being evaluated from available plugin evidence. Server-side delivery of WooCommerce events to Meta Conversions API (CAPI) using a configured Meta Pixel ID and Access Token. No specific visitor-facing translation surface is currently confirmed.
Visit CapiFlow – Conversions API (CAPI) Tracking for WooCommerce ↗
AWAITING VERIFICATION
What the available evidence establishes for CapiFlow – Conversions API (CAPI) Tracking for WooCommerce.
Official plugin information supports the compatibility context documented for this category.
AWAITING VERIFICATION
This integration has not yet been manually verified by REEID.
PLUGIN PROFILE
CapiFlow – Conversions API (CAPI) Tracking for WooCommerce is documented in the Analytics category with 8 concrete capabilities identified in the current evidence.
EVIDENCE COVERAGE
Plugin capabilities are documented from available official evidence. Translation support is listed only when concrete visitor-facing content is explicitly established.
COMPATIBILITY REVIEW
How CapiFlow – Conversions API (CAPI) Tracking for WooCommerce compatibility is evaluated
01 · Review official plugin evidence
Establish documented plugin behaviour before making any multilingual compatibility claim.
02 · Identify visitor-facing content
Determine whether the documented behaviour exposes human-readable values that visitors can see.
03 · Separate content from functionality
Keep structure, configuration, logic, integrations and runtime behaviour outside translation scope unless concrete content values are identified.
04 · Confirm translation scope
Publish supported content only when concrete visitor-facing values are explicitly established and can be validated.
PLUGIN INTELLIGENCE
What the official plugin evidence shows
Plugin capabilities
- Server-side delivery of WooCommerce events to Meta Conversions API (CAPI) using a configured Meta Pixel ID and Access Token.
- Supports 7 standard WooCommerce-to-CAPI event types: Purchase, InitiateCheckout, AddPaymentInfo, AddToCart, ViewContent, Search, and PageView.
- Implements Meta deduplication by sending browser and server events with a shared `event_id`.
- Performs SHA-256 hashing of personal data (email, phone, name) before transmitting server-side events; also transmits client IP and browser user agent.
- Loads the Meta Pixel JavaScript SDK on the frontend when a Pixel ID is configured (hosted by Meta at `connect.facebook.net`).
- Provides analytics/monitoring components including a dashboard, debug console (payloads and Meta API responses), system health checks, and cart monitoring/abandoned cart summary.
- Implements consent gating via a “Consent Enforcement” setting and a `capiflow_has_tracking_consent` filter hook to block browser and server events until CMP consent is detected.
- Uses an async delivery mechanism via WooCommerce Action Scheduler queue with retry logic for event delivery.
CONTENT BOUNDARY
CapiFlow – Conversions API (CAPI) Tracking for WooCommerce capabilities and translation scope are documented separately.
The available evidence documents plugin functionality, but does not currently establish a specific visitor-facing translation surface.
Functional capability alone is not treated as evidence that a value should be translated.
LIMITATIONS & QA
Verification notes
- This integration is documented for compatibility context. Visitor-facing translation scope is not listed for this category.
COMMON QUESTIONS
CapiFlow – Conversions API (CAPI) Tracking for WooCommerce and REEID Translate FAQ.
What does CapiFlow – Conversions API (CAPI) Tracking for WooCommerce do according to the available plugin evidence?
CapiFlow – Conversions API (CAPI) Tracking for WooCommerce has 8 concrete capabilities documented from the currently available official plugin evidence. See the Plugin Intelligence section for the individual capabilities.
Is a REEID translation surface currently confirmed for CapiFlow – Conversions API (CAPI) Tracking for WooCommerce?
No specific visitor-facing content values are currently confirmed as an evidence-backed translation surface for this integration.
What would establish translation scope for CapiFlow – Conversions API (CAPI) Tracking for WooCommerce?
The evidence must identify concrete visitor-facing values such as labels, titles, descriptions, messages or other human-readable content that can be validated through the integration workflow.
RELATED GUIDES
Continue through the compatibility library.
INTEGRATION EVIDENCE
Evaluate CapiFlow – Conversions API (CAPI) Tracking for WooCommerce in a multilingual WordPress workflow.
REEID documents CapiFlow – Conversions API (CAPI) Tracking for WooCommerce functionality separately from evidence-backed translation support so compatibility claims remain specific and testable.
Translation scope will be published when concrete visitor-facing content is established by evidence.