Set up GTM Data Layer

Overview: Data Layer Integration Approaches

When integrating tracking with JENTIS, the recommended and most robust method is using the JENTIS Data Layer. This approach ensures consistency, performance, and ease of maintenance across all tracked events and objects on your site.

However, we understand that in certain scenarios—especially on sites with legacy setups or third-party dependencies—access to the JENTIS Data Layer may not be immediately feasible. In such cases, bridging from the existing website's Data Layer becomes a practical solution.

This overview outlines two supported bridge approaches in JENTIS:

Preferred: Bridge via Code Snippet

This method adds a code block (JavaScript snippet) to your JENTIS Tag Manager container, which automatically translates Enhanced Ecommerce objects pushed to the global window.dataLayer (typically used with Google Tag Manager) into JENTIS-native tracking commands.

Key Advantages

• No need to rewrite existing tracking logic

• Supports most Enhanced Ecommerce actions

• Activates the JENTIS default state (JENTIS Data Layer Send)

• Avoids reworking triggers and tags across the platform

GA4 E-Commerce Data Layer Bridge (GA4 to JENTIS)

Enhanced E-Commerce Data Layer Bridge (GTM to JENTIS)

Alternative: Bridge via JENTIS State (Option A)

This method involves creating a JENTIS State that observes specific dataLayer.push events and activates a custom state in JENTIS. This allows full control over when to trigger tracking, based on your existing Data Layer activity.

Key Advantages

• Tailored for specific events (e.g. gtm.init, custom.eventName)

• Can use event object data directly for variables

• Ideal when not relying on standard Enhanced Ecommerce schemas

Enhanced E-Commerce Bridge via JENTIS State

Recommendation

🚀 Always aim for native usage of the JENTIS Data Layer.

It is the most efficient, predictable, and future-proof approach for tracking across all types of websites and tools.

But if you must work with an existing window.dataLayer setup, we recommend starting with the Bridge via Code Snippet method due to its ease of implementation and minimal maintenance effort.

Use the Bridge via JENTIS State if you have:

• Custom event models

• Non-standard data structures

• Strict timing or race condition handling requirements

Both solutions are fully supported and can be implemented side-by-side with a full migration path toward the JENTIS-native model.