Tracklution product update: April 2026
Tracklution’s April update introduces Event Creation Rules to create and transform events server-side, support for new vs returning customer logic, and Custom Connector Pixels to combine frontend pixels with webhooks for more flexible data delivery.
Emma Ojapuska
28/04/2026 12:00 AMThis April brings updates that give you more flexibility in how you shape and deliver your tracking data in Tracklution:
- Event Creation Rules: create and transform events server-side
- + New vs. Returning customer in Event rules: use the parameter to create a separate event for new customer purchases
- Custom Connector Pixel: fire frontend pixels alongside webhooks
🎥 Prefer to watch and learn? Get a quick overview on YouTube.
Event Creation Rules (Create & Transform Events Server-Side)
Event Creation Rules let you automatically create or modify events directly inside Tracklution, based on incoming data, without changing your website tracking setup. Instead of relying on frontend changes or developer work, you can define logic once and apply it to all matching events in real time.
How it works
Each rule is simple: you choose which event to listen for, set any conditions, define the new event you want to create, and decide what happens to the original event. Rules run directly in the event processing pipeline as data comes in.
What you can do with it
Typical use cases include:
- Adjusting conversion values (e.g. profit instead of revenue)
- Splitting events by source (e.g. POS vs web orders)
- Remapping webhook fields to standard event fields
- Filtering out test or internal traffic
- Creating custom events for specific business logic
New: Use “New vs Returning Customer” in Rules
Tracklution automatically identifies whether a customer is new or returning, based on previous purchase data in Tracklution, or data delivered from your backend system, and adds this as a parameter to your events. This parameter can now be used inside Event Creation Rules.
For example:
- Separate Purchase events between first-time buyers and returning customers
- Send only new customer conversions to ad platforms
- Optimise campaigns specifically for new customer acquisition
This makes it easier to align your tracking with actual business goals, not just raw conversion volume.
👉 Learn more about how to create/transform events server-side and about new vs returning customer tracking.
🔌 Custom Connector Pixel (Frontend + Server-Side)
The Custom Connector has been extended. You can now fire a frontend pixel in addition to sending data via webhook. This means your connector can now:
- Send data via webhook
- Fire a frontend pixel
- Or do both at the same time
When to use it
This is especially useful when working with:
- Custom integrations
- Affiliate platforms
- Tracking setups that require specific pixel formats
Important note
During the beta phase, custom pixels need to be approved by Tracklution before they go live.
👉 Learn more about Custom Connector here.
Feature reminder 👇🏻
Magic feature automatically detects potential tracking events on your website and surfaces them for review inside Tracklution. You can approve and activate only what you need, without changing your existing setup.
Wrap Up
These April updates give you more control over:
- How your events are structured (Event Creation Rules)
- How your data is delivered (Custom Connector Pixel)
All directly inside Tracklution, without requiring changes to your website tracking setup.
As always, happy tracking! 👋🏻
Emma Ojapuska
Customer Success Manager at TracklutionRelated posts
Tracklution product update: July 2026
Discover Tracklution's July updates: improved GA4 tracking, Meta attribution insights, stronger first-party tracking, and enhanced reporting.
Tracklution product update: July 2026
Discover Tracklution's July updates: improved GA4 tracking, Meta attribution insights, stronger first-party tracking, and enhanced reporting.
Tracklution product update: June 2026
Tracklution's June update introduces an OpenAI Ads Connector for direct server-side conversion tracking, a more powerful Audit Tool, automatic critical notifications, and attribution improvements for LinkedIn Ads and Adform.
Tracklution product update: June 2026
Tracklution's June update introduces an OpenAI Ads Connector for direct server-side conversion tracking, a more powerful Audit Tool, automatic critical notifications, and attribution improvements for LinkedIn Ads and Adform.
Tracklution product update: May 2026
Tracklution’s May update introduces MCP support for connecting AI assistants directly to Tracklution and automated bot traffic blocking to help reduce spam, improve data quality, and keep optimization signals cleaner.
Tracklution product update: May 2026
Tracklution’s May update introduces MCP support for connecting AI assistants directly to Tracklution and automated bot traffic blocking to help reduce spam, improve data quality, and keep optimization signals cleaner.
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?
