
TRACKLESS
Trackless – Cookieless Analytics compatibility with REEID Translate
Trackless – Cookieless Analytics compatibility with REEID Translate is being reviewed using official plugin documentation. Cookieless analytics with no measurement JavaScript snippet; data collection and delivery are server-side only. No specific text shown to visitors is currently confirmed for translation.
AWAITING VERIFICATION
What Trackless – Cookieless Analytics does
Official plugin information supports the compatibility context documented for this category.
MANUAL REVIEW
This integration has not yet been manually verified by REEID.
PLUGIN PROFILE
Trackless – Cookieless Analytics is documented in the Analytics category with 7 documented features.
DOCUMENTATION REVIEW
We use official plugin documentation to describe what the plugin does. Translation support is listed only for text that can be identified and tested.
COMPATIBILITY REVIEW
How Trackless – Cookieless Analytics compatibility is evaluated
01 · Review official plugin documentation
Confirm documented plugin behaviour before making multilingual compatibility claims.
02 · Identify text shown to visitors
Check whether the documented features display text that visitors can read.
03 · Separate content from functionality
Structure, settings, logic, integrations and runtime behaviour are not treated as translatable content unless they include specific visible text.
04 · Confirm what can be translated
List supported content only after specific text shown to visitors has been identified and can be validated.
PLUGIN INFORMATION
What the plugin does
Plugin capabilities
- Cookieless analytics with no measurement JavaScript snippet; data collection and delivery are server-side only.
- Daily-rotating, keyed HMAC-SHA256 visitor identifier derived from IP + User-Agent + day; raw IP is neither stored nor transmitted (only keyed hash).
- Honors Global Privacy Control (`Sec-GPC`) by not tracking opted-out visitors.
- Event collection via a local queue table in the site database; events are flushed once per day using WP-Cron (or manually via a “Send now” action).
- Data delivery to the hosted Trackless ingest endpoint (`https://trackless.cz/ingest`) is HMAC-SHA256 signed and idempotent (retries are safe).
- Requires explicit opt-in: data is collected and sent only after entering an API key and ticking a Data Processing Agreement (DPA) consent checkbox in plugin settings.
- With WooCommerce enabled, sends e-commerce metrics including orders, revenue, refunds, payment/shipping methods, order attribution computed server-side, and ordered items (optionally including per-unit purchase cost for margin reporting if configured).
TRANSLATION BOUNDARY
Trackless – Cookieless Analytics capabilities and translatable content are documented separately.
Official documentation describes the plugin functionality, but does not currently identify specific text shown to visitors that can be translated.
A feature is not considered translatable unless it includes text that users can read.
LIMITATIONS & QA
Verification notes
- This integration is documented for compatibility context. Visitor-facing translation scope is not listed for this category.
FREQUENTLY ASKED QUESTIONS
Trackless – Cookieless Analytics and REEID Translate FAQ.
What does Trackless – Cookieless Analytics do?
Trackless – Cookieless Analytics has 7 documented features listed in its official documentation. See the Plugin Information section for details.
Does Trackless – Cookieless Analytics have any content currently confirmed for translation?
No specific content is currently confirmed for translation in this integration.
What needs to be confirmed before translating content from Trackless – Cookieless Analytics?
Official documentation must identify specific text, such as labels, titles, descriptions or messages, that can be tested in the integration.
RELATED GUIDES
Explore more compatibility guides.
COMPATIBILITY INFORMATION
Evaluate Trackless – Cookieless Analytics in a multilingual WordPress workflow.
REEID documents Trackless – Cookieless Analytics functionality separately from confirmed translation support so the distinction is clear.
Supported content will be listed when specific translatable text is identified in the official documentation.