Browse Analytics
Clicks explore
The Clicks explore has one row for every click and every form sent. What it covers, what to know when reading it, and every dimension and metric in it.
The Clicks explore has one row for every click on a link, a button or another control, and every form submitted without one, on a property with clicks turned on. On a store that captures purchases with Kontala's Shopify pixel, every step of a Shopify checkout that a shopper submits is a row too.
Each click has a Click type, which says what it did, such as Add to cart: the type the site declared, the first of your click type rules to match, or the answer of Kontala's model. See Page and click types.
Good to know
- A click has the dimensions of the page view it happened on, so you can slice clicks by path, page title, page type, country or channel exactly as page views.
- Element text keeps up to 255 characters, with anything shaped like an email address, a card number or a token removed, and is never read from form fields. Form values never stores passwords, card security codes, one-time codes or PINs.
- Bot traffic is left out, and a click without consent is never stored.
- Unique visitors counts device cookies, so it reads high on Safari.
Used on dashboards
Charts on these dashboards are built on the Clicks explore:
- Engagement: Do they stick?: Key elements
Dimensions
The Clicks explore has 130 dimensions.
The interaction
| Dimension | Type | Description |
|---|---|---|
| Interaction | String | A click, or a form submitted with no click before it: by the Enter key in a form with no button, or by the page's own code. Checkout step is a step of a Shopify checkout, submitted, as Kontala's Shopify pixel reports it. |
| Form submission | Boolean | Whether it sent a form: a click on a form's submit button, or a form submitted with no click before it. A search or login box submitted with Enter and no form around it is not one. A store's Add to cart is a form, so it counts; Click type tells them apart. |
| Input | String | What activated it. Keyboard includes the Enter key submitting a form through its button. Empty where the browser did not say, on a submit, and on a Shopify checkout's step. |
| Page region | String | The part of the page the element sits in: header, nav, main, aside, footer or dialog. |
| Declared type | String | The click type the site declared on the element with data-ac-event, such as add_to_cart, or Kontala's Shopify pixel declared for a Shopify checkout's step, such as checkout_contact_info_submitted. Empty where none was declared. |
The element
| Dimension | Type | Description |
|---|---|---|
| Element | String | The element the click resolved to: the button a click on its icon belongs to, a radio button a click on its label chose, or the form a submit came from. Empty on a Shopify checkout's step, which Kontala's Shopify pixel reports with no element, and so is every element column. |
| Element text | String | What the element says, up to 255 characters, with anything shaped like an email address, a card number or a token removed. Never read from form fields, choices or anything a site masks. |
| Element id | String | The element's id attribute. |
| Element classes | String | The element's class attribute. |
| Element name | String | The element's name attribute, as a form control carries it. |
| Element type | String | A button's or an input's type attribute: submit, button, radio. |
| Element role | String | The element's role attribute, such as button or tab. |
| Element label | String | The element's aria-label, which is what an icon button says to a screen reader. |
| Element path | String | Where the element sits in the page, up to eight elements from the nearest: main > div.product > form#buy > button.add. |
| Element attributes | String | Every attribute kept, as JSON, which a contains filter reads: data-sku, data-testid and the site's own. |
| Hit element | String | What was actually under the pointer, when it was not the element itself: the svg inside a button, the image inside a link. |
Where it leads
| Dimension | Type | Description |
|---|---|---|
| Link | String | Where a link leads, scrubbed by the same rules as the page's own URL. A mailto: or tel: link keeps its scheme alone. |
| Link hostname | String | The host a link leads to, read from Link. |
| Outbound link | Boolean | Whether the link leaves the site. Empty for a click that is not on a web link. |
| Form id | String | The form a submit, or a click on a submit button, belongs to. |
| Form name | String | The name attribute of the form a submit belongs to. |
| Form action | String | Where the form sends, scrubbed as a link is. |
| Search term | String | What a search looked for: the search box's value on a submit, a click on a search button, or Enter in a search box. |
| Form values | String | What the form held when it was sent, as JSON, name by name. Passwords, card security codes, one-time codes, PINs and anti-forgery tokens are never stored. |
Click type
| Dimension | Type | Description |
|---|---|---|
| Click type | String | What the click did: the type the site declared with data-ac-event, or Kontala's Shopify pixel for a checkout's step, else the first of the click type rules confirmed in Kontala to match, else the answer of the click type model where the property lets it answer. Unclassified when none says. |
| Click type source | String | Where Click type came from: Declared by the site or by Kontala's Shopify pixel, the kind of rule that matched - Form, Link, Markup, Text or Page - or Model. None when nothing did. |
From the Page views explore
Every row also has these 104 dimensions of the Page views explore, 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 Clicks explore has 4 metrics.
| Metric | Calculation | Description |
|---|---|---|
| Clicks | Count | Clicks and form submits, and the steps of a Shopify checkout Kontala's Shopify pixel reports. Bot traffic is left out, and a click without consent is never stored. |
| Unique visitors | Count distinct | Distinct device cookies among visitors who clicked. Optimistic on Safari for the reason the page view explore gives. |
| Sessions | Count distinct | Distinct sessions with at least one click. |
| Clicks per session | Ratio | Clicks per session. |
Your own fields
When your organisation maps data layer fields in Data Capture, they appear in the Clicks 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.