EASY SERVER SIDE TRACKING
Easy Server Side Tracking translation compatibility with REEID Translate — evidence review.
Official plugin evidence describes what Easy Server Side Tracking does, but does not yet establish specific visitor-facing content values that REEID should translate.
AWAITING VERIFICATION
Translation scope is not yet established.
Plugin capabilities can be documented without treating structure, behavior, configuration or feature availability as translatable content.
AWAITING VERIFICATION
This integration has not yet been manually verified by REEID.
TRANSLATION SCOPE
No specific visitor-facing content values are currently approved for translation scope.
PLUGIN EVIDENCE
Plugin capabilities and distinctive features are documented separately from REEID translation support.
PRACTICAL WORKFLOW
Translation workflow
01 · Review official plugin evidence
Document factual capabilities, content models and relevant plugin behavior from the available evidence.
02 · Identify concrete visitor-facing values
Look for explicit labels, titles, descriptions, messages, placeholders or other human-readable content values.
03 · Approve translation scope
Only evidence-backed visitor-facing values become supported translation scope for the integration record.
04 · Test confirmed integration behavior
Validate approved content and plugin behavior before publishing compatibility claims.
PLUGIN INTELLIGENCE
What the official plugin evidence shows
Plugin capabilities
- Server-side forwarding of analytics events to a managed ingestion endpoint (collect.easyserversidetracking.com) rather than sending tracking requests directly to google-analytics.com.
- Consent-aware measurement behavior: when visitors refuse cookie consent, events are still forwarded to Google Analytics with identifying fields removed (e.g., no client id / advertising click id / campaign / location/browser detail), keeping the visitor anonymous.
- WooCommerce event coverage out of the box, including product views, add-to-cart, checkout steps, shipping/payment, and purchase; purchase is sent from the server when the order is paid (not dependent on the thank-you page loading).
- Hybrid operation option for GA4: the plugin can run alongside gtag.js, and when hybrid mode is enabled it loads gtag.js from googletagmanager.com only after consent.
- Provisioning/connection workflow: activating the plugin does not transmit externally; external communication occurs when creating a free account / provisioning (sending site URL and admin email) and when linking a site via a Site ID.
- Data handling claims for compatibility context: raw IP is processed for geo lookup/rate limiting and is not stored in raw form long-term (hashed with a rotating daily salt and truncated).
- Local storage of operational/non-personal data in WordPress options (e.g., site id, signing secret, collect endpoint/plan summary, consent evidence fields) and a first-party cookie (esst_click_id) used to associate ad click identifiers with resulting WooCommerce orders.
Distinctive features
Server-side forwarding of analytics events to a managed ingestion endpoint (collect.easyserversidetracking.com) rather than sending tracking requests directly to google-analytics.com. Consent-aware measurement behavior: when visitors refuse cookie consent, events are still forwarded to Google Analytics with identifying fields removed (e.g., no client id / advertising click id / campaign / location/browser detail), keeping the visitor anonymous. WooCommerce event coverage out of the box, including product views, add-to-cart, checkout steps, shipping/payment, and purchase; purchase is sent from the server when the order is paid (not dependent on the thank-you page loading). Hybrid operation option for GA4: the plugin can run alongside gtag.js, and when hybrid mode is enabled it loads gtag.js from googletagmanager.com only after consent. Provisioning/connection workflow: activating the plugin does not transmit externally; external communication occurs when creating a free account / provisioning (sending site URL and admin email) and when linking a site via a Site ID. Data handling claims for compatibility context: raw IP is processed for geo lookup/rate limiting and is not stored in raw form long-term (hashed with a rotating daily salt and truncated). Local storage of operational/non-personal data in WordPress options (e.g., site id, signing secret, collect endpoint/plan summary, consent evidence fields) and a first-party cookie (esst_click_id) used to associate ad click identifiers with resulting WooCommerce orders.
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
Keep plugin capabilities separate from translation scope.
Current evidence documents what Easy Server Side Tracking does, but no specific visitor-facing content values have been approved as translation scope.
Structure, configuration, logic, integrations and runtime behavior are not translation claims.
LIMITATIONS & QA
Verification notes
- This integration is documented for compatibility context. Visitor-facing translation scope is not listed for this category.
COMMON QUESTIONS
Easy Server Side Tracking and REEID Translate FAQ.
Does the current evidence establish translation scope for Easy Server Side Tracking?
No specific visitor-facing content values are currently approved as translation scope for this integration.
What does the plugin intelligence section describe?
It summarizes factual plugin capabilities and distinctive features separately from REEID translation-support claims.
What is required before translation scope is published?
Concrete visitor-facing content values must be supported by evidence, approved for the integration record and tested as appropriate.
RELATED GUIDES
Continue through the compatibility library.
INTEGRATION EVIDENCE
Explore REEID Translate for multilingual WordPress workflows.
REEID separates factual plugin intelligence from evidence-backed translation scope.
No specific visitor-facing content values are currently approved for this integration.