# Checkout explore The Checkout explore has one row for every checkout opened, every step of one submitted and every order paid, as Kontala's Shopify pixel reports them, on a property with purchases turned on. Its rows come only from the Shopify pixel, so the explore is empty for a site without it. The same rows are page views and clicks in the [Page views](/docs/analytics/page-views) and [Clicks](/docs/analytics/clicks) explores; here they are the stages of a checkout. See [Shopify checkout](/docs/data-capture/shopify-checkout) to set the pixel up. ## Good to know - Each row's **Page type** is Checkout or Order confirmation, as the pixel declares it. - You can slice an order by the channel, campaign, entrance, country or device of the visit it was paid in, using the page view dimensions. - The rows hold nothing about the buyer. ## Used on dashboards None of the ready-made [dashboards](/docs/analytics/dashboards) is built on the Checkout explore, so its charts are the ones you build. ## Dimensions The Checkout explore has 116 dimensions. ::field-table | Dimension | Type | Description | | --- | --- | --- | | Stage | String | How far through the checkout this row is: opened, a step submitted, or paid. Grouped with Sessions and sorted by Stage order, the checkout's funnel. | | Stage order | Number | Where the stage falls in a checkout, from 1 for opened to 6 for paid, to sort Stage by. | | Order ID | String | The order a purchase paid for, as Shopify numbers it in its admin. Empty on a checkout opened and on its steps. | | Counts as a purchase | Boolean | True on the one row that counts an order. An order reported twice, as a reloaded thank-you page can, counts on its first report alone. | | First order | Boolean | Whether the order was the buyer's first with the store, as Shopify knows them. Empty where Shopify did not say, and on a checkout that was not paid. | | Currency | String | The currency the checkout was priced in, which the buyer chose where the store sells in several. Group by it before reading a sum: amounts in two currencies do not add up. | | Value | Number | What the checkout came to at this stage, taxes, shipping and discounts included, in its currency; on a purchase, what the order was paid. | | Subtotal | Number | The lines before shipping and taxes, in the checkout's currency. | | Tax | Number | The taxes on the lines and the shipping, in the checkout's currency. | | Shipping | Number | The shipping chosen, in the checkout's currency. Empty until the buyer chose one. | | Discount | Number | What the checkout's discounts took off, in its currency. | | Units | Number | How many units the checkout held, every line's quantity added up. Empty on a step, which does not say. | :: ### 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 Checkout explore has 9 metrics. ::field-table | Metric | Calculation | Description | | --- | --- | --- | | Sessions | Count distinct | Distinct sessions that reached the stage in question. Grouped by Stage, the checkout's funnel, one visit counted once at each stage it reached. | | Sessions that opened a checkout | Count distinct | Distinct sessions in which a checkout was opened, however often. | | Sessions with a purchase | Count distinct | Distinct sessions in which an order was paid. | | Checkout conversion rate | Ratio (%) | The share of sessions that opened a checkout which went on to pay for an order. | | Orders | Count distinct | Orders paid, each once however often it was reported. | | First orders | Count distinct | Orders that were their buyer's first with the store, as Shopify knows them. | | Revenue | Sum | What the orders were paid, taxes, shipping and discounts included. Group by Currency where the store sells in more than one: it adds up amounts as they are, whatever their currency. | | Average order value | Ratio | Revenue over Orders, in the orders' currency; grouped by Currency for the reason Revenue gives. | | Units sold | Sum | Units in the orders paid, every line's quantity added up. | :: ## Your own fields When your organisation maps data layer fields in Data Capture, they appear in the Checkout explore too: the standard fields under **Standard fields** and your own under **Data layer**. They are left out of the lists above, because every organisation maps its own.