CAPYBARA SEO LEAD SOURCE TRACKER
Capybara SEO Lead Source Tracker compatibility with REEID Translate
Capybara SEO Lead Source Tracker compatibility with REEID Translate is being evaluated from available plugin evidence. Captures URL attribution parameters including UTM fields (utm_source, utm_medium, utm_campaign, utm_content, utm_term) and click IDs (gclid, gbraid, wbraid, fbclid). No specific visitor-facing translation surface is currently confirmed.
AWAITING VERIFICATION
What the available evidence establishes for Capybara SEO Lead Source Tracker.
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
Capybara SEO Lead Source Tracker is documented in the Analytics category with 7 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 Capybara SEO Lead Source Tracker 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
- Captures URL attribution parameters including UTM fields (utm_source, utm_medium, utm_campaign, utm_content, utm_term) and click IDs (gclid, gbraid, wbraid, fbclid).
- Implements first-touch attribution by storing captured lead-source data in browser localStorage and preserving it across page navigation even when later URLs lack UTMs.
- Performs automatic channel detection (e.g., Google Ads, Meta Ads, Organic, Referral) and exposes the detected channel via a template placeholder.
- Updates WhatsApp links/messages by injecting a dynamic message that includes captured lead-source data; message lines whose placeholders have no captured value are omitted.
- Supports click-time page tracking by reporting the complete URL where the visitor clicks (including query string and fragment) via placeholders {exit_page} (and legacy {landing_page} which returns the same click-time URL).
- Provides frontend debug logging by logging captured data to the browser console when debug mode is enabled.
- Injects WhatsApp tracking into the UI via multiple placements: an auto-injected floating button, a CSS-selector-based update of existing buttons, and an always-available [capysele_button] shortcode; these placements share the same tracking data.
CONTENT BOUNDARY
Capybara SEO Lead Source Tracker 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
Capybara SEO Lead Source Tracker and REEID Translate FAQ.
What does Capybara SEO Lead Source Tracker do according to the available plugin evidence?
Capybara SEO Lead Source Tracker has 7 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 Capybara SEO Lead Source Tracker?
No specific visitor-facing content values are currently confirmed as an evidence-backed translation surface for this integration.
What would establish translation scope for Capybara SEO Lead Source Tracker?
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 Capybara SEO Lead Source Tracker in a multilingual WordPress workflow.
REEID documents Capybara SEO Lead Source Tracker 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.