OCTANIST
Octanist compatibility with REEID Translate
Octanist compatibility with REEID Translate is being evaluated from available plugin evidence. First-party pixel proxy: serves the Octanist tracking script from the WordPress site at `/wp-json/oct/p`, using a local cache refreshed from Octanist in the background. No specific visitor-facing translation surface is currently confirmed.
AWAITING VERIFICATION
What the available evidence establishes for Octanist.
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
Octanist 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 Octanist 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
- First-party pixel proxy: serves the Octanist tracking script from the WordPress site at `/wp-json/oct/p`, using a local cache refreshed from Octanist in the background.
- Event proxy endpoint: receives pixel events via POST to `/wp-json/oct/e` and forwards them upstream with a short (one-second) timeout; upstream failures are not persisted in WordPress.
- Call tracking proxy: supports dynamic phone number assignment via `/wp-json/oct/call-tracking/assign`, forwarding the request to Octanist so numbers remain first-party.
- Server-side form submission capture for multiple form plugins (Gravity Forms, Contact Form 7, WPForms, Ninja Forms, Elementor Pro, Fluent Forms, Formidable Forms, Forminator, SureForms, Divi Contact Form) using action hooks rather than browser interception.
- Form forwarding behavior and resilience: forwards form submissions synchronously with a longer timeout; confirmed failures are queued for retry with backoff via WP-Cron.
- Optional toggles for listener mode and consent mode (as stated in the plugin description).
CONTENT BOUNDARY
Octanist 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
Octanist and REEID Translate FAQ.
What does Octanist do according to the available plugin evidence?
Octanist 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 Octanist?
No specific visitor-facing content values are currently confirmed as an evidence-backed translation surface for this integration.
What would establish translation scope for Octanist?
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 Octanist in a multilingual WordPress workflow.
REEID documents Octanist 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.