WILDROCK
WildRock compatibility with REEID Translate
WildRock compatibility with REEID Translate is being evaluated from available plugin evidence. WooCommerce AI search via an embeddable storefront widget that sends shopper search queries to WildRock cloud endpoints and returns results No specific visitor-facing translation surface is currently confirmed.
AWAITING VERIFICATION
What the available evidence establishes for WildRock.
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
WildRock 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 WildRock 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
- WooCommerce AI search via an embeddable storefront widget that sends shopper search queries to WildRock cloud endpoints and returns results
- Catalog synchronization to the WildRock API (triggered by pressing “Sync” and automatically when products change), sending product data such as title/description/price/stock/images/categories
- Search attribution reporting to WildRock cloud when an order is placed using the search, sending order id, order total, and an anonymous session pseudonym (no names/emails)
- Optional analytics integration (“WildRock Insights”) that is disabled by default and requires an explicit consent checkbox in WooCommerce → WildRock
- When analytics is enabled, the plugin sends order/cart/visit events to a WildRock Insights ingest endpoint, including personal data fields listed in the readme (e.g., billing/shipping name, email, phone, address, IP for orders; email/name/phone for carts; page visited plus an anonymous session id for visits)
- Analytics event types (orders, carts, visits) can be turned off individually once enabled
CONTENT BOUNDARY
WildRock 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
WildRock and REEID Translate FAQ.
What does WildRock do according to the available plugin evidence?
WildRock 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 WildRock?
No specific visitor-facing content values are currently confirmed as an evidence-backed translation surface for this integration.
What would establish translation scope for WildRock?
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 WildRock in a multilingual WordPress workflow.
REEID documents WildRock 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.