Tracklution product update: April 2026

This 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! 👋🏻