
PIXELFLOW
PixelFlow compatibility with REEID Translate
PixelFlow compatibility with REEID Translate is being evaluated from available plugin evidence. Implements Meta Conversions API (CAPI) for WooCommerce to send conversion/event data from the server to Meta No specific visitor-facing translation surface is currently confirmed.
AWAITING VERIFICATION
What the available evidence establishes for PixelFlow.
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
PixelFlow is documented in the Analytics category with 7 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 PixelFlow 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
- Implements Meta Conversions API (CAPI) for WooCommerce to send conversion/event data from the server to Meta
- Automatically tracks WooCommerce e-commerce events: Add to Cart (product name, price, quantity), Initiate Checkout (cart totals), and Purchase (full order data including revenue)
- Works alongside an existing Meta Pixel and performs deduplication so Meta does not count events twice
- Provides real-time event monitoring via a dashboard/event log showing events sent to Meta and delivery status/errors
- Supports configuration options to exclude free products from tracking and to exclude admins/specific user roles
- Includes settings to control which events fire and when
- Can be configured to fire events only after consent is given (GDPR/CCPA context) and is described as working with popular consent plugins
CONTENT BOUNDARY
PixelFlow 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
PixelFlow and REEID Translate FAQ.
What does PixelFlow do according to the available plugin evidence?
PixelFlow has 7 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 PixelFlow?
No specific visitor-facing content values are currently confirmed as an evidence-backed translation surface for this integration.
What would establish translation scope for PixelFlow?
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 PixelFlow in a multilingual WordPress workflow.
REEID documents PixelFlow 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.