TRACKING FOR DIVI
Tracking for Divi compatibility with REEID Translate
Tracking for Divi compatibility with REEID Translate is being evaluated from available plugin evidence. Tracks successful Divi contact form submissions by monitoring network communication rather than relying on native JavaScript events. No specific visitor-facing translation surface is currently confirmed.
AWAITING VERIFICATION
What the available evidence establishes for Tracking for Divi.
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
Tracking for Divi 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 Tracking for Divi 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
- Tracks successful Divi contact form submissions by monitoring network communication rather than relying on native JavaScript events.
- Pushes structured dataLayer events containing form ID, post ID, and submitted field data for Google Tag Manager integration.
- Sends direct Google Analytics 4 events via gtag.js with flattened parameters including name, email, and message fields.
- Reports Google Ads conversions using gtag.js when specific conversion IDs and labels are configured.
- Provides settings to customize the dataLayer variable name and event names independently for dataLayer and gtag implementations.
- Includes an optional setting to capture and flatten all form fields into the analytics event payload.
CONTENT BOUNDARY
Tracking for Divi 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
Tracking for Divi and REEID Translate FAQ.
What does Tracking for Divi do according to the available plugin evidence?
Tracking for Divi 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 Tracking for Divi?
No specific visitor-facing content values are currently confirmed as an evidence-backed translation surface for this integration.
What would establish translation scope for Tracking for Divi?
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 Tracking for Divi in a multilingual WordPress workflow.
REEID documents Tracking for Divi 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.