PIXLINT
Pixlint – Multi-Platform Pixel Tracking & Server-Side Conversions API (CAPI) for WooCommerce compatibility with REEID Translate
Pixlint – Multi-Platform Pixel Tracking & Server-Side Conversions API (CAPI) for WooCommerce compatibility with REEID Translate is being evaluated from available plugin evidence. Dual-channel tracking for WooCommerce: client-side browser pixels plus server-side Conversions/Measurement Protocol-style event dispatch with shared `event_id` for deduplication. No specific visitor-facing translation surface is currently confirmed.
Visit Pixlint – Multi-Platform Pixel Tracking & Server-Side Conversions API (CAPI) for WooCommerce ↗
AWAITING VERIFICATION
What the available evidence establishes for Pixlint – Multi-Platform Pixel Tracking & Server-Side Conversions API (CAPI) 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
Pixlint – Multi-Platform Pixel Tracking & Server-Side Conversions API (CAPI) for WooCommerce 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 Pixlint – Multi-Platform Pixel Tracking & Server-Side Conversions API (CAPI) 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
- Dual-channel tracking for WooCommerce: client-side browser pixels plus server-side Conversions/Measurement Protocol-style event dispatch with shared `event_id` for deduplication.
- Meta (Facebook) Pixel integration including browser-side `fbevents.js` loading and “ fallback image rendering, plus server-side Meta Conversions API event transmission to `graph.facebook.com`.
- Google Analytics 4 integration including client-side `gtag.js` loading and server-side Measurement Protocol event transmission to `google-analytics.com/mp/collect`, with support for GA4 e-commerce parameters (e.g., `transaction_id`, `value`, `currency`, `items`).
- WooCommerce event coverage for standard ecommerce lifecycle events (e.g., PageView/view_item, view_item_list, view_search_results, add_to_cart/begin_checkout, purchase) and additional engagement/lead events (e.g., Contact link clicks and form submission detection).
- Asynchronous/non-blocking server-side dispatch for CAPI/Measurement Protocol requests (described as using `wp_remote_post(…, blocking => false)`), intended to avoid checkout/page-load delays.
- User privacy/role-based exclusions described as preventing tracking for certain roles (e.g., Administrators/Shop Managers) to reduce analytics skew.
- Compatibility claims for WooCommerce High-Performance Order Storage (HPOS) and modern Block/Cart checkout flows, plus declared compatibility with caching plugins via dynamic tracking-code output and AJAX event handling.
CONTENT BOUNDARY
Pixlint – Multi-Platform Pixel Tracking & Server-Side Conversions API (CAPI) 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
Pixlint – Multi-Platform Pixel Tracking & Server-Side Conversions API (CAPI) for WooCommerce and REEID Translate FAQ.
What does Pixlint – Multi-Platform Pixel Tracking & Server-Side Conversions API (CAPI) for WooCommerce do according to the available plugin evidence?
Pixlint – Multi-Platform Pixel Tracking & Server-Side Conversions API (CAPI) for WooCommerce 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 Pixlint – Multi-Platform Pixel Tracking & Server-Side Conversions API (CAPI) 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 Pixlint – Multi-Platform Pixel Tracking & Server-Side Conversions API (CAPI) 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 Pixlint – Multi-Platform Pixel Tracking & Server-Side Conversions API (CAPI) for WooCommerce in a multilingual WordPress workflow.
REEID documents Pixlint – Multi-Platform Pixel Tracking & Server-Side Conversions API (CAPI) 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.