TALKE CRM
Talke CRM compatibility with REEID Translate
Talke CRM compatibility with REEID Translate is being evaluated from available plugin evidence. Installs a tracking script on every page load by loading `tracker.js` from `https://crm.talke.com.br/tracker.js`. No specific visitor-facing translation surface is currently confirmed.
AWAITING VERIFICATION
What the available evidence establishes for Talke CRM.
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
Talke CRM 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 Talke CRM 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
- Installs a tracking script on every page load by loading `tracker.js` from `https://crm.talke.com.br/tracker.js`.
- Sends page view events on every page load to `https://crm.talke.com.br/api/pageview`, including page URL/title, referrer, UTM/ad-click parameters (e.g., `utm_source`, `utm_medium`, `gclid`, `fbclid`), plus technical data (IP address and browser user agent) to identify the session.
- Captures leads by sending submitted form/order data to `https://crm.talke.com.br/api/capture`, including visitor-provided fields (e.g., name, email, phone and other form fields) along with attribution parameters.
- Supports native capture of Elementor Pro form submissions.
- Supports capture of new WooCommerce orders and customer registrations.
- Provides an OAuth-like connection flow (“Connect with Talke CRM”) so site owners authorize the connection without manually copying tokens.
- Can inject the tracker even when Elementor and WooCommerce are not present, relying on JavaScript auto-detection to capture leads.
CONTENT BOUNDARY
Talke CRM 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
Talke CRM and REEID Translate FAQ.
What does Talke CRM do according to the available plugin evidence?
Talke CRM 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 Talke CRM?
No specific visitor-facing content values are currently confirmed as an evidence-backed translation surface for this integration.
What would establish translation scope for Talke CRM?
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 Talke CRM in a multilingual WordPress workflow.
REEID documents Talke CRM 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.