Skip to content
SilktideHelp

Views

A view is a named slice of the visits Analytics has recorded. Hosts that send data appear here on their own. An analytics admin can also make views from hostnames and rules, at the top level or nested inside another view, and decide who can see each one.

Manage views under Analytics → Settings → Views. Privacy, data, and install sit in the same settings area. The list starts with All websites, everything this account collects, then shows each view under the one it sits inside. A badge says where each view came from:

  • Auto-discovered - a hostname that sent data. You can rename, move, or hide it, but its hostname is fixed. To combine hostnames or add rules, make a new view.
  • Custom - a view someone on your team made.
  • Legacy - a view kept from an older property and segment, which decide where it sits and what it covers. It counts only visits recorded by that property's own tracking code. Once a site sends data through the Silktide Script instead, the legacy view keeps its history, and new visits appear in the site's auto-discovered view, or in a view you made for it.

What you can do

  • New view makes a view at the top level, and Add view inside on a row makes one inside that view.
  • Rename a view so the Analytics picker uses the name your team already uses.
  • Turn off Visible to hide a view you do not need in the picker. The data stays and links to it keep working; it just stops appearing as a choice.
  • Open a view to change its name, where it sits (Inside), what it covers, and whether it shows in the picker (Show in the view picker).
  • Remove AI optimizer takes back a view's so you can use it on another view. It is on the view's own settings when the view has one. The weekly AI report for that view stops; what it has already written stays.
  • Delete a view your team made when you no longer need it. Its goals, funnels, and AI reports are deleted with it, and views inside it have to be moved or deleted first. Hosts that arrived because they sent data stay until you hide them.

Switch views from the Analytics picker. Goals, reports, and the Inspector's Analytics families follow the view you have open.

What a view covers

A view you make is defined by Hostnames, Rules, or both, and needs at least one hostname or one rule.

  • Hostnames - one per line, such as www.example.com. Leave it empty for a view defined by rules alone.
  • Rules - each rule names something about a page view, how to compare it, and a value, such as URL starts with /aerospace. Choose Add rule for each one. A view can have up to 20 rules.

Rules can use:

  • the page: Hostname or URL. For a page address, start the value with / to match that path on any host, or give the full address to match one site.
  • where the visitor was: Country or Region
  • their browser and device: Browser, Browser width, Operating system, Language, or Color scheme
  • their accessibility preferences: Pointer, Touchscreen, Reduced motion, Contrast, Forced colors, or Reduced transparency
  • where the visit came from: Source, Medium, Campaign, Term, Ad content, or Referrer

Every rule can use is or is not. Addresses and where the visit came from can also use contains or starts with, and browser, operating system, and country can use contains. Browser width takes a number of pixels, with is, is not, is more than, or is less than. There is no rule for the kind of device, so use browser width for that: Browser width is less than 768, for example.

Each rule narrows the view further. A visit is in the view when at least one of its page views matches every rule of the view and every rule of the views above it. Landing page, exit page, event, and outgoing link are not offered, because they describe a whole visit rather than a page view. Use them as filters instead.

Views inside views

A view only ever sees what the view above it sees, so a nested view includes only traffic that also matches every view above it.

  • When the view above it lists hostnames, a nested view can use only hostnames from that list. Leave its hostnames empty to keep all of them.
  • Moving a view with Inside moves the views inside it too.
  • Views can only nest so deep. A view at the deepest level offers no Add view inside, and Inside lists only the views a view can move into.

A view also lists the goals, funnels, AI reports, and tasks of every view inside it, so All websites shows every view's. On Goals and Funnels, one that belongs to a view further down is marked with that view's name, such as In Aerospace, and opens in that view, where it can be changed.

Who can see it

Open a view to see Who can see it. Access to a view is granted on a role, alongside every other permission that role carries. Everyone with account-wide analytics access can already see every view, and anyone who can see a view can also see the views inside it.

Manage roles opens Roles.

Last updated

Was this page helpful?