Analytics settings
Analytics settings live under Analytics itself. They decide which views the picker offers, how much of a visitor may be remembered, how the script records what it sees, what your stored values are called, and how the script is installed. Privacy and Data apply to every site the Silktide Script is on, and saving updates the script automatically. 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 consents. 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 consents, collect sets the level for visitors who consent to analytics. 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 the Silktide Consent Manager, or any banner that supports Google Consent Mode. On a website with neither, every visitor stays at the level you picked.
Under Cookies, Remember a visitor for sets how long a returning visitor is recognized at the levels that use a cookie: 30 days, 90 days, 180 days, 1 year, or 2 years.
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.
- Basic - counts every page view and tracks no visitor. Page views and events are counted with no visitor ID, but visitors, sessions, journeys and traffic sources are unavailable. If you chose search boxes, what people search for is kept too, and people can type personal details into a search box.
- Cookie-free - recognizes a visitor for a day. No cookies. A privacy-safe fingerprint stands in for the cookie, so no report is unavailable, but visitors and returning visitors are estimates: a fingerprint isn't unique to one person the way a cookie is. People who share a network and a browser, in an office or on a campus, can count as one visitor; see Why do some visits have no duration?
- Complete - remembers returning visitors, with a cookie. 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 shapes what the Silktide Script records:
- Linked domains lists other domains you own. Follow a visitor between your domains decides whether a visitor who moves between them stays one visit: Across every linked domain, Only links you tag (links marked
data-st-xdomain), or Never. It never links a visitor to a site you do not measure. - Ignore these IP addresses keeps visits from those addresses out of Analytics entirely, typically your own offices. Enter one IP address or range per line.
- Ignore #fragments in URLs counts
#sectionlinks as the same page. Turn it off only for a single-page app that moves between screens by fragment. - Query parameters decides what happens to a parameter in a recorded address: Remove from URLs, Keep in URLs, Log only, or read it as the visit's Campaign, Medium, Source, Search term, or Ad content. Removing tracking noise such as
fbclidstops one page splitting into many. - File extensions counted as downloads decides which links count on Downloads.
- Site search names your site's own search boxes, one CSS selector per line, so the Site search screen can show what people search for. Silktide records nothing anyone types until you list a box there, and never anything typed into another field. Only text and search boxes are recorded, never passwords or email addresses. Describe your results page there as well, and Silktide also records which searches found nothing. See Read searches from your results page.
Known bots are kept out of your reports by default. See them on Bots.
Install
Install is how data starts flowing. Copy the account Silktide Script and place it in the <head> of every page you want measured; the same snippet works on every site you own. Decide what to collect on Privacy first, because consent levels apply from the first page view.
There is nothing to register. Within a few minutes of the first visit, each site sending data appears as a view in the picker at the top of Analytics.
If a site was measured in Silktide 4, new visits stop reaching its Silktide 4 property once this script is on the site, even if the old tracking code is still there too. The history the property already collected stays, in Silktide 4 and in its Legacy view, and new visits show in the site's view. See Views.
Page speed
The Silktide Script is non-blocking: installed as shown, it does not block or slow down any part of your page load, however many pages it is on. The snippet loads the script with defer, so:
- the browser keeps reading and showing your page while the script downloads alongside it;
- the script only runs once the page's HTML is ready;
- browsers keep a copy, so a visitor moving between your pages does not usually download it again.
Paste the snippet exactly as it is. Removing defer, or loading the script some other way, can make it hold up your page.
Content Security Policy
If your site sends a , the policy has to allow the Silktide Script. Otherwise the browser blocks it: your pages keep working, but their visits never reach Analytics. Add these to your policy:
script-src-https://scripts.silktide.com, where the Silktide Script loads from.connect-src- the address for your account's region, where the script sends what it records:https://a.eu.silktide.com,https://a.us.silktide.comorhttps://a.au.silktide.com. If you're not sure which region your account is in, ask your Silktide contact, or allow all three.
The second part of the snippet is a short inline script. If your policy does not allow inline scripts ('unsafe-inline'), give it a nonce or a hash, the same way you allow your own inline scripts.
A policy written for Silktide 4's tracking code allows analytics.silktide.com. The Silktide Script loads from scripts.silktide.com instead, so add that too.
When the policy blocks something, your browser's developer console shows a Content Security Policy error naming the blocked address.
Labels
Labels gives the values Analytics stores a name your team recognizes: "Higher-ed ebook, round 1" for the campaign higher_ed_ebook_R1, or "Newsletter sign-up" for the event newsletter_signup. Pages, campaigns, ad content, search terms, sources, mediums, and events can all be named. A name applies across your account and shows everywhere in Analytics in place of the stored value. Filters, exports, and links keep using the value itself.
An analytics administrator can add a name here, or from Give it a name… in a row's menu on any list. Suggested names lists names an AI run has proposed for values that have none: accept one to save it, or decline it.
Related
- Analytics
- Views
- Consent - how your traffic splits across the consent levels
- Preferences - what visitors' devices asked for, once collection is running
- Bots - the visits by known bots that your reports leave out