ClickTrail / first-party attribution
KEEP THE SIGNAL
Capture UTMs, click IDs, referrers, and consent-aware events before a cached page, route change, form, order, or workflow breaks the trail.
KEEP SOURCE WITH THE CONVERSION
The missing layer
A click is observed in one runtime while a form, order, or workflow completes in another. ClickTrail keeps source context in a canonical payload so the host can store, inspect, and route it without handing attribution logic to a hosted analytics vendor.
Designed for real handoffs
- Landing pages and conversion surfaces often live in different runtimes.
- SPA route changes, cached pages, and dynamic forms can skip ordinary page-load assumptions.
- Consent is decided by the host before capture, storage, or dispatch begins.
- Flat canonical payloads map to a dataLayer, CRM, database, or server intake.
- WordPress remains a supported distribution, not the boundary of the product.
CAPTURE, EVENTS, RUNTIMES, AND DELIVERY
The ClickTrail workspace separates the deterministic engine from browser, server, framework, workflow, and WordPress adapters. Adopt only the surfaces your implementation can verify.
Core engine
Parse arrival context and merge first-touch and last-touch attribution into a deterministic, flat contract.
Browser
Capture in the browser, persist first-party context, enrich forms, and push canonical events to a host-owned dataLayer.
Server
Build conversion and delivery events on the server when the application owns the request lifecycle and endpoint boundary.
Adapters
Use framework and workflow integrations for Astro, Nuxt, SvelteKit, Qwik, Svelte CLI, n8n, Activepieces, Directus, Typebot, and Formbricks.
WordPress
Keep the plugin distribution for WooCommerce, forms, admin diagnostics, and configured endpoint delivery.
QUESTIONS TO SETTLE BEFORE YOU INSTALL
Start here