ITERACTIVE AI SITE SYNC AND PUBLISHING
Iteractive AI Site Sync and Publishing compatibility with REEID Translate
Iteractive AI Site Sync and Publishing compatibility with REEID Translate is being evaluated from available plugin evidence. Site-wide injection of Meta Pixel and Google Tag (GA4/GTM) scripts based on configured Pixel/Tag IDs stored in WordPress options. No specific visitor-facing translation surface is currently confirmed.
AWAITING VERIFICATION
What the available evidence establishes for Iteractive AI Site Sync and Publishing.
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
Iteractive AI Site Sync and Publishing 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 Iteractive AI Site Sync and Publishing 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
- Site-wide injection of Meta Pixel and Google Tag (GA4/GTM) scripts based on configured Pixel/Tag IDs stored in WordPress options.
- REST API pairing protection via a small signed REST namespace (`iteractive/v1`) that only accepts requests carrying a random secret token generated during pairing.
- WooCommerce product mirroring/sync into iteractive.ai for ad-creative generation (requires WooCommerce for product sync).
- Manual sync workflow: plugin sends data to the iteractive.ai backend only when the user clicks Connect (pairing) or triggers a manual sync action from the iteractive.ai dashboard; no automatic background calls.
- Visitor tracking behavior is delegated to standard Meta/Google scripts: when configured, the visitor’s browser loads `fbevents.js` and sends a standard PageView to `facebook.com/tr`, and loads `gtag/js` and sends a standard page view to Google; if IDs are not configured, no requests are made.
- Plugin-side data handling scope: plugin stores a paired secret, iteractive.ai user ID, Meta Pixel ID, and Google Tag ID in `wp_options`, and the plugin itself does not collect or transmit visitor data.
CONTENT BOUNDARY
Iteractive AI Site Sync and Publishing 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
Iteractive AI Site Sync and Publishing and REEID Translate FAQ.
What does Iteractive AI Site Sync and Publishing do according to the available plugin evidence?
Iteractive AI Site Sync and Publishing 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 Iteractive AI Site Sync and Publishing?
No specific visitor-facing content values are currently confirmed as an evidence-backed translation surface for this integration.
What would establish translation scope for Iteractive AI Site Sync and Publishing?
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 Iteractive AI Site Sync and Publishing in a multilingual WordPress workflow.
REEID documents Iteractive AI Site Sync and Publishing 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.