Skip to content
Docs
Browse Analytics

Swipes explore

The Swipes explore has one row for every swipe through a carousel or gallery. What it covers, what to know when reading it, and every dimension and metric in it.

The Swipes explore has one row for every sideways swipe, such as through a carousel or a gallery, and every up or down swipe the site's own code handled, on a property with scroll and swipes turned on. A vertical swipe that scrolled the page is scrolling, which Scroll depth measures in the Page views explore, and never a row here.

Good to know

  • A swipe has the dimensions of the page view it happened on, so you can slice swipes by path, page title, country or channel.
  • A swipe's element is described as a click's is, except that its text is never kept.
  • Swipes have no click types: those say what a click did, and belong to the Clicks explore.

Used on dashboards

None of the ready-made dashboards is built on the Swipes explore, so its charts are the ones you build.

Dimensions

The Swipes explore has 118 dimensions.

The swipe

DimensionTypeDescription
DirectionStringThe way the finger moved. Left and right are every sideways swipe; up and down are only the swipes the site's own code took, since any other is scrolling.
EffectStringWhat the swipe did. Page moved: the page itself scrolled. Scroller moved: a scroller the finger was on moved, such as a row of cards that snaps. Handled by the site: the site's own code took the swipe, as a carousel script does. Nothing responded: nothing moved and no script took it, often on an image visitors expect to be a gallery.
Distance (px)NumberHow far the finger travelled in the swipe's direction, in CSS pixels.
Duration (ms)NumberHow long the swipe took, from the finger's touch to its lift, in milliseconds.
Page regionStringThe part of the page the element sits in: header, nav, main, aside, footer or dialog.

The element

DimensionTypeDescription
ElementStringThe element the swipe was on: the scroller that moved, else the element the site's own code took it on, else the link or button the finger was on, else what the finger touched.
Element idStringThe element's id attribute.
Element classesStringThe element's class attribute.
Element nameStringThe element's name attribute, as a form control carries it.
Element typeStringThe element's type attribute, where it has one, such as a button's.
Element roleStringThe element's role attribute, such as button or tab.
Element labelStringThe element's aria-label, which is often what a carousel calls itself to a screen reader.
Element pathStringWhere the element sits in the page, up to eight elements from the nearest: main > section.gallery > ul.slides.
Element attributesStringEvery attribute kept, as JSON, which a contains filter reads: data-sku, data-testid and the site's own.

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 Swipes explore has 4 metrics.

MetricCalculationDescription
SwipesCountSideways swipes, and the up and down swipes the site's own code took. Bot traffic is left out, and a swipe without consent is never stored.
Unique visitorsCount distinctDistinct device cookies among visitors who swiped. Optimistic on Safari for the reason the page view explore gives.
SessionsCount distinctDistinct sessions with at least one swipe.
Swipes per sessionRatioSwipes per session.

Your own fields

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

Was this helpful?