LOCALIQ
LocaliQ – Tracking Code compatibility with REEID Translate
LocaliQ – Tracking Code compatibility with REEID Translate is being evaluated using available plugin evidence. Injection of required JavaScript tracking code on all site pages via a CDN-hosted script (mms.js) No specific visitor-facing text is currently confirmed for translation.
AWAITING VERIFICATION
What the available evidence establishes for LocaliQ – Tracking Code.
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
LocaliQ – Tracking Code is documented in the Analytics category with 5 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 LocaliQ – Tracking Code 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
Do not treat structure, configuration, logic, integrations or runtime behaviour as translatable content unless specific human-readable text is identified.
04 · Confirm what can be translated
Publish supported content only when specific visitor-facing text has been identified and can be validated.
PLUGIN INFORMATION
What the plugin officially supports
Plugin capabilities
- Injection of required JavaScript tracking code on all site pages via a CDN-hosted script (mms.js)
- Collection and transmission of analytics data, visit metrics, and referrer attribution to LocaliQ servers
- Capture and transmission of lead management data including visits, emails, and form submissions
- Replacement of email links with contact forms, offloading form data processing and email sending to LocaliQ infrastructure
- Dynamic configuration loading from LocaliQ via capture_configs JS to support ongoing feature updates without plugin version changes
CONTENT BOUNDARY
LocaliQ – Tracking Code capabilities and translatable content are documented separately.
The available evidence documents plugin functionality, but does not currently identify specific visitor-facing text that can be translated.
Functional capability alone is not treated as evidence that a value should be translated.
LIMITATIONS & QA
Verification notes
- This integration is documented for compatibility. No specific content shown to visitors is confirmed for translation in this category.
COMMON QUESTIONS
LocaliQ – Tracking Code and REEID Translate FAQ.
What does LocaliQ – Tracking Code do according to the available plugin evidence?
LocaliQ – Tracking Code has 5 concrete capabilities documented from the currently available official plugin evidence. See the Plugin Intelligence section for the individual capabilities.
Does LocaliQ – Tracking Code currently have any visitor-facing content confirmed for translation?
No specific visitor-facing text is currently confirmed for translation in this integration.
What evidence is needed to confirm translatable content for LocaliQ – Tracking Code?
The evidence must identify specific visitor-facing text, such as labels, titles, descriptions or messages, that can be validated through the integration workflow.
RELATED GUIDES
Continue through the compatibility library.
INTEGRATION EVIDENCE
Evaluate LocaliQ – Tracking Code in a multilingual WordPress workflow.
REEID documents LocaliQ – Tracking Code functionality separately from evidence-backed translation support so compatibility claims remain specific and testable.
Supported translatable content will be published when specific visitor-facing text is confirmed by evidence.