What's new in ClickTrail since launch

Thanks to everyone who's followed along. Here's what we've shipped in the month since launch:

WordPress plugin (now v1.10.3)

• Calendly bookings now keep their ad click. Booking links, inline widgets and popups carry the click ID and consent, bookings come through as book_appointment with their UTMs, and cancellations no longer count.

• Consent is tighter. We fixed a Complianz issue where an accepted banner could be read as a refusal, Cookiebot withdrawal now clears ClickTrail storage right away, and nothing gets written to orders or form entries once marketing consent is denied.

• Contact Form 7 only counts a conversion after a successful submission, and duplicate touch records are gone.

• Settings, Logs and Diagnostics have a cleaner look.

Core SDK (clicktrail-js 0.2.0 RC)

• New adapters for Next.js (first touch preserved through signup), Shopify, PostHog, and Meta/WhatsApp referrals with Chatwoot.

• Cookiebot, OneTrust and Complianz consent adapters.

• Better handling of cached and dynamic WordPress forms, plus stricter safety checks on server destinations.

New tools around it

• clicktrail-mcp: an MCP server so AI agents can work with attribution schemas, diagnostics and conversion delivery.

• clicktrail-skills: agent playbooks for Google Ads offline conversions, Meta CAPI dedup and click ID preservation.

• clicktrail-verify: a local tool that checks whether attribution actually survives the handoff.

• clicktrail-examples: runnable setups for Next.js, Shopify, Twenty CRM, Chatwoot, Google Ads and Meta CAPI.

Still free and open source. If your click IDs or UTMs go missing somewhere between the ad and the sale, tell me where it happens. That's what decides what we build next.