Analytics settings
Analytics settings live under Analytics itself. They decide which views the picker offers, how much of a visitor may be remembered, which traffic is recorded, and how the script is installed. Changes apply from the moment you save. Data already collected is not rewritten.
Views
Views are the named slices of your traffic. Hosts appear automatically once they send data. An admin can also create a view, nest it inside another, rename, hide, or delete a view they made.
Privacy
Privacy asks what Analytics should collect before a visitor agrees. The consent levels sit side by side, each showing what your reports can tell you at that level, and you pick one.
Under the table, After a visitor agrees, collect sets the level for visitors who have agreed. You can choose the level you picked or anything above it; the levels below it can't be chosen. There is nothing to switch on: the Silktide Script picks up a visitor's consent from Google Tag Manager or Silktide's consent banner. On a website with neither, every visitor stays at the level you picked. Cookie settings sit on this same screen.
The levels, and what each one costs you in the reports:
- Nothing - collects nothing; the script blocks every event before it leaves the page. Every report is unavailable for this traffic.
- Page views only - counts page views and events, identifying no visitor, even anonymously. Visitors, sessions, journeys and traffic sources are unavailable.
- Cookie-free visitors - recognises a returning visitor from a privacy-safe fingerprint, setting no cookie. No report is unavailable, but returning visitors are an estimate: a fingerprint isn't unique to one person the way a cookie is.
- Full analytics - sets a cookie so visits, journeys and funnels follow one visitor over time. Nothing is unavailable.
The table also marks which levels you use and shows the share of the last 30 days of page views collected at each, so the setting and the data stay honest with each other. The Consent report shows the same split for any date range and view.
Data
Data decides which events count at all: whether known bots are included, whether #fragments in URLs are ignored, optional URL prefixes to record, IP addresses to ignore, and which file extensions count as downloads.
Install
Install is how data starts flowing. The account Silktide Script is the usual snippet. The screen also shows whether anything has arrived yet.
Related
- Analytics
- Views
- Consent - how your traffic splits across the consent levels
- Preferences - what visitors' devices asked for, once collection is running