Tracklution product update: February 2026

February’s product release has officially dropped! 📦

This month brings clearer attribution insights and stronger Google integrations.

Prefer to watch and learn? Get a quick overview on YouTube.

✨ First Paid Click Attribution

You can now switch between First Paid Click and Last Paid Click directly in the Tracklution dashboard. This makes it easy to see:

• Which ad platform introduces the customer
• Which ad platform closes the customer

It’s a powerful addition for multi-touch journeys and cross-platform analysis.

As always, this affects reporting inside Tracklution only. All valid conversions are still delivered to ad platforms, which apply their own attribution models.

🧩 Campaign Manager 360 Connector

The CM360 Connector is now available!

You can send conversions directly to Campaign Manager 360 with automatic mapping, enhanced conversions support, and hybrid Pixel + API delivery.

If you’re using CM360, let us know - we’re happy to hear feedback and answer integration questions.

Here’s a link to the Connector documentation.

🔗 Google Ads Connector

We’ve added support for the new_customer field in Google Ads conversions. This will be included in outgoing payloads and visible in logs for verification.

At the same time, we’ve upgraded the Google Ads API to v23. The move to API v23 keeps us fully up to date with Google’s latest version. There are no changes affecting the functionality we use, so no disruption is expected, just a clean upgrade to the newest standard.

🔄 Custom Connector: Event Name Override

You can now override event names in the Custom Connector webhook.

This allows you to keep standard Tracklution event names internally (e.g. PageView) while sending platform-specific formats (e.g. page_view) to external endpoints like Outbrain.

No need to rename events globally anymore,  event name mapping can now be handled directly inside the Custom connector.

We’ve also improved the Tracking Script and GTM Template to support multiple simultaneous initializations from different sources. Previously, parallel loads could cause race conditions and pointer conflicts in certain setups — this has now been resolved.

Feature reminder 👇🏻

Trackie AI is already inside your container. Ask about purchase volume, recent drops, deduplication or setup gaps and get clear answers based on your real tracking data. So before you dig through logs, ask Trackie.

Wrap Up

This month’s updates give you clearer attribution comparisons, stronger Google integrations, and more flexibility in how events are structured and sent out. More precision in reporting, more control in setup, and more confidence in the data you’re scaling on.

As always, happy tracking. 👋🏻