ClickTrail / docs
Documentation for the handoff
Read the guide that matches the boundary you own. Every page names prerequisites, install, configuration, payload, consent, failure modes, verification, evidence, and sources.
Start with meaning
Core contract
ClickTrail docs / quickstart
Carry the signal to the conversion boundary
Start with the smallest path that proves a tagged visit survives to one form, order, or application event. Add delivery only after the local record is correct.
ClickTrail docs / contract
Use one flat attribution contract
The contract separates observed first-touch and last-touch fields from the systems that store, report, or deliver them. Keep the meaning stable while adapters change.
ClickTrail docs / attribution models
Explain first-touch and last-touch separately
First-touch and last-touch answer different questions. Store both when the business needs acquisition origin and the most recent eligible context in the same record.
ClickTrail docs / consent
Put consent before capture and delivery
ClickTrail receives consent state from the host. The CMP remains the owner of the legal decision, while the adapter applies that decision to capture, storage, and delivery.
ClickTrail docs / storage
Make storage and retention an explicit choice
The browser adapter can use host-controlled first-party storage, but the host still defines lifetime, fields, access, deletion, and the boundary where data stops being needed.
Then connect the record
Conversion boundaries
ClickTrail docs / forms
Carry attribution into forms without trusting the current URL
Forms often render from cached HTML or complete after a route change. Bind fields at the form boundary, then inspect the actual stored entry instead of assuming that a tagged landing URL survived.
ClickTrail docs / commerce
Inspect the order, not only the browser event
WooCommerce adds an order record, checkout lifecycle, purchase event, and optional delivery path. Verify each boundary so a direct-looking report can be separated from a missing capture or missing provider receipt.
ClickTrail docs / analytics
Use GTM as the routing layer, not the source of truth
ClickTrail can push canonical events to a host-owned dataLayer. GTM maps and routes those events, while GA4 or another consumer must still be inspected at its own request boundary.
ClickTrail docs / server
Add server delivery only after the local event is correct
Server delivery changes the ownership and failure boundary. The server package can build or send events, but it does not create a collector, authenticate a provider, or certify acceptance.
ClickTrail docs / offline outcomes
Treat offline conversion upload as a separate acceptance chain
A CRM, booking, call, or revenue outcome can be mapped to observed acquisition context, but the upload is only complete when the destination accepts the event and the business record can be reconciled.
ClickTrail docs / webhooks
Make webhook delivery observable
A webhook URL is only a configured destination. Keep request, response, consent, retry, idempotency, and final business-record evidence separate.
Finish with proof and ownership
Operations
ClickTrail docs / troubleshooting
Debug the boundary where the signal disappears
Troubleshooting starts with a unique tagged visit and a boundary-by-boundary trace. Do not jump from a blank report to a provider or plugin conclusion.
ClickTrail docs / security and privacy
Keep the data boundary visible
ClickTrail carries observed acquisition context. It does not make a legal determination, resolve a person across devices, or remove the need for the host's security and privacy controls.
ClickTrail docs / migration
Migrate one conversion boundary at a time
A migration is safe when the old and new paths have named responsibilities, compatible fields, and a rollback. Do not replace a working source with two unverified writers.
ClickTrail docs / API reference
Use the API surface that matches your owner
The JavaScript repository separates core parsing, browser lifecycle, consent, and server delivery. Import only the surface the host owns and keep incubating entry points behind an adapter.
ClickTrail docs / testing
Turn the conversion path into a failing test
A green unit test proves a function. A trustworthy integration test proves that a tagged visit reaches the record and destination you actually use, including denied and failed paths.