Getting Started

Verify your installation

Confirm that Otus is receiving events from your website before you rely on the data.

After adding the snippet, it's worth confirming that events are actually reaching Otus. There are a few quick ways to check.

Use the verify screen

Each site has a Verify page in the dashboard. Open your site and:

Make sure your website is deployed with the snippet in the <head>.
Return to the Otus Verify page — it will confirm once it detects incoming events.

The fastest sanity check is the Realtime report:

Open your live website in one tab.
Open Reports → Realtime in another.
You should see Active right now increment and your visit appear in the live event stream within a few seconds.

Open your website, then open your browser's developer tools:

On the Network tab, filter for otus.js — it should load with status 200.
Look for requests to your ingestion endpoint (/e). Each pageview sends one. A 202 Accepted response means the event was received.

You can also confirm the tracker initialised by checking the global object in the console:

typeof window.otus; // → "object"

Not seeing any data? Work through these common causes.

Wrong or missing site ID — confirm data-site-id matches the site in your dashboard.
Snippet not on the page — view source on your live site and check the <script id="otus-script"> tag is present.
You opted yourself out — clear it with localStorage.removeItem('otus_ignore').
Ad/script blockers — some blockers may stop the request. Test in a clean profile.
Caching — if you use a CDN or page cache, purge it so the updated HTML (with the snippet) is served.

Still stuck? Email info@otusanalytics.com with your site ID and we'll take a look.

All good? Take the dashboard tour to learn what you're looking at.

Install the tracking script

Add the Otus tracking snippet to the head of your website to start collecting data.

Cookieless vs. full tracking

Understand Otus's two tracking modes and which metrics each one unlocks.