MX COOKIELESS ANALYTICS
MX Cookieless Analytics | REEID Translate Compatibility
REEID processes supported labels, notices and consent-related text while MX Cookieless Analytics 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.
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
- Opt-in tracking behavior: activating the plugin loads nothing and sends nothing until the user pastes a site API key, clicks “Connect & verify site,” and enables tracking in plugin settings.
- Frontend tracker script injection: after tracking is enabled, the plugin loads the MetriXs tracker script (tracker.js) from app.metrixs.eu to collect pageviews and events.
- Backend/API communication for site verification and connection status: the plugin communicates with the MetriXs API at app.metrixs.eu/api/… using the provided site API key (including for “Connect & verify site”).
- Analytics measurement coverage: collects pageviews, visitors, visits, bounce rate, visit duration, and pages per visit.
- Attribution and device/location measurement: collects sources (referrer, UTM, paid-ad click attribution), locations, and devices.
- Event and interaction tracking: supports custom events, outbound link clicks, file downloads, and 404s.
- WooCommerce server-side revenue tracking: when enabled, sends WooCommerce order/checkout-related events server-side to capture redirect-based payment methods; dashboard metrics include revenue, AOV, conversion rate, funnel, and top products.
- Privacy/identity handling claims relevant to compatibility: states it sets no cookies, never stores visitor IPs, and rotates identifiers daily so it cannot track visitors across days; also claims data is EU-hosted (Germany) and does not leave the EU.
Distinctive features
Opt-in tracking behavior: activating the plugin loads nothing and sends nothing until the user pastes a site API key, clicks “Connect & verify site,” and enables tracking in plugin settings. Frontend tracker script injection: after tracking is enabled, the plugin loads the MetriXs tracker script (tracker.js) from app.metrixs.eu to collect pageviews and events. Backend/API communication for site verification and connection status: the plugin communicates with the MetriXs API at app.metrixs.eu/api/… using the provided site API key (including for “Connect & verify site”). Analytics measurement coverage: collects pageviews, visitors, visits, bounce rate, visit duration, and pages per visit. Attribution and device/location measurement: collects sources (referrer, UTM, paid-ad click attribution), locations, and devices. Event and interaction tracking: supports custom events, outbound link clicks, file downloads, and 404s. WooCommerce server-side revenue tracking: when enabled, sends WooCommerce order/checkout-related events server-side to capture redirect-based payment methods; dashboard metrics include revenue, AOV, conversion rate, funnel, and top products. Privacy/identity handling claims relevant to compatibility: states it sets no cookies, never stores visitor IPs, and rotates identifiers daily so it cannot track visitors across days; also claims data is EU-hosted (Germany) and does not leave the EU.
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 MX Cookieless Analytics 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.
RELATED GUIDES
Continue through the compatibility library.
ANALYTICS INTEGRATION
Translate visitor-facing MX Cookieless Analytics 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.