PIXLINT
Pixlint – Multi-Platform Pixel Tracking & Server-Side Conversions API (CAPI) for WooCommerce translation compatibility with REEID Translate — evidence review.
Official plugin evidence describes what Pixlint – Multi-Platform Pixel Tracking & Server-Side Conversions API (CAPI) for WooCommerce does, but does not yet establish specific visitor-facing content values that REEID should translate.
Visit Pixlint – Multi-Platform Pixel Tracking & Server-Side Conversions API (CAPI) for WooCommerce ↗
AWAITING VERIFICATION
Translation scope is not yet established.
Plugin capabilities can be documented without treating structure, behavior, configuration or feature availability as translatable content.
AWAITING VERIFICATION
This integration has not yet been manually verified by REEID.
TRANSLATION SCOPE
No specific visitor-facing content values are currently approved for translation scope.
PLUGIN EVIDENCE
Plugin capabilities and distinctive features are documented separately from REEID translation support.
PRACTICAL WORKFLOW
Translation workflow
01 · Review official plugin evidence
Document factual capabilities, content models and relevant plugin behavior from the available evidence.
02 · Identify concrete visitor-facing values
Look for explicit labels, titles, descriptions, messages, placeholders or other human-readable content values.
03 · Approve translation scope
Only evidence-backed visitor-facing values become supported translation scope for the integration record.
04 · Test confirmed integration behavior
Validate approved content and plugin behavior before publishing compatibility claims.
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.
Distinctive features
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.
Dynamic content
Dynamic or runtime content behavior remains limited to what is explicitly documented in the official plugin evidence.
SEO and metadata
SEO and metadata behavior is documented only where it is explicitly established by official plugin information.
URLs and navigation
URL and navigation behavior remains outside translation scope unless explicitly represented by the integration category.
Forms and commerce
Forms and commerce behavior is limited to factual capabilities documented for this plugin.
CONTENT BOUNDARY
Keep plugin capabilities separate from translation scope.
Current evidence documents what Pixlint – Multi-Platform Pixel Tracking & Server-Side Conversions API (CAPI) for WooCommerce does, but no specific visitor-facing content values have been approved as translation scope.
Structure, configuration, logic, integrations and runtime behavior are not translation claims.
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.
Does the current evidence establish translation scope for Pixlint – Multi-Platform Pixel Tracking & Server-Side Conversions API (CAPI) for WooCommerce?
No specific visitor-facing content values are currently approved as translation scope for this integration.
What does the plugin intelligence section describe?
It summarizes factual plugin capabilities and distinctive features separately from REEID translation-support claims.
What is required before translation scope is published?
Concrete visitor-facing content values must be supported by evidence, approved for the integration record and tested as appropriate.
RELATED GUIDES
Continue through the compatibility library.
INTEGRATION EVIDENCE
Explore REEID Translate for multilingual WordPress workflows.
REEID separates factual plugin intelligence from evidence-backed translation scope.
No specific visitor-facing content values are currently approved for this integration.