Tracklution Knowledge Base

Here, you'll find practical guides, best practices, and detailed integration instructions to help you. We’ve organized the content into focused sections so you can quickly find what you need. If you're new to Tracklution, start with Get Started. If you're integrating with platforms like Google Ads or Meta, head to Data Destinations. Whatever your goal, these docs are here to support you.

This video gives a high-level introduction to the Tracklution dashboard for users who are new to the platform. It walks through the overall structure of the dashboard and explains how different parts of Tracklution fit together after you log in. You’ll see how tracking containers are organized, where to find events and session data, and how the dashboard helps you understand what data is being tracked and where it is being delivered. The video also briefly introduces key area…

Create Tracklution account at www.tracklution.com. The account is used to get access to your Tracklution tracking containers. You may have access to multiple tracking containers with the account, and you may create multiple companies with the account. Once you have clicked "Start for free" at www.tracklution.com, you will be guided through the onboarding process. To finish creating the account you need to:

Deleting a Tracking Container permanently stops Tracklution from collecting, processing, and delivering data for that container.

You can track multiple websites in one Tracking container with simple implementation.

Enable first-party data collection with DNS setup. This is highly recommended as it increases the amount of tracked conversions. To fully unlock the power of Tracklution’s server-side tracking, we strongly recommend setting up a custom DNS record for your website. This crucial step allows you to collect data as first party, dramatically improving your ability to track conversions accurately, even when third-party cookies are blocked or click IDs are missing.

After adding the Tracklution Main script to your website, you can start tracking events. If you have not yet installed any Tracklution tracking on your site, please do that first. Find a suitable installation method for your site from here: https://www.tracklution.com/docs/

You can add extra parameters to your events if you want to send (eCommerce) data to Tracklution when events are tracked on your website. For example; you want to send product information with "AddToCart" event. You can send send event parameters with an event to Tracklution by pushing them from your website to Google Tag Manager data layer. You can also do this with manual script installation without Google Tag Manager.

In the Settings tab of your tracking container, the Standard and Custom Events table gives you a full overview of all current event mappings and lets you remap events per Connector.

If you want to set up two data-servers for your website for whatever reason, different configurations, multiple ad-accounts, opposite consent modes, you can do so by setting up two data-servers for you website. This is done by duplicating your Tracklution tags in GTM and adding the target parameter to your duplicated tags with your second container's Tracklution ID.

There’s been a lot of discussion about Safari removing ad click identifiers such as Google’s GCLID, Facebook’s FBCLID, Microsoft’s MSCLKID, and others. Some of this is based on rumor, so it’s important to still keep level headed while preparing for official updates.

Using the Tracklution Template in Google Tag Manager, each event has its own tag, and each tag need at least one trigger.

To add your own individual or custom Tracklution events in Google Tag Manager, start by installing the Tracklution template for Google Tag Manager. Go to the Templates tab in Google Tag Manager and click Search Gallery. Search 'tracklution' for the Tracklution template by tracklution and click Add to workspace. Proceed to approve and install this template.

You can now prevent duplicate events by using the event ID parameter. This ID helps ensure that the same event isn’t tracked multiple times.

When you collect product information in your events to send to your analytics or ad platforms, Tracklution automatically picks which product ID to include. It checks several options in a set order and uses the first one that’s available.

When you want to exclude website traffic from being tracked in your server-side container, (e.g. internal traffic, traffic from a specific country, specific pages, currencies, or for example 0 value purchases) you can use the Event Block Rules to do so.

After DNS is configured for tralut.website.com then the content security policy (CSP) headers file needs the https://tralut.website.com URL and the backup URL https://main-1234.trlution.com added to these policies:

Event Creation Rules let you automatically create or transform tracking events based on data arriving in Tracklution without changing your website code or dataLayer. You define the logic once, and Tracklution applies it to every matching event in real time.

Tracklution tracks whether a converting visitor is a new or returning customer and makes this data available across your tracking setup. You can use it to enrich conversion signals sent to ad platforms, split events by customer type, build filtering logic, or forward the data to external systems like a CRM or affiliate network.

Tracklution's MCP integration lets you connect AI assistants that supports MCP directly to your Tracklution account. Once connected, you can query your tracking data, check your setup, and get insights in plain language, without opening the dashboard.

You can now use Event Block Rules to automatically block likely bot traffic from being tracked in your Tracklution container. This helps improve reporting accuracy and prevents low-quality traffic from being sent to ad platforms.

In the video below, we show how to send offline conversions with a webhook in two ways:

First, get started at www.tracklution.com by creating an account and providing your website URL to create a Tracking Container for your site inside Tracklution.

The template works like the standard script method, but with fewer manual errors and easier tag maintenance.

First, get started at www.tracklution.com by creating an account and providing your store URL. Tracklution will check if your site operates with Shopify, and if it does, it will suggest you install the Shopify App.

