Video Walkthrough
{height=315 width=560}
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.
You can 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.
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 Webhooks from here: Send Events From Any Platform With a Webhook
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. Google Ads, Google Analytics 4, and Microsoft Ads support Consent Mode directly in their pixels, meaning tracking can continue in a limited form (cookieless pings) when consent is denied. Meta and Pinterest, on the other hand, do not support Consent Mode in their pixels, but they provide an opt_out parameter in their server-side APIs (Conversions API). This allows Tracklution to deliver data through the API when consent is granted, and omit data when the user opts out. For platforms that do not support Consent Mode at all, data is not sent when consent is denied.
To enable advanced consent mode with Tracklution, toggle on the Use automatic consent reading, and optionally apply your default consent states for Analytics and Marketing (defaults set inside the Tracklution UI will be treated as fallback consent states). This setting is found under the Settings tab in your Tracklution dashboard.
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. If you load Tracklution tags with "Advanced Consent Mode" (in other words: 'no additional consent'), Tracklution will automatically read and adjust to consent values from Data Layer when you activate "**Use automatic consent reading"**from the container's Settings > Advanced Settings.
Using Shopify App
If you are using Shopify App, Tracklution can read consent status from Data Layer and apply them 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':'{{ ADD DATA LAYER VARIABLE HERE }}', 'marketingConsent':'{{ ADD DATA LAYER VARIABLE HERE }}'});
</script>
Detailed implementation:
<script>tlq('set', 'Consent', { 'ad_user_data':'{{ ADD DATA LAYER VARIABLE HERE }}', 'ad_personalization':'{{ ADD DATA LAYER VARIABLE HERE }}', 'ad_storage':'{{ ADD DATA LAYER VARIABLE HERE }}', 'analytics_storage':'{{ ADD DATA LAYER VARIABLE HERE }}'});
</script>
Important: Values need to be 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"), or
- 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, OR
- Manual implementation
- 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
- First-party user provided data from webhooks or website visitors
- Configured and collected automatically if you use Shopify App or WooCommerce Plugin, or if you 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 a technology provider (processor) and don't gain any control rights to your data.
