Skip to content
SilktideHelp

Audience

Audience reports describe visitor location, technology, and how people have asked their devices to present the web.

Screens

  • Locations groups visitors by country and region where that information is available.
  • Languages shows the languages visitors' browsers ask for, and whether you publish in them.
  • Browser sizes shows dimensions observed during visits.
  • Browsers compares browser families.
  • Operating systems compares device operating systems.
  • Preferences shows light and dark appearance, touch versus mouse, and accessibility settings such as reduced motion and contrast.
  • Consent shows how your page views split across the consent levels they were collected under, and what each level leaves out of the reports.
  • Bots shows the visits by known bots and AI agents that every other report leaves out: how many, whether that is growing, and which pages they read.

Use these reports to prioritize testing and design decisions, not to exclude less common users. Small audience segments can still include important customers or people who face disproportionate barriers.

Location is inferred and may be imprecise. Browser and operating-system labels depend on information reported by the visitor's software.

How these screens work

Locations, Languages, Browser sizes, Browsers, and Operating systems are built the same way:

  • Each opens with Visitors: the visitors the table at the foot of the screen counts, added up, so the figure and the rows always agree. With Compare on, it shows the change from the previous period.
  • The link under the figure, such as How browsers are identified, opens this page.
  • Select a country, language tag, browser, or operating system to filter every Analytics screen to it.
  • They count visitors, so traffic collected at Basic is not in them. When part of the period was collected at Basic, Visitors carries the amber mark explained on Consent. When almost all of it was, a note replaces the charts to say visitor counts are unavailable. The table stays.

Locations

Locations shows where visitors were browsing from.

  • Visitors names the places most visitors came from, beside a world map with every visited country shaded. The United States, Canada, and Australia are shaded state by state, and the United Kingdom by its four countries.
  • Point at a place on the map to see its name and visitors. Choose a country on the map, under the figure, or in the table to see its regions: the map moves to that country and the table lists its regions. All countries goes back.
  • Map in the option band chooses how the map is drawn: Wireframe, Earth, or Globe.
  • The Countries table lists the visitors and page views from each country. Visitors whose country could not be worked out are left out of the screen.

Languages

Languages shows the languages visitors ask for, whether you publish in them, and where those visitors are.

Every browser tells websites which language its user prefers, as a language tag such as en-US (English, United States) or fr-CA (French, Canada). Analytics reads the language a visitor's browser asks for from its Accept-Language header, and counts visitors by it.

  • Languages asked for groups the tags by language, so en-US, en-GB, and en-AU add up under English, with each tag and its visitors on the line beneath. Smaller languages are added together as Other.
  • Languages you publish in sets your visitors' languages against the languages your pages are written in, which Governance measures with its Readability check (How languages work). A bar splits visitors into A language you publish in and Another language, and Largest audiences with no pages in their language lists the biggest languages you have no pages in, with their tags. Open Readability opens that check.
    • It needs a view tied to one monitored website. Any other view says there is no website to compare against.
    • Until the Readability check has run, it says no page languages have been measured yet.
  • Where they are shows the countries that visitors asking for one language tag browse from. Choose the tag with Language. It opens on the busiest tag you have no pages in, when there is one. Open Locations opens Locations filtered to that tag.
  • The Language tags table lists every tag. When the website's languages are known, On this site says whether it has pages in that language: Has pages or No pages.

Browser sizes

Browser sizes shows the windows visitors browse in: how wide, how tall, how sharp, and whether that mix is shifting.

A size is the browser window's , not the whole screen, so a desktop browser that is not maximized reports the size of its window. Width is read on the visitor's first page.

  • Visitors splits visitors into Mobile, Tablet, and Desktop by the width of their window, not by the device itself. A window 425 px wide or narrower counts as a phone.
  • Where windows fall charts visitors across the seven width bands the table uses, each bar colored by device class. The note under it says where most windows fall and how many visitors are on phones.
  • Device mix over time shows visitors per day on phones, tablets, and desktops, and says how much of your traffic is mobile and whether that changes on weekends.
  • Above the fold shows how much of a page shows before anyone scrolls (the part ), and how sharply it is drawn:
    • Window height puts visitors into three groups: under 700 px, 700 to 950 px, and over 950 px tall.
    • Pixel density shows how many screens draw at 1×, 1.5×, 2×, and 3× and up. A 2× screen packs twice as many pixels into the same space, so images need a 2× version to look sharp on it. The note under the bar says how many screens that is.
  • The table has four tabs: Width, Height, Width and height, and Pixel density. Show heights and Show pixel densities under Above the fold open those tabs.

Browsers

Browsers shows which browsers to support, how far behind their users are, and what in the mix is not an ordinary browser.

A browser is identified by the name its user agent gives, the description of itself it sends to every website. Visitors whose browser could not be identified are counted in Visitors but left out of the running total, and the description under the figure says how many there were.

  • Support coverage folds browsers into the families you would test on: Chrome, Safari, Edge, Firefox, In-app browsers, and Other browsers, with the browsers in each listed under its name. Each family shows its visitors, its Share, and Covers, the running total of identified visitors down to that row. A note names the browsers to test on and how many of your identified visitors they cover, and marks that row with a check.
  • Inside another app lists the browsers built into other apps, such as the one a social media app opens links in. Each is marked with the kind of app it runs in, such as Android apps or iPhone and Mac apps. The note says how many visitors arrived in one: downloads, cookie consent, and some CSS behave differently there, so they are worth testing. Not a person lists browsers driven by a script rather than a person.
  • Versions in use shows which versions of one browser visitors run, newest first, with older versions grouped together. Choose Chrome, Safari, Edge, or Firefox with Browser. A note says how many visitors are two or more releases behind, and why: Chrome, Edge, and Firefox update themselves, so those visitors are mostly on machines where updates are held back, while Safari updates with the operating system.
  • The Browsers table lists every browser. Kind marks the ones that are In-app, Automated, or Not identified.

Operating systems

Operating systems shows which platforms visitors are on, which browser they pair it with, and how far behind the versions run.

The operating system is the one the visitor's browser reports. Visitors whose browser sent none sit outside the families, appear as Unknown in the table, and are counted in the description under Visitors.

  • Visitors splits identified visitors into Desktop and Mobile, each with its share and its own bar of systems, so you can see that a site is mostly Windows on desktop and mostly iOS on phones at the same time. A system that is neither appears under Other systems. Select a system in a bar to filter every Analytics screen to it.
  • The note under the families gives the split between the two biggest phone systems, such as "On phones, iOS outnumbers Android 62:38". With Compare on, it also says whether that gap widened, narrowed, or flipped since the previous period.
  • Pairs people actually use lists operating systems and browsers together, such as Chrome on Windows, which is what a test plan is made of. Running total shows how much of your audience the pairs down to each row cover.
  • Versions in use shows which versions of one system visitors run. Choose the system with System. It opens on iOS, where the version decides what Safari supports, and says how many visitors, if any, are on iOS 15 or older, where Safari has no container queries. Some systems do not report their real version, and the card says so:
    • Browsers on a Mac report 10.15 on every later version of macOS.
    • Windows 11 reports itself as Windows 10, so the two are counted together.
    • Chrome, and browsers built on it such as Samsung Internet, report every Android version as 10. Those visits are shown apart.
  • The Operating systems table has a Family column for each system.
  • Consent - what each consent level leaves out of these reports
  • Bots - the visits every report here leaves out
  • Analytics settings - privacy, data, and install
Last updated

Was this page helpful?