Skip to content
English
Go to trendemon.com
  • There are no suggestions because the search field is empty.

How Trendemon Supports Cookieless Tracking & Consent Logic

Overview

Trendemon provides flexible options to ensure our tracking setup aligns with your specific privacy and compliance requirements. How Trendemon behaves depends on whether our script is managed by your Google Tag Manager (or any other tag manager) or by Trendemon's logic. 

Scenario A: Managed by Google Tag Manager

In this scenario, you configure Google Tag Manager (or another tag manager) to fire the Trendemon tag only after the visitor grants cookie consent.

  • How it works: Trendemon does not manage the consent logic. We simply execute immediately once the script is loaded by Google Tag Manager.
  • Behavior: Since consent is already granted by the time we load, we immediately use standard First-Party Cookies and activate all integrations.

Scenario B: Trendemon Managed

If not managed by Google Tag Manager, you can use one of the following 2 Modes to determine how we handle data before and after cookie consent:

Option 1: Cookieless Mode (Local Storage) - opt-out option 

  • How it works: We use browser Local Storage as the default method to track and store visitor’s info, ensuring that analytics are available even if cookies are declined.
  • Pre-Consent State: We store the Trendemon Visitor ID in Local Storage. No cookies are written to the browser, and we don't pair Marketing Automation to Trendemon.
  • Post-Consent (If "Accept" is clicked): We switch from Local Storage to Standard First-Party Cookies. Marketing Automation pairing becomes active.
  • Post-Consent (If "Decline" is clicked): We continue using (or revert to) Local Storage. Any existing Trendemon cookies are deleted.

Option 2: Strict Mode (Zero Storage) - opt-in option

  • How it works: The Trendemon script requires a positive consent signal in order to load. 
  • Pre-Consent State: We don’t use any of the following tracking methods: Cookies, Local Storage, Fingerprinting.
  • Post-Consent (If "Accept" is clicked): The script activates and we begin using Standard First-Party Cookies. Full tracking and MA integration are enabled.
  • Post-Consent (If "Decline" is clicked): Same as pre-consent state - our script does not load and no data is written or stored. 

Real-Time Consent Detection

Applies to Scenario B (Trendemon Managed)

Trendemon utilizes intelligent Event Listeners to monitor visitor interactions with your cookie consent banner in real-time. We detect whether a visitor clicks "Accept" or "Decline", and immediately adjust the tracking behavior to match your selected configuration (Cookieless, Strict, or Essential) without requiring a page reload.

If a visitor clicks "Decline" after previously accepting, the revocation is registered immediately, but the removal of Trendemon cookies will occur on the next page view.

 

Cross-Domain Tracking & Fingerprinting

As the digital landscape evolves, leading browsers like Safari and Chrome are phasing out support for legacy tracking methods (specifically third-party cookies). This shift makes it challenging to track a single visitor's journey as they move between your different web properties across multiple domains - for example, navigating from your main website (company_name.com) to your blog (blog.company_name.com).

To bridge this gap and ensure you retain a unified view of the visitor journey, Trendemon may utilize Fingerprinting in some cases (but not in the strict mode mentioned above). It essentially looks at various device and browser parameters to distinguish between different visitors. When used in combination with other points of data, such as time and IP, it can provide a more accurate representation of visitors.