Skip to main content
TayStack

Troubleshooting

No data in the dashboard? Ad blockers, domain mismatch, localhost, CORS and what the ingest endpoint answers.

Nothing in the dashboard

  • Check the snippet: both data-website-id and data-domain must be there, or the script silently does nothing.
  • Look for the POST to /api/events as described in the Quick start. No request means the script did not run or sent nothing: see the points below.
  • Only the visitors-now count updates by itself (about every 15 seconds). Refresh the rest of the dashboard.

Ad blockers

Some ad and privacy blockers stop analytics scripts or requests. If a blocked request shows in the Network tab, or nothing is requested at all, try a private window with extensions off. The script cannot work around a blocker and fails silently. Serving it from your own domain may help: Proxy setup.

Automated browsers

Browsers driven by automation tools (Selenium, Puppeteer, Playwright and similar, which set navigator.webdriver) are not counted: the script sends nothing and sets no cookies there. Test your install in a normal browser window.

Domain mismatch

  • The script only sends events when the page's hostname is your data-domain, its www. form or a subdomain. Otherwise nothing is sent.
  • The server also compares the hostname of each event with the domain registered for the site. A mismatch is logged on the server and the event is still stored. It is not rejected, so you will not see an error.

localhost is not tracked

Pages on localhost, 127.0.0.1 and [::1] send nothing unless the script tag has data-allow-localhost="true". Remove that attribute before you deploy, or your test visits are counted.

Exclude your own visits

To stop counting your own browser, open any page of your site with ?taystack_ignore=true added to the address, for example https://example.com/?taystack_ignore=true. The script saves a flag in that browser's localStorage. Open ?taystack_ignore=false to turn tracking back on. The parameter is never sent to TayStack: it is removed from the page address in the event and nothing else in the address changes.

You can also set the flag by hand in the browser console: localStorage.taystack_ignore = 'true'. Remove it with localStorage.removeItem('taystack_ignore'). Only the exact value true excludes the browser.

  • While the flag is set, the script sends no events at all (pageviews, custom events, identify, outbound and download events) and sets no cookies.
  • It only affects that browser on that site's domain. Repeat it on every browser and device you use, and clearing site data removes the flag. If the browser blocks localStorage, the flag cannot be saved and your visits are counted.

Set the time zone of your reports

Each site has a time zone, UTC until you choose another. It decides what today means: the Today, 7 days, 30 days and 90 days ranges, custom dates, and the day, week and month buckets of the chart all start at midnight in that zone, and weeks start on Monday. Pick it when you add a site (it starts on your browser's zone) or change it later in the site's settings, in the Timezone card. It changes how stored events are grouped into days, not the events themselves. The Recent visitors profile shows its times in the same zone, and the live "online now" view always looks at the last five minutes.

Exclude paths, hostnames and countries

In a site's settings, the Exclusions card lists traffic TayStack should not count. A visit that matches is dropped by the server and never stored. The script still gets the usual 202 answer, so nothing on your page can tell.

  • Paths start with /. They match exactly, or as a prefix when they end in *, for example /admin/*. It is the same rule as a page goal, and case matters. A path has no ? or #. A trailing slash does not matter: /admin matches /admin and /admin/, and /admin/* also matches /admin. Paths with accents or other non-ASCII characters are saved percent-encoded, as the browser reports them (/café becomes /caf%C3%A9). The rule /* excludes the whole site.
  • Hostnames match exactly, in lower case, for example staging.example.com. A trailing dot is removed. Subdomains are not included: example.com does not match www.example.com. Enter internationalised names in punycode form (xn--). A rule equal to your own domain excludes all of your traffic.
  • Countries are two-letter ISO codes such as DE, matched against the country TayStack works out for the request.
  • A change applies to new visits within about a minute. It is not retroactive: events that were already stored stay in your data, and excluded visits are never stored.
  • A site can have up to 50 exclusions in total.
  • There is no IP address exclusion. TayStack never stores IP addresses, so there is nothing to match against. To leave out your own visits use the browser flag above.

CORS

The ingest endpoint allows requests from any origin (Access-Control-Allow-Origin: * for POST and OPTIONS), so you do not need to configure CORS. The script sends the body as text/plain and without credentials.

What the endpoint answers

  • 202 for any well-formed request, even if the site id is unknown, the request comes from a bot or has no User-Agent, or storing it fails (the failure is logged on the server). A 202 therefore does not prove the event was stored. Testing with curl returns 202 but stores nothing, because curl is not a browser User-Agent.
  • 400 when the body is not valid: for example an event name with characters that are not allowed, or properties over 4096 characters. The event is lost.
  • 413 when the body is over 64 KB, 429 when one address sends over 120 requests in a minute, 405 for methods other than POST and OPTIONS.

The script never reads these answers, so none of them can affect your page.

Cookies

The script sets first-party cookies: taystack_visitor_id (one year), taystack_session_id (30 minutes) and, after an identify call, taystack_user_id (one year). They are shared across your data-domain, its www. form and its subdomains, so one person moving between example.com and www.example.com is one visitor. If the browser refuses them, every event gets new random ids and each pageview looks like a new visitor.

Missing pages in a single-page app

See Single-page apps: hash-only changes and repeated URLs are not recorded.