LEAD RECORDER
Lead Recorder compatibility with REEID Translate
Lead Recorder compatibility with REEID Translate is being evaluated from available plugin evidence. Injects a single deferred JavaScript tracking snippet on every page view when a valid tracking key is configured No specific visitor-facing translation surface is currently confirmed.
AWAITING VERIFICATION
What the available evidence establishes for Lead Recorder.
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
Lead Recorder 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 Lead Recorder 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
- Injects a single deferred JavaScript tracking snippet on every page view when a valid tracking key is configured
- Records lead events including phone number clicks, form submissions, booking/calendar link clicks, and email address clicks
- Attributes each recorded lead to its source traffic channel such as Google Ads, organic search, referral, social, or direct
- Captures the visitor's page journey history prior to each enquiry event for context
- Operates without setting cookies, eliminating consent banner requirements for the plugin's own data collection
- Connects to Lead Recorder external services only after an administrator enters a tracking key in settings
CONTENT BOUNDARY
Lead Recorder 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
Lead Recorder and REEID Translate FAQ.
What does Lead Recorder do according to the available plugin evidence?
Lead Recorder 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 Lead Recorder?
No specific visitor-facing content values are currently confirmed as an evidence-backed translation surface for this integration.
What would establish translation scope for Lead Recorder?
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 Lead Recorder in a multilingual WordPress workflow.
REEID documents Lead Recorder 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.