OPINLY
Opinly compatibility with REEID Translate
Opinly compatibility with REEID Translate is being evaluated from available plugin evidence. Tracks anonymous visitor analytics and traffic-source attribution (e.g., referrer, UTM tags, ad click ids) on page views. No specific visitor-facing translation surface is currently confirmed.
AWAITING VERIFICATION
What the available evidence establishes for Opinly.
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
Opinly 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 Opinly 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
- Tracks anonymous visitor analytics and traffic-source attribution (e.g., referrer, UTM tags, ad click ids) on page views.
- Records conversions as either completed WooCommerce orders (order total and currency) or form submissions (forms can be marked as conversions in the Opinly dashboard).
- Loads a tracker script as a normal WordPress script (no theme edits; no tracking snippet to paste) and sends analytics data to the Opinly API.
- Implements consent handling by registering with the WordPress Consent API and following an active consent plugin’s decision for the “statistics” category; otherwise uses an on-by-default setting that can be turned off.
- Generates a random anonymous visitor id stored in the browser and uses it to associate events and purchases with the visitor.
- For WooCommerce, records purchases on the order-received page and also sends a signed server-side webhook on order completion; matches by order id to avoid double-counting.
- Supports email-based conversion identification/crediting: if a submitted form contains an email, the email is sent to Opinly (only field names/that a submission occurred are sent otherwise); for WooCommerce purchases, the buyer’s email is sent from the server for attribution.
CONTENT BOUNDARY
Opinly 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
Opinly and REEID Translate FAQ.
What does Opinly do according to the available plugin evidence?
Opinly 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 Opinly?
No specific visitor-facing content values are currently confirmed as an evidence-backed translation surface for this integration.
What would establish translation scope for Opinly?
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 Opinly in a multilingual WordPress workflow.
REEID documents Opinly 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.