Automatic Data Layer Mapping
Track faster with your existing website setup
JENTIS can automatically detect and map standard behavioral and e-commerce events from your website’s existing data layer during new container creation.
This means you can start collecting relevant tracking events immediately without rebuilding your data layer, writing custom bridge logic, or manually configuring every event from scratch.
In short: JENTIS uses your existing tracking setup and translates standard events into the JENTIS schema automatically.
Why this matters
Many websites already have a data layer in place. It may be used by tools such as tag managers, analytics platforms, or e-commerce integrations.
Previously, using this data in JENTIS often required a technical setup step:
defining how the existing data layer should be read,
mapping existing events to JENTIS events,
configuring values and parameters,
validating the setup manually,
and often involving developers or implementation specialists.
Automatic Data Layer Mapping reduces this friction.
Instead of treating JENTIS onboarding as a migration project, JENTIS can work with your existing setup from the beginning.
What JENTIS detects automatically
During container creation, JENTIS checks whether standard behavioral or e-commerce events are available on the website.
When supported events are detected, JENTIS creates mappings into the JENTIS schema automatically.
Typical examples include:
Behavioral events
Page views, clicks, form interactions
E-commerce events
Product views, add to cart, checkout steps, purchases
Data layer values
Product IDs, product names, prices, quantities, order values
The exact detected events depend on the data layer implementation available on the website.
How it works
1. Create a new container
When you create a new container, JENTIS analyzes the website setup and checks for existing data layer structures.
You can check how to create a container here: Create a Container
2. JENTIS detects standard events
JENTIS identifies supported events and values that can be mapped into the JENTIS tracking schema.
This allows the container to start with useful event mappings instead of an empty technical configuration.
3. Events are mapped automatically
Detected events are translated into the JENTIS schema.
For example, an existing e-commerce purchase event can be mapped to the corresponding JENTIS purchase event, including relevant order and product data.
4. Review and adjust mappings
The DCP lists the created mappings so users can review them before or after activation.
Users can:
preview mapped events,
disable mappings that should not be used,
adjust existing mappings,
extend the setup with additional mappings,
validate whether the captured data matches expectations.
[Screenshot placeholder: Mapping list with preview, edit, disable actions]
Benefits
Faster onboarding
New containers can start tracking key events immediately. This reduces setup time from days or weeks to a much shorter onboarding flow.
Less technical implementation effort
Users do not need to manually recreate standard tracking logic that already exists on the website.
Easier migration from existing setups
JENTIS can work with the customer’s existing data layer. This reduces the feeling of a technical migration and makes adoption easier.
Better first-time experience
Users can see data flowing earlier, validate the setup faster, and understand the value of JENTIS sooner.
Full control after setup
Automatic mappings are not a black box. They can be reviewed, disabled, edited, or extended in the DCP.
Who is this feature for?
Automatic Data Layer Mapping is useful for teams that already have tracking structures on their website and want to activate JENTIS without a heavy implementation project.
It is especially helpful for:
marketing teams that want faster time to value,
analytics teams that want to validate data quickly,
implementation teams that want to reduce repetitive setup work,
agencies or consultants onboarding multiple customers,
sales and proof-of-concept scenarios where “works out of the box” behavior is important.
User control and customization
Automatic mapping gives you a starting point. You remain in control of the final tracking setup.
After the mappings are created, you can manually adapt them in the DCP.
Preview
Check which events and values JENTIS detected
Disable
Turn off mappings that should not be used
Edit
Adjust how an existing event is mapped
Extend
Add further mappings for custom business logic
Validate
Confirm that event data is captured as expected
Important notes
Automatic Data Layer Mapping is designed to cover standard and commonly used event structures.
Custom or highly specific tracking logic may still require manual mapping or additional configuration.
The feature is intended to reduce implementation effort, not remove the need for validation. We recommend reviewing the generated mappings before using them in production reporting or activation workflows.
Summary
Automatic Data Layer Mapping helps JENTIS work with your existing website tracking setup from the start.
It reduces technical setup work, accelerates onboarding, and makes it easier to activate tracking without treating the implementation as a migration project.
With automatic detection, generated mappings, and full control inside the DCP, users can start faster while still keeping the flexibility to adapt the setup to their needs.
Last updated
Was this helpful?