CLICKTRAIL
ClickTrail – UTM, Click ID & Ad Tracking (with Consent) translation compatibility with REEID Translate — evidence review.
Official plugin evidence describes what ClickTrail – UTM, Click ID & Ad Tracking (with Consent) does, but does not yet establish specific visitor-facing content values that REEID should translate.
Visit ClickTrail – UTM, Click ID & Ad Tracking (with Consent) ↗
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
- First-touch/last-touch campaign context capture from UTMs, major ad click IDs, and referrers with organic/social/referral fallback when UTMs are absent.
- Attribution persistence for WooCommerce: stores attribution on WooCommerce orders and pushes enriched purchase events on the thank-you page; can optionally emit GA4-style storefront commerce events (e.g., view_item, view_cart, add_to_cart, begin_checkout) via the plugin’s browser event layer.
- Form attribution enrichment across multiple form plugins: automatic hidden-field injection for Contact Form 7 and Fluent Forms; hidden-field population for Gravity Forms and WPForms using matching ct_* fields; submission-record storage for Elementor Forms (Pro) and Ninja Forms.
- Browser-side event collection and integration with site-owned GTM/dataLayer: pushes collected browser events to the dataLayer and supports canonical REST intake, webhook ingestion, and lifecycle updates; includes one-time WordPress follow-up events (e.g., login, sign_up, comment_submit).
- Optional server-side delivery pipeline: consent-gated dispatch with a retry queue and diagnostics; includes adapter/endpoint configuration and consent recheck immediately before delivery.
- Consent and privacy lifecycle controls: supports selecting a consent source/mode (including listening to banner/Cookiebot/OneTrust/Complianz/GTM/custom) and synchronizes browser consent authority across tabs; includes allowlisted export/erase/retention/uninstall lifecycle for WooCommerce order metadata.
- Cross-domain continuity support via approved link decoration and attribution tokens to preserve observed context between configured domains/subdomains.
Distinctive features
First-touch/last-touch campaign context capture from UTMs, major ad click IDs, and referrers with organic/social/referral fallback when UTMs are absent. Attribution persistence for WooCommerce: stores attribution on WooCommerce orders and pushes enriched purchase events on the thank-you page; can optionally emit GA4-style storefront commerce events (e.g., view_item, view_cart, add_to_cart, begin_checkout) via the plugin’s browser event layer. Form attribution enrichment across multiple form plugins: automatic hidden-field injection for Contact Form 7 and Fluent Forms; hidden-field population for Gravity Forms and WPForms using matching ct_* fields; submission-record storage for Elementor Forms (Pro) and Ninja Forms. Browser-side event collection and integration with site-owned GTM/dataLayer: pushes collected browser events to the dataLayer and supports canonical REST intake, webhook ingestion, and lifecycle updates; includes one-time WordPress follow-up events (e.g., login, sign_up, comment_submit). Optional server-side delivery pipeline: consent-gated dispatch with a retry queue and diagnostics; includes adapter/endpoint configuration and consent recheck immediately before delivery. Consent and privacy lifecycle controls: supports selecting a consent source/mode (including listening to banner/Cookiebot/OneTrust/Complianz/GTM/custom) and synchronizes browser consent authority across tabs; includes allowlisted export/erase/retention/uninstall lifecycle for WooCommerce order metadata. Cross-domain continuity support via approved link decoration and attribution tokens to preserve observed context between configured domains/subdomains.
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 ClickTrail – UTM, Click ID & Ad Tracking (with Consent) 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
ClickTrail – UTM, Click ID & Ad Tracking (with Consent) and REEID Translate FAQ.
Does the current evidence establish translation scope for ClickTrail – UTM, Click ID & Ad Tracking (with Consent)?
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.