METRION
Metrion compatibility with REEID Translate
Metrion compatibility with REEID Translate is being evaluated from available plugin evidence. Frontend and server-side event brokering (described as “Front-end event brokering” and “Server-side event brokering”). No specific visitor-facing translation surface is currently confirmed.
AWAITING VERIFICATION
What the available evidence establishes for Metrion.
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
Metrion is documented in the Analytics category with 6 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 Metrion 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
- Frontend and server-side event brokering (described as “Front-end event brokering” and “Server-side event brokering”).
- Optional consent-related behavior to avoid storing data in cookies/browser storage before explicit consent, plus event floodgating to prevent tracking before proper consent is given.
- Consent Management Platform (CMP) integration support (explicitly listed as “Consent Management Platform integrations”).
- Conversion tracking integrations for major ad platforms, including Google Ads conversion tracking (and enhanced conversion tracking/lead tracking via Google Ads API), Meta Ads pixel and Conversion API integration, and Microsoft Ads conversion tracking/enhancement via conversion uploading.
- Google Analytics 4 server-side tracking capability (listed as “Google Analytics 4 sever-side”).
- Additional ad-platform conversion tracking/integration support including TikTok Ads conversion tracking and TikTok Ads Conversion API integration; also includes Google dynamic remarketing tracking for retail vertical and Meta Ads Advantage+ catalog ads tracking (as listed).
Distinctive features
First-party/server-side tracking of a fixed set of ecommerce and lead interactions (e.g., visit, page view, product view/list view, search results, add to cart, cart view, checkout start, purchase, purchase cancellations, and user engagements such as clicks/form engagements/browser engagements). Frontend and server-side event brokering (described as “Front-end event brokering” and “Server-side event brokering”). Optional consent-related behavior to avoid storing data in cookies/browser storage before explicit consent, plus event floodgating to prevent tracking before proper consent is given. Consent Management Platform (CMP) integration support (explicitly listed as “Consent Management Platform integrations”). Conversion tracking integrations for major ad platforms, including Google Ads conversion tracking (and enhanced conversion tracking/lead tracking via Google Ads API), Meta Ads pixel and Conversion API integration, and Microsoft Ads conversion tracking/enhancement via conversion uploading. Google Analytics 4 server-side tracking capability (listed as “Google Analytics 4 sever-side”). Additional ad-platform conversion tracking/integration support including TikTok Ads conversion tracking and TikTok Ads Conversion API integration; also includes Google dynamic remarketing tracking for retail vertical and Meta Ads Advantage+ catalog ads tracking (as listed).
CONTENT BOUNDARY
Metrion 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
Metrion and REEID Translate FAQ.
What does Metrion do according to the available plugin evidence?
Metrion has 6 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 Metrion?
No specific visitor-facing content values are currently confirmed as an evidence-backed translation surface for this integration.
What would establish translation scope for Metrion?
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 Metrion in a multilingual WordPress workflow.
REEID documents Metrion 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.