Compatibility with Cookie Banners and Consent Mode (v2)

Loading Tracklution tags after Cookie Consent has been given ("Basic Consent Mode")

The most common installation method is to set up Tracklution tags to load only after cookie consent has been given, in a manner similar to how other tracking tags are typically loaded post-cookie consent. This is the default assumed installation approach.

The first PageView should be triggered IMMEDIATELY once cookie consent is given! It is sometimes observed that the first PageView trigger occurs only after the user moves to the next page, which can result in the loss of important information from the beginning of the session, such as UTM tags and click IDs.

Additional Information:

If, for instance, in the event of a purchase, terms of use acceptance or customer relationship establishment provides a basis for data processing, but cookie consent was not initially obtained, purchases can also be reported to a webhook as an offline conversion. This also functions as a method to complement conversion data in the "Loading Tags After the Cookie Banner" installation approach. Read more about Webhook

Loading Tracklution tags always ("Advanced Consent Mode")

It is possible to implement Advanced Consent Mode. This integrates the customer's cookie choices into Tracklution and allows Tracklution tags to load immediately upon session start. Tracklution will communicate user's consent choices to the Connectors that support Consent Mode. Consent Mode is currently supported by Google Ads, Google Analytics 4, and Microsoft Ads. For the Connectors that support consent mode, tracking pixels can be loaded. For the Connectors that do not support consent mode, tracking pixels are not loaded. Data can still be delivered via server-side APIs.

Using GTM's built-in Consent Mode: If you are using GTM built-in Consent Mode and have integrated your cookie banner to it, Tracklution can read those values from Data Layer automatically. To enable this, you do not need to do anything - if you load Tracklution tags with "Advanced Consent Mode" (always), Tracklution will automatically read and adjust to consent values from Data Layer.

Using Shopify App or WooCommerce Plugin: If you are using Shopify App or Woocommerce Plugin, Tracklution can reads consent status from Data Layer automatically.

Manual installation of Cookie Consent Status

If you cannot or don't want to use the above mentioned automatic options, you can implement cookie consents manually.

The most critical aspect of entering Consent Mode values is that they should be communicated to Tracklution as quickly as possible, ideally at the start of the session or when the cookie consent is obtained/updated.

Many have implemented this alongside the PageView tag, ensuring it continuously accompanies the session and updates if choices are revised (e.g., consent is given after several page loads or during a purchase event, when a customer relationship is established, providing a basis for data processing).

Either of the following models can be used, depending on which is easier for the installation:

Simple implementation:

<script>
	tlq('set', 'Consent', {
		'analyticsConsent':'{{ INSERT DATA LAYER VARIABLE HERE }}', 
		'marketingConsent':'{{ INSERT DATA LAYER VARIABLE HERE }}'
	});
</script>

Detailed implementation:

<script>
	tlq('set', 'Consent', {
		'ad_user_data':'{{ INSERT DATA LAYER VARIABLE HERE }}', 
		'ad_personalization':'{{ INSERT DATA LAYER VARIABLE HERE }}', 
		'ad_storage':'{{ INSERT DATA LAYER VARIABLE HERE }}', 
		'analytics_storage':'{{ INSERT DATA LAYER VARIABLE HERE }}'
	});
</script>

(Values are either 'granted' or 'denied'. Remember to replace the pre-set values with correct Data Layer Variables.)

You always have full control on how Tracklution is installed and what data is collected

Installation in relation to Cookie Banner

You can always choose whether you install Tracklution tags to be loaded:

Only after Cookie Consent has been granted ("Basic Consent Mode")

Always ("Advanced Consent Mode")

What data is collected

Web session related technical data: user agent, IP address (collected automatically)
Cookie consent:
- GTM built-in Consent Mode, Shopify, WooCommerce (collected automatically), OR
- Manual implementation (not collected automatically)
Events happening in your website:
- Events happening in website you have configured manually
- Standard ecommerce funnel events configured automatically, if you use Shopify App or WooCommerce Plugin)
Additional event data: eCommerce data
- eCommerce data like product IDs and product variants
- Configured and collected automatically, if you use Shopify App or WooCommerce Plugin)
- Configure manually in GTM or directly in website
Enhanced Conversions: ContactInfo tag
- Enables the collection of 1st party data from users that convert on your website
- Configured and collected automatically, if you use Shopify App or WooCommerce Plugin), or have selected automatic collection from GTM data layer
- Configure manually in GTM or directly in website

What data is sent and where

You always define and control which Connectors (data destinations) you use. Tracklution never sends your data forward to ad platforms unless you have activated a Connector to send data.
You can always activate, pause, and review Connector statuses in your Tracking Container.
You always have full transparency and logging in your Tracking Container to see what data has been collected and what data has been sent to each active Connector.
All PII data is always hashed before it's forwarded to any Connector. You can hash this data before it reaches Tracklution, or let us handle hashing for you. Hashed or not, your data always remains yours - we're only a technology provider (processor) and don't gain any control rights to your data.

Validate Tracking Setup Tracking Events