First, get started at Tracklution.com by creating an account and providing your store URL. Tracklution will check if your site operates with WooCommerce, and if it does, it will suggest you install the WooCommerce Plugin.

To install Tracklution tracking to your website you can implement the scripts directly to the code of your website if you don't want to use a tag management system like Google Tag Manager for the installation.

A webhook is a tool that allows different systems to communicate with each other in real time. In essence, it’s a way for one application to send automatic data updates to another as soon as a certain event occurs. This eliminates the need for constant polling and ensures that information flows seamlessly between platforms.

You can enrich data in Tracklution by utilising our webhook feature and sending the data fully server-side to Tracklution.

Sending events from Calendly to Tracklution allows you to track booked appointments and integrate this data with your website’s user sessions. By linking Calendly events to Tracklution, you can gain deeper insights into user behavior, track offline conversions, and optimize your marketing efforts by connecting booking activity to other interactions. This helps you understand how appointments impact your overall conversion funnel and improve your tracking accuracy.

To maximize the effectiveness of your ad campaigns, it's essential to track real conversions, attribute them correctly, and provide ad platforms with reliable data. Tracking Stripe checkouts can be challenging due to external checkout sessions, tracking code limitations, and cross-domain issues. Tracklution simplifies this process with an easy, no-code solution that combines website visitor data with Stripe purchase data through server-side tracking. This ensures precise trac…

Magic is an experimental feature that automatically detects possible tracking events on your website: things like button clicks, form submissions, or other user interactions.

To create a webhook to send data to your server:

Connectors are used to send the data collected from your website to the specific Ad Platforms and Analytics platforms you choose. We currently provide Connectors for:

The Google Ads Connector is used to send data to the Google Ads API.

The Google Analytics 4 Connector sends your Tracklution-tracked events to Google Analytics 4 through the Tracking Pixel and the GA4 Measurement Protocol (API). New connectors use the latest version, GA4 v2. The legacy GA4 v1 is also available; see Connector versions below.

The LinkedIn Conversion API Connector is used to send data to LinkedIn's Conversion API. The connector uses the LinkedIn Conversion API send data to LinkedIn.

The Facebook/Meta Ads Connector is used to send data to the Facebook/Meta Conversion API.

The Snapchat Ads Connector is used to send data to the Snapchat Ads Pixel and Conversion API.

The TikTok Ads Connector is used to send data to the TikTok Pixel and Conversion API.

The Pinterest Ads Connector is used to send data to both the Pinterest Ads Pixel and Conversion API.

The Adform Connector is used to send data to both the Adform Pixel and Conversion API.

The Microsoft Ads Connector is used to send data to both the Microsoft Ads Pixel and Conversion API.

The Custom Connector lets you deliver Tracklution event data to external systems in two ways:

The Klaviyo Connector is used to send data to the Klaviyo onsite tracking pixel and Klaviyo API.

The Reddit Connector is used to send data to the Reddit onsite tracking pixel and Reddit CAPI.

The Campaign Manager 360 (CM360) Connector is used to send conversion data to Google's Campaign Manager 360 via the CM360 Conversions API. Tracklution sends events by creating and firing Floodlight Activities in your CM360 account.

The OpenAI Ads Connector is used to send data to the OpenAI Ads Measurement Pixel and the OpenAI Ads Conversions API.

This video explains how Consent Mode works with Tracklution and the difference between Basic and Advanced implementations. It walks through how tracking behavior changes based on granted or denied consent, how to enable automatic consent reading, and how to manually pass consent values if needed. The video also covers Shopify setups and how to test that consent status is correctly reflected inside the Tracklution dashboard.

Tracklution is fully GDPR compliant, with all customer data securely stored within the European Union, specifically in AWS Stockholm.

From the Tracklution container dashboard, you can see all events Tracklution has captured, including details like timestamps, sources, event values, and the Connectors they were sent to. For deeper inspection, you can drill down into individual sessions to view event payloads, ClickIDs, and UTM tags, helpful for both validation and troubleshooting. Filtering and search tools make it simple to focus on specific events, time ranges, or Connectors, so you can quickly identify an…

You can download events as CSV from the Dashboard if you need to make reports, debug, cross-check sales, compare performance, or do custom analysis. To export as CSV:

Server-side tracking enables more accurate conversion tracking, which improves the quality of data sent to ad platforms. Better data allows ad algorithms to perform more effectively, resulting in better ad performance and higher return on advertising spend.

Update missing from the video: as of February 2026, you can also use First Paid Click attribution on your Tracklution dashboard.

Are you missing an event that should be delivered to Meta or Google Ads? Find your missing event by going through the Tracklution Debug Quest.

At Tracklution, we follow a structured and professional approach to system development to ensure reliability, maintainability, and continuous improvement. Our development process is designed to guarantee that our system remains stable while evolving with new features.