
PIWIK PRO
Piwik PRO compatibility with REEID Translate
Piwik PRO compatibility with REEID Translate is being evaluated from available plugin evidence. Adds a Piwik PRO Analytics Suite container (tracking code) to a WordPress site via the plugin’s configured Container address and Site ID settings. No specific visitor-facing translation surface is currently confirmed.
AWAITING VERIFICATION
What the available evidence establishes for Piwik PRO.
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
Piwik PRO 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 Piwik PRO 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
- Adds a Piwik PRO Analytics Suite container (tracking code) to a WordPress site via the plugin’s configured Container address and Site ID settings.
- Provides an option to leave “Basic container (async)” checked, described as the container that holds tracking code and is used to handle most tags.
- Automatically tracks WooCommerce ecommerce events such as ecommerce orders and abandoned carts, enabling ecommerce reporting in Piwik PRO when ecommerce reports are enabled in the Piwik PRO admin UI.
- Supports consent management by allowing consents to be managed and data collection to occur only when specific consent is received (via Consent Manager integration in the platform).
- Supports tag management by enabling creation/testing/deployment of tags (including coordination with Analytics, Customer Data Platform, and Consent Manager) through the Piwik PRO platform.
- Can integrate with WordPress multisite either at the site level (load on that site only) or at the network level (integration with all sites in the network).
CONTENT BOUNDARY
Piwik PRO 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
Piwik PRO and REEID Translate FAQ.
What does Piwik PRO do according to the available plugin evidence?
Piwik PRO 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 Piwik PRO?
No specific visitor-facing content values are currently confirmed as an evidence-backed translation surface for this integration.
What would establish translation scope for Piwik PRO?
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 Piwik PRO in a multilingual WordPress workflow.
REEID documents Piwik PRO 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.