Keep campaign context attached to WooCommerce orders, WordPress forms, and event flows across cached pages, dynamic forms, cross-domain journeys, repeat visits, and consent-aware sites.

Read in English
Leia em Portugues (Brasil)
Contributor Guide
Guia de Contribuicao
Technical Docs
WordPress Readme

• WooCommerce orders lose campaign context before revenue is reported.
• UTMs and click IDs disappear after the landing page.
• Cached or dynamic forms submit without attribution.
• Cross-domain flows reset the source trail.
• Teams need consent-aware capture and optional server-side delivery in one plugin.

ClickTrail is designed to keep first-touch and last-touch context alive until the point where WordPress actually needs it: WooCommerce orders, form submissions, browser events, and optional downstream delivery.

• Capture: first-touch and last-touch attribution, referrers, classic and extended UTMs, click IDs, browser identifiers, retention, and cross-domain continuity.
• WooCommerce: order attribution, enriched purchase payloads, thank-you page purchase pushes, optional list-view and cart storefront events, richer Woo dataLayer support, and post-purchase milestones.
• Forms: automatic hidden-field enrichment for Contact Form 7 and Fluent Forms, compatible hidden-field population for Gravity Forms and WPForms, cached-page fallback, dynamic-content support, and WhatsApp continuity.
• Events: browser collection, dataLayer pushes, sGTM compatibility mode, webhook intake, lifecycle updates, and optional Woo storefront signals.
• Delivery: optional server-side transport, retries, diagnostics, conflict scanning, backup/restore, and consent-aware dispatch.

This maintenance release cleans up coding-standards noise and packaging consistency without changing runtime behavior.

• Mixed line endings were normalized in the consent, attribution-token, and privacy handlers.
• Remaining PHPCS findings in those handlers were resolved or documented where the behavior is intentional.
• Runtime behavior is unchanged from 1.5.1.
• Full release notes are available in changelog.txt and the public WordPress listing in readme.txt.

• GitHub visitors: start with README.en.md or README.pt-BR.md.
• Contributors and reviewers: use CONTRIBUTING.md or CONTRIBUTING.pt-BR.md.
• Engineers and agents: use docs/README.md and AGENTS.md.

• docs/README.md: engineering index by task and subsystem
• docs/guides/IMPLEMENTATION-PLAYBOOK.md: practical rollout guide for lead-gen, WooCommerce, cross-domain, consent-aware, and server-side setups
• docs/architecture/PLUGIN-OVERVIEW.md: runtime architecture and module map
• docs/reference/INTEGRATIONS.md: forms, commerce, consent, webhook, and delivery integrations
• docs/guides/SETTINGS-AND-ADMIN.md: current admin IA and option mapping
• changelog.txt: full plain-English release history aligned with the WordPress readme
• .github/PULL_REQUEST_TEMPLATE.md: PR checklist for repo changes

1. Read CONTRIBUTING.md.
2. Use docs/README.md to find the canonical doc for the area you will change.
3. Keep product docs, technical docs, and changelog entries aligned with the implementation.

• WordPress 6.5+
• PHP 8.1+

GPL-2.0-or-later. See LICENSE.