GTM template with instructions video from Simo Ahava!

GTM template with instructions video from Simo Ahava!

Tracklution product update: February 2026

Tracklution’s February 2026 update introduces First Paid Click attribution, a new CM360 connector, Google Ads enhancements, and improved Custom Connector flexibility and script stability.

Emma Ojapuska
26/02/2026 12:00 AM

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. 👋🏻


Emma Ojapuska

Customer Success Manager at Tracklution


Questions and answers

What does Tracklution actually do?

Tracklution sends conversion data directly to ad platforms (Meta, Google Ads, TikTok, etc.) through server-side APIs. Instead of relying on browser pixels that get blocked by ad blockers, iOS privacy changes, and cookie restrictions, your data goes server-to-server. The result: ad platforms see more of your real conversions, their algorithms optimize better, and you get better ROAS.

What is server-side tracking?

Server-side tracking gathers first-party data directly on your website and sends tracking events to ad platforms via Conversion APIs. This approach bypasses restrictions from iOS devices, ad blockers, and privacy-focused browsers, providing more accurate data and making your paid advertising more efficient.

Is it just one setup that feeds data into all my ad platforms?

Yes. You install Tracklution once, connect your ad accounts, and it sends conversion data to all platforms simultaneously through their respective APIs (Meta CAPI, Google Ads API, TikTok Events API, etc.). No need to manage separate server-side setups for each platform.

How much more conversion data will my ad platforms actually see?

On average, clients report 34.2% more conversions compared to traditional browser-based pixels. This means the ad algorithms have significantly more signal to work with, which translates to 15-35% lower customer acquisition costs for most clients.

Do I need developers to set this up?

No. Setup takes 5-15 minutes depending on your platform. For Shopify, WooCommerce, and other supported platforms, it is plug-and-play. You do not need custom coding or engineering resources. For GTM users, you can keep your existing setup and add Tracklution alongside it.

Do I need to remove my existing tracking tags?

Not necessarily. Tracklution works alongside your current setup. You can run both in parallel initially to compare data, then decide whether to simplify.

What about the DNS / CNAME setup?

Tracklution uses a first-party CNAME record on your domain for data collection. This takes a couple of minutes to configure and up to 48 hours to propagate. It is what makes the tracking resistant to ad blockers and browser restrictions.

Can I verify that the data is actually more accurate?

Yes. Run Tracklution alongside your existing tracking and compare. The dashboard also shows "recovered events" so you can see exactly how many conversions would have been missed without server-side tracking.

Can I distinguish between organic and paid traffic?

Yes. Tracklution preserves traffic source attribution. The conversion data sent to each ad platform includes the proper attribution parameters.

What about offline conversions (phone calls, in-store, CRM events)?

Tracklution supports offline conversion tracking through webhooks and CRM integrations. If someone clicks an ad, then converts offline, you can feed that back to the ad platforms. Clients using this see up to 35% reduction in acquisition costs because the algorithms learn from the full conversion picture.

How does this work with cookie consent and CMP tools?

Tracklution supports both Basic and Advanced Consent Mode. It reads your CMP data layer automatically and respects user consent choices. In Advanced Consent Mode, it can still collect anonymized, cookieless data when users decline cookies, which helps ad platform modeling without violating privacy rules. Fully GDPR-compliant.

How is this different from Stape or building your own sGTM setup?

Stape provides server-side GTM hosting, which means you still need to build and maintain the tags, triggers, and configuration yourself. Tracklution is a complete solution: plug-and-play setup, automatic event detection, built-in consent management, a real-time analytics dashboard, and ongoing maintenance of all API connections. When ad platforms change their APIs (which happens often), we handle the updates.

How does the agency partner model work?

Single dashboard to manage all client accounts. Each client has their own tracking container. The platform handles all technical maintenance, so you are not stuck troubleshooting API changes or broken tracking.

Have further questions?

Contact us

Already convinced? Get 100% accurate data with server side tracking

Start a Free trial

Already convinced? Get 100% accurate data with server side tracking

Start a Free trial

Server-Side Tracking, First-Party Cookies and Conversion APIs for any website with easy installation. Simple yet powerful tracking tool for digital advertising.

Tracklution customer rating badgeTracklution customer rating badge

4.8+ Rating on G2 and Trustpilot

Helsinki

Simonkatu 6 A
00100 Helsinki, Finland

New York

307 W 38th St
NY 11105, United States

Meta partner badge
Google partner badge
Meta partner badge

For AI coding agents: read www.tracklution.com/agent-install.md for one-shot install, or tell your agent: “Install Tracklution.”

© Tracklution Oy 2026. All rights reserved.