# Items explore

The Items explore has one row for each item of every list your organisation maps as items, such as the products in a GA4 purchase.
For a store that captures purchases with Kontala's Shopify pixel, each line of the cart, of a line added or removed, of a checkout opened and of an order paid is a row too.

You have this explore when your organisation maps an item list in Data Capture, or captures a store's purchases.

## Good to know

- The rows are items, so a metric here adds up items.
  A page or event field, such as an order's value, is a dimension only, since adding it up over an order's items would count it once per item.
- **Item ID** is always text, so 00123 and 123 stay two items.
- An item list on a row that says no action, such as a promotion's, is here but not in the [Products](/docs/analytics/products) explore, which counts only ecommerce actions.

<!-- 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 Items explore, so its charts are the ones you build.

## Dimensions

The Items explore has 111 dimensions.

::field-table
| Dimension | Type | Description |
| --- | --- | --- |
| Item list | String | Which of the organisation's item lists the item came from, by the name it was given when the list was mapped, or which of a Shopify store's lists Kontala's Shopify pixel reported it in: Shopify cart, Shopify added to cart, Shopify removed from cart, Shopify checkout or Shopify order. |
| Position | Number | The item's position in its list, counting from 0. |
| Item ID | String | The identifier the list's mapping names: a SKU, a product id; for a Shopify list, the variant's id, whose SKU is Item SKU. Always text, so 00123 and 123 stay two items. |
| Item name | String | The item's name, as the list's mapping reads it. |
| Price | Number | The unit price the list states, in whatever currency the site uses. Null where the value is not a number. |
| Quantity | Number | The quantity the list states. Null where it states none. |
| Event | String | The pushed event whose payload held the item, or empty for an item read from the page's data layer. |
::

### 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 Items explore has 7 metrics.

::field-table
| Metric | Calculation | Description |
| --- | --- | --- |
| Items | Count | Item rows: every item of every list, however many of one product it names. |
| Units | Sum | The quantities the lists state, counting an item that states none as one. |
| Item revenue | Sum | Price times units, per item, in the site's own currency. Items without a numeric price add nothing. It is only revenue for lists that record sales, such as a purchase event's items. |
| Distinct items | Count distinct | Distinct items, by Item ID. |
| Rows with items | Count distinct | Page views and events whose data layer held at least one mapped item, and rows of Kontala's Shopify pixel carrying a line. |
| Unique visitors | Count distinct | Distinct device cookies among visitors with an item. Optimistic on Safari for the reason the page view explore gives. |
| Sessions | Count distinct | Distinct sessions with at least one item. |
::

## Your own fields

When your organisation maps data layer fields in Data Capture, they appear in the Items 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.
