
RELEVA.AI INTEGRATION
Releva.ai Integration compatibility with REEID Translate
Releva.ai Integration compatibility with REEID Translate is being evaluated from available plugin evidence. Loads a Releva JavaScript SDK from Releva.ai external servers on storefront pages to collect page view and user interaction events. No specific visitor-facing translation surface is currently confirmed.
AWAITING VERIFICATION
What the available evidence establishes for Releva.ai Integration.
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
Releva.ai Integration 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 Releva.ai Integration 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
- Loads a Releva JavaScript SDK from Releva.ai external servers on storefront pages to collect page view and user interaction events.
- Sends WooCommerce product catalog data to Releva.ai during a catalog sync process.
- Sends cart and order data to Releva.ai for personalization purposes (after configuration).
- Provides a REST API endpoint that Releva.ai calls to fetch the WooCommerce product catalog, including prices (including tax), images, categories, tags, custom taxonomies, and meta fields.
- Supports custom event tracking via frontend and API (as stated in the plugin description).
- Implements GDPR-oriented consent management via custom consent management (as stated in the plugin description).
- Requires configuration with Releva.ai account credentials (access token, secret key, and page tokens) before any data is sent to Releva.ai servers.
CONTENT BOUNDARY
Releva.ai Integration 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
Releva.ai Integration and REEID Translate FAQ.
What does Releva.ai Integration do according to the available plugin evidence?
Releva.ai Integration 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 Releva.ai Integration?
No specific visitor-facing content values are currently confirmed as an evidence-backed translation surface for this integration.
What would establish translation scope for Releva.ai Integration?
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 Releva.ai Integration in a multilingual WordPress workflow.
REEID documents Releva.ai Integration 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.