ASERVA AI CHAT WIDGET
aserva AI Chat Widget | REEID Translate Compatibility
REEID processes supported labels, notices and consent-related text while aserva AI Chat Widget 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 aserva AI Chat Widget.
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 evidence-backed 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
- Asynchronous frontend chat widget script loading (does not block initial page render).
- External data transmission to aserva after configuration with an API key, including widget configuration (organization ID, widget position, color, language).
- Collection and transmission of logged-in customer context when available (e.g., display name and email).
- WooCommerce event tracking and data collection for support workflows, including order events (order identifiers, status, totals/currency, items, product URLs/images, customer contact and address fields).
- WooCommerce refund/return-related event syncing and capture of refund/return requests for review (merchant-controlled approvals not handled automatically).
- Collection of contact form submissions from supported WordPress form plugins, including submitted fields and page URL.
- Signed webhook communication to aserva using HMAC-SHA256 with a timestamp; plugin diagnostics (plugin version, WordPress version, site URL, connection status) are also sent after API-key configuration.
Distinctive features
Asynchronous frontend chat widget script loading (does not block initial page render). External data transmission to aserva after configuration with an API key, including widget configuration (organization ID, widget position, color, language). Collection and transmission of logged-in customer context when available (e.g., display name and email). WooCommerce event tracking and data collection for support workflows, including order events (order identifiers, status, totals/currency, items, product URLs/images, customer contact and address fields). WooCommerce refund/return-related event syncing and capture of refund/return requests for review (merchant-controlled approvals not handled automatically). Collection of contact form submissions from supported WordPress form plugins, including submitted fields and page URL. Signed webhook communication to aserva using HMAC-SHA256 with a timestamp; plugin diagnostics (plugin version, WordPress version, site URL, connection status) are also sent after API-key configuration.
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 aserva AI Chat Widget 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
aserva AI Chat Widget and REEID Translate FAQ.
Does REEID Translate work with aserva AI Chat Widget?
REEID Translate Pro processes the supported visitor-facing fields documented for this integration while aserva AI Chat Widget 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 aserva AI Chat Widget.
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 aserva AI Chat Widget 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.