# Data layer events explore

The Data layer events explore has one row for every event a site pushed to a data layer that Kontala captures, such as an add_to_cart, a purchase or a form submission.
Each event carries your page fields, read from the page it happened on, and your event fields, read from the event itself.

You have this explore once your organisation maps a field read from pushed events.
See [Existing tags and data layers](/docs/data-capture/existing-tags-and-data-layers) for how fields are mapped.

## Good to know

- An event has the dimensions of the page view it happened on, so you can slice events by path, country or channel exactly as page views.
- Bot traffic, and events from visitors who did not consent, are left out.

<!-- GENERATED: everything below is written by scripts/explore-reference.mjs from autocapture 69662e2. Edit the explanation above it, and rerun the script to refresh this part. -->

## Used on dashboards

None of the ready-made [dashboards](/docs/analytics/dashboards) is built on the Data layer events explore, so its charts are the ones you build.

## Dimensions

The Data layer events explore has 106 dimensions.

::field-table
| Dimension | Type | Description |
| --- | --- | --- |
| Event | String | The event name the site pushed, as its data layer spells it: purchase, add_to_cart. Characters outside letters, digits, spaces and . : @ $ / + - _ are stored as underscores. |
| Data layer | String | Which of the organisation's configured data layers the event was pushed to, by the name the capture rules give it. |
::

### From the Page views explore

Every row also has these 104 dimensions of the [Page views explore](/docs/analytics/page-views#dimensions), which mean the same here and are described there:

- **Time**: Event time, Ingest time
- **The visitor**: Visitor type, Days since first visit
- **The visit**: Entrance page, Entrance hostname, Session page views, Single-page session, Session number
- **Scroll depth**: Scroll depth (%), Scroll depth band
- **Page speed**: LCP (ms), LCP rating, INP (ms), INP rating, CLS, CLS rating, FCP (ms), FCP rating, TTFB (ms), TTFB rating, Speed rating, Load or route, LCP element, INP element
- **Friction**: Friction measured
- **Page**: Path, Section, Subsection, Page title, Hostname, Site domain, Query string, Referrer host, Referring domain
- **Attribution**: Campaign source, Campaign medium, Campaign, Campaign term, Campaign content, Click ID source, Has click ID
- **Attribution carried across the visit**: Session campaign source, Session campaign medium, Session campaign, Session click ID source, Session referring domain, Session referrer host, Session campaign term, Session campaign content, Channel
- **First touch**: First-touch channel, First-touch source, First-touch medium, First-touch campaign, First-touch referring domain
- **Geo**: Country, Country name, Continent, Region, City, Geo source
- **Network**: ISP, ASN, Datacenter traffic, Cellular
- **Browser environment**: Language, Language code, Language name, Device class, Screen resolution, Viewport size, Timezone offset (min)
- **The visitor's own clock**: UTC offset, Local hour of day, Local day of week, Local day of week number
- **Browser, operating system and device**: Browser, Browser version, Operating system, Device type, User agent
- **An app**: Platform, Shown in app, App version, App build, OS version, Device model, SDK version
- **Data source and quality**: Tenant, Site, Allowed origin, Origin, Tag, Tag version, Collector version, Delivery mode
- **Signed-in user**: Signed in, Organisation, Company domain, Global Privacy Control, Scrubbed parameters
- **Page type**: Page type, Page type source

## Metrics

The Data layer events explore has 4 metrics.

::field-table
| Metric | Calculation | Description |
| --- | --- | --- |
| Events | Count | Pushed data layer events. Bot traffic and consent-denied rows are already left out. |
| Unique visitors | Count distinct | Distinct device cookies among visitors who pushed an event. Optimistic on Safari for the reason the page view explore gives. |
| Sessions | Count distinct | Distinct sessions with at least one pushed event. |
| Events per session | Ratio | Data layer events per session. |
::

## Your own fields

When your organisation maps data layer fields in Data Capture, they appear in the Data layer events explore too: the standard fields under **Standard fields** and your own under **Data layer**.
Each one can carry the metrics chosen when it was mapped, named after it, such as **Order value (total)**: a total, average, lowest, highest or median for a number, a count of distinct values for text, and a count of true for a true-or-false field.
They are left out of the lists above, because every organisation maps its own.