LEAD FORENSICS
Lead Forensics | REEID Translate Compatibility
REEID processes supported labels, notices and consent-related text while Lead Forensics remains responsible for tracking IDs, events, measurement and analytics data.
AWAITING VERIFICATION
Translate visible text. Preserve measurement logic.
Multilingual visitor-facing wording stays separate from tracking configuration, event definitions and collected analytics data.
AWAITING VERIFICATION
This integration has not yet been manually verified by REEID.
CONTENT BOUNDARY
Translatable content remains separate from plugin-specific functional configuration.
DATA-SAFE
Tracking IDs, events, measurement rules and collected analytics data remain functional configuration.
PRACTICAL WORKFLOW
Translation workflow
01 · Configure analytics normally
Maintain tracking, events and measurement settings through Lead Forensics.
02 · Identify visible analytics text
Locate supported consent labels, notices, embedded labels or other visitor-facing wording.
03 · Translate supported wording
Process multilingual text without altering IDs, event names or measurement configuration.
04 · Validate tracking and frontend text
Review translated wording while confirming analytics collection still behaves as intended.
SUPPORTED CONTENT
Translation scope
Visitor-facing text
Replace this draft item with the exact content coverage.
Interface content
Document supported labels, titles or interface strings where applicable.
Product-specific content
Add confirmed product-specific support before publication.
PLUGIN INTELLIGENCE
What the official plugin evidence shows
Plugin capabilities
- Injects the Lead Forensics tracking code into the head of every page.
- Uses a single settings field for pasting the tracking code from the Lead Forensics portal.
- Does not add async or defer attributes to the injected script.
- Stores only the pasted tracking code snippet in the site’s WordPress database.
- Does not itself collect, transmit, or store user data.
- Supports automatic migration of tracking code from earlier plugin versions.
- Includes validation and migration handling to keep script and noscript content separated.
Distinctive features
Injects the Lead Forensics tracking code into the head of every page. Uses a single settings field for pasting the tracking code from the Lead Forensics portal. Does not add async or defer attributes to the injected script. Stores only the pasted tracking code snippet in the site’s WordPress database. Does not itself collect, transmit, or store user data. Supports automatic migration of tracking code from earlier plugin versions. Includes validation and migration handling to keep script and noscript content separated.
Dynamic content
Dynamic or runtime content behavior remains limited to what is explicitly documented in the official plugin evidence.
SEO and metadata
SEO and metadata behavior is documented only where it is explicitly established by official plugin information.
URLs and navigation
URL and navigation behavior remains outside translation scope unless explicitly represented by the integration category.
Forms and commerce
Forms and commerce behavior is limited to factual capabilities documented for this plugin.
CONTENT BOUNDARY
Separate multilingual wording from analytics data and tracking logic.
REEID handles supported visitor-facing text while Lead Forensics controls tracking configuration, measurement logic and analytics data.
Tracking IDs, event configuration and collected data are not translation content.
LIMITATIONS & QA
Verification notes
- This integration is documented for compatibility context. Visitor-facing translation scope is not listed for this category.
COMMON QUESTIONS
Lead Forensics and REEID Translate FAQ.
Does REEID Translate work with Lead Forensics?
REEID Translate Pro processes the supported visitor-facing fields documented for this integration while Lead Forensics retains control of its own functionality.
Does REEID translate or alter tracking IDs and events?
No. Tracking identifiers, event definitions and measurement rules remain controlled by Lead Forensics.
Can consent or visitor-facing analytics labels be translated?
Yes when those strings are available through supported visitor-facing content paths.
RELATED GUIDES
Continue through the compatibility library.
ANALYTICS INTEGRATION
Translate visitor-facing Lead Forensics text without disturbing analytics.
Keep multilingual wording separate from tracking IDs, events and measurement logic.
Supported content and limitations are defined by the integration record.