# Otus Analytics Docs > Documentation for Otus Analytics: privacy-first, cookieless web analytics. Install the tracker, understand your reports, track goals and query your data via the API. Canonical Origin: https://docs.otusanalytics.com/ **Notes:** Otus Analytics is privacy-first, cookieless web analytics built in the EU: one lightweight tracking script (under 5 KB), no cookies and no consent banner required. Every documentation page is available as Markdown by appending `.md` to its URL. An MCP server with `list_pages`, `search_pages` and `get_page_markdown` tools is available at https://docs.otusanalytics.com/mcp. ## LLM Resources - [Full Content](https://docs.otusanalytics.com/llms-full.txt): Complete page content in markdown format. - [MCP server card](https://docs.otusanalytics.com/.well-known/mcp/server-card.json): Connect an MCP client to https://docs.otusanalytics.com/mcp when you need information from this site's indexed pages. - [API catalog](https://docs.otusanalytics.com/.well-known/api-catalog): The public API and service descriptions. ## Otus Analytics - [Website](https://otusanalytics.com): Product overview, features and pricing. - [Dashboard](https://app.otusanalytics.com): Sign in to view your analytics, manage sites and configure tracking. - [Docs MCP server](https://docs.otusanalytics.com/mcp): Streamable HTTP MCP endpoint for searching and reading this documentation from AI assistants. --- - **Page:** Introduction - **Source:** https://docs.otusanalytics.com/ - **Description:** Otus Analytics is a simple, privacy-friendly alternative to Google Analytics. No cookies, no personal data collection, no consent banners required. Just one lightweight script and one easy-to-read dashboard. Otus Analytics is a simple, privacy-friendly alternative to Google Analytics. **No cookies, no personal data collection, no consent banners required**. Just one lightweight script and one easy-to-read dashboard. Otus is built for the EU and for the AI age: your data stays clear and actionable, and you can even ask questions about it in plain language. ## Why Otus Cookieless tracking means no consent banner and no personal data stored. Raw IP addresses are never saved. The tracking script is under 5 KB and loads asynchronously, so it never slows your site down. Traffic, engagement, e-commerce and conversions in a single view. No report-building required. Get a written weekly report on every plan, and chat with an AI analyst about your numbers on Growth and above. ## How it works Otus has three moving parts you should know about: 1. **The tracker:** a small script you add to your site. It sends anonymous events (pageviews, engagement, outbound clicks and any custom events) as visitors browse. 2. **Ingestion:** events are received, enriched (country, device, browser) and stored. Raw IP addresses are discarded after geolocation. 3. **The dashboard:** where you read your stats, build funnels, track revenue and manage your sites and team. ## Get started ### Create your account and add a site [Register](https://docs.otusanalytics.com/getting-started/create-account) and add the domain you want to measure. ### Install the script [Add the snippet](https://docs.otusanalytics.com/getting-started/install-script) to the `` of your site, or use an [integration guide](https://docs.otusanalytics.com/integrations). ### Verify it's working [Confirm events are arriving](https://docs.otusanalytics.com/getting-started/verify-installation). ## Explore the docs Create an account, install the script, verify it and learn the dashboard. Add Otus via a script tag, Google Tag Manager, WordPress and more. Overview, realtime, engagement, e-commerce, funnels and AI. Track signups, purchases and any custom event, and mark conversions. Configure sites, exclude traffic and invite teammates. Can't find what you're looking for? Use the search box (`⌘ K` / `Ctrl K`) or email us at [info@otusanalytics.com](mailto:info@otusanalytics.com). --- - **Page:** Site settings - **Source:** https://docs.otusanalytics.com/settings-team - **Description:** Configure an individual site: name, timezone, snippet, exclusions, events and team. Each site has its own settings, separate from your personal account settings. Open a site and choose **Site settings** to manage it. ## Tabs
Tab What it's for
General Site name, domain and timezone .
Tracking snippet Copy your install code. See Install the script .
Exclusions Filter out pages or internal traffic .
Events & Conversions Choose conversions and register custom events .
Team Invite members and set roles .
Danger zone Permanently delete the site.
## General Set a human-friendly **name** so the site is easy to recognise in the switcher, and confirm the **timezone**. This determines how days are bucketed in your reports, so set it to the timezone you think about your business in. Changing the timezone affects how future data is grouped into days. Historical events keep their original timestamps. ## Danger zone Deleting a site removes its settings and stops accepting new events for it. This can't be undone, so you'll be asked to confirm. ## Account vs. site settings - **Site settings** (this section) apply to one website: timezone, snippet, exclusions, events, team. - **Account settings** apply to *you*: email, password and two-factor authentication. Subscription and [billing](https://docs.otusanalytics.com/account-billing/plans) live there too. ## Related - [Excluding pages & traffic](https://docs.otusanalytics.com/settings-team/exclusions) - [Managing custom events](https://docs.otusanalytics.com/settings-team/custom-events) - [Team & access](https://docs.otusanalytics.com/settings-team/team-access) --- - **Page:** Custom events & goals - **Source:** https://docs.otusanalytics.com/events-goals - **Description:** Track signups, purchases, clicks and form completions, and mark the ones that matter as conversions. Pageviews are only part of the picture. **Events** let you measure the actions that matter: signups, purchases, downloads, clicks and form completions. Mark an event as a **goal** (conversion) and Otus attributes it to your traffic. ## Events that track themselves The tracker records several events automatically, with no setup:
Event When it fires
page_view On page load and on every SPA navigation.
engagement When a visitor leaves a page, capturing the active time spent.
outbound_click When a visitor clicks a link to another website.
See [auto-tracked events](https://docs.otusanalytics.com/events-goals/auto-tracked-events) for the full detail on each one. ## Three kinds of events 1. **Automatic events:** the three above, sent for you. 2. **Standard events:** a catalogue of pre-defined events for common and e-commerce actions (`sign_up`, `login`, `search`, `purchase`, `add_to_cart`…). See the [standard events catalogue](https://docs.otusanalytics.com/events-goals/standard-events). 3. **Custom events:** any event you define yourself, named in `snake_case`. All non-automatic events are sent with the [tracking API](https://docs.otusanalytics.com/events-goals/tracking-api): ```js otus('track', 'newsletter_signup', { location: 'footer' }); ``` ## Goals (conversions) A **goal** is an event you've flagged as important. Open **Site settings → Events & Conversions** and toggle **Conversion** on: - a **standard event**, such as `sign_up` or `purchase` (no registration needed), or - a **custom event**, after registering its name (optionally with a description). `form_submit`, `sign_up`, `login`, `search` and `share` are conversions by default; you can switch them off. Once flagged, the event: - counts towards **Conversions** on the [Overview](https://docs.otusanalytics.com/reports/overview) and Events reports, and makes its session count towards the **conversion rate**, - gets its own card on the Events report, and - makes a session count as engaged. The number of registered custom events you can keep depends on your plan (Starter 10, Growth 50, Business 200, Enterprise unlimited). See [Plans & limits](https://docs.otusanalytics.com/account-billing/plans). ## Naming rules Custom event names must match `^[a-z0-9][a-z0-9_]{0,63}$`: lowercase letters, numbers and underscores, up to 64 characters, not starting with an underscore. Events with invalid names are dropped silently, so stick to names like `signup_completed` or `pricing_cta_click`. Event parameters have limits too, such as 25 parameters per event and 1024 characters per text value. See [Parameter limits](https://docs.otusanalytics.com/events-goals/tracking-api#parameter-limits). ## Where to go next - [Auto-tracked events](https://docs.otusanalytics.com/events-goals/auto-tracked-events): full detail on what's captured for you automatically. - [Standard events catalogue](https://docs.otusanalytics.com/events-goals/standard-events): pre-defined events and their parameters. - [Ecommerce revenue tracking](https://docs.otusanalytics.com/events-goals/ecommerce-tracking): attribute revenue to traffic. - [Tracking API](https://docs.otusanalytics.com/events-goals/tracking-api): the full client API reference. - [Events & conversions](https://docs.otusanalytics.com/settings-team/custom-events): choose conversions and register custom events. --- - **Page:** Overview - **Source:** https://docs.otusanalytics.com/integrations - **Description:** Choose the best way to add Otus Analytics to your website or platform. Otus works on any website that lets you add a ` ``` ## Where to paste it
Platform Where to add the snippet
Shopify Online Store → Themes → Edit code → theme.liquid , before .
Webflow Project settings → Custom code → Head code.
Squarespace Settings → Developer/Advanced → Code injection → Header.
Wix Settings → Custom code → Add custom code → place in the Head, on all pages.
Ghost Settings → Code injection → Site Header.
Framer Project settings → General → Custom code → End of .
Hugo / Eleventy / Astro / Jekyll Add to your base layout's .
Don't see your platform? Any "custom code", "code injection" or "header scripts" feature works, as long as it adds the snippet to the **head on all pages**. Dedicated, one-click integrations for more platforms are coming soon. ## After installing Some hosted platforms cache pages aggressively. If you don't see data immediately, clear any cache, then [verify your installation](https://docs.otusanalytics.com/getting-started/verify-installation). Need help with a specific platform? Email [info@otusanalytics.com](mailto:info@otusanalytics.com). --- - **Page:** Google Tag Manager - **Source:** https://docs.otusanalytics.com/integrations/google-tag-manager - **Description:** Deploy the Otus tracking script through Google Tag Manager without touching your site's code. If you already use Google Tag Manager (GTM), you can deploy Otus through it without editing your site's HTML. A dedicated GTM template is on the way. In the meantime, the **Custom HTML tag** method below works today. ## Add Otus as a Custom HTML tag 1. Open your **Google Tag Manager** container. 2. Go to **Tags → New → Tag Configuration → Custom HTML**. 3. Paste your Otus snippet into the HTML field:```html ``` 4. Under **Triggering**, choose **All Pages** (the *Initialization* or *All Pages* trigger) so the script loads on every page. 5. **Save**, then **Submit / Publish** your container. ## A note on accuracy Because GTM itself is a script that loads after the page, deploying Otus through a tag manager can slightly undercount visitors who leave very quickly or who block tag managers. For the most accurate numbers, the [direct script tag](/integrations/script-tag) in your `` is preferred. ## Tracking custom events from GTM You can fire Otus [custom events](/events-goals) from GTM tags. Add a **Custom HTML** tag with the appropriate trigger (for example a button-click trigger): ```html ``` Custom event names must be lowercase letters, numbers and underscores (max 64 characters). See the [Tracking API](https://docs.otusanalytics.com/events-goals/tracking-api) for details. To connect events across sessions or devices, pass a [linking ID](https://docs.otusanalytics.com/events-goals/tracking-api#linking-events) as the fourth argument, for example a cart ID from a data layer variable: `otus('track', 'begin_checkout', { value: 89 }, {{DLV - cart ID}});`. Never use a user ID or email address as linking ID. ## Identifying logged-in users from GTM On sites in [full tracking](https://docs.otusanalytics.com/getting-started/tracking-modes) mode, a **Custom HTML** tag on a login or page-view trigger can pass your internal user ID (never an email address), and another on logout can reset it: ```html ``` ```html ``` See [identify](https://docs.otusanalytics.com/events-goals/tracking-api#identify) for how this works with consent. ## Passing consent from your CMP Otus never assumes consent: until you tell it otherwise, visits are counted anonymously and nothing is forwarded to ad platforms. Most consent management platforms (Cookiebot, OneTrust, Usercentrics, …) push a consent event to the data layer when the visitor makes a choice. Add a **Custom HTML** tag that fires on that event and forwards the choice. Most CMPs also push it on page load when a returning visitor already has a stored choice. Don't fire this tag before the visitor has answered, or an unanswered banner would be recorded as a denial: ```html ``` Replace the two variables with the ones your CMP provides. The snippet's queue stub makes the call safe even if it runs before the tracker has loaded. See [consent](https://docs.otusanalytics.com/events-goals/tracking-api#setconsent) for what each category controls, and `consentWait` if your CMP reports stored choices slightly after page load. ## Next step After publishing, [verify your installation](https://docs.otusanalytics.com/getting-started/verify-installation). --- - **Page:** Use the docs with AI - **Source:** https://docs.otusanalytics.com/getting-started/use-with-ai - **Description:** Ask ChatGPT, Claude, Cursor and other AI assistants about Otus using these docs. Prefer asking an AI assistant instead of reading? These docs are built so ChatGPT, Claude, Cursor and other assistants can read them and give accurate answers about Otus. This is about the **documentation**. To ask questions about your own analytics data, use [AI Chat](https://docs.otusanalytics.com/reports/ai-chat) in the dashboard. ## Ask about a single page Every page has a **Copy page** button at the top. Use the arrow next to it to: - **Copy page:** copy the page as Markdown and paste it into any AI chat. - **Open in ChatGPT** or **Open in Claude:** start a new chat that has already read the page. - **View as Markdown:** open the plain-text version of the page. You can also add `.md` to the end of any docs URL to get the Markdown version, for example [/getting-started/install-script.md](https://docs.otusanalytics.com/getting-started/install-script.md). ## Give your assistant all of the docs To give an assistant the full picture, point it at one of these files: - [`/llms.txt`](https://docs.otusanalytics.com/llms.txt): an index of every page with a short summary of each. - [`/llms-full.txt`](https://docs.otusanalytics.com/llms-full.txt): the complete docs in one file. ## Connect the docs to your AI tools If you use an assistant that supports MCP (Model Context Protocol), such as Claude, Cursor or VS Code, connect it to the Otus docs. It can then search and read the docs whenever you ask about Otus. The server address is: ```txt https://docs.otusanalytics.com/mcp ``` For example, in Claude Code: ```bash claude mcp add --transport http otus-docs https://docs.otusanalytics.com/mcp ``` See [MCP server](https://docs.otusanalytics.com/ai/mcp) for setup steps for every supported tool. ## Next step Set up the [MCP server](https://docs.otusanalytics.com/ai/mcp) in your favorite AI tool. --- - **Page:** Cookieless vs. full tracking - **Source:** https://docs.otusanalytics.com/getting-started/tracking-modes - **Description:** Understand Otus's two tracking modes and which metrics each one enables. Otus supports two tracking modes. You choose one per site via the `trackingMode` option in your snippet's `otus.init()`. **Cookieless is the default** and is what most sites should use. ## Cookieless (default) In cookieless mode Otus sets **no tracking cookies** and stores **no persistent identifiers** in the visitor's browser, with or without consent. The only cookie is `otus_consent`, and only if your site reports consent choices with [`setConsent`](https://docs.otusanalytics.com/events-goals/tracking-api#setconsent): it remembers the visitor's choice, which is strictly necessary. Because no personal data or identifiers are persisted, you typically **don't need a consent banner** for analytics. To group requests into sessions, Otus derives a session identity **server-side** from a hash of the truncated IP address (IPv4 /28, IPv6 /48), user agent and language, combined with a secret salt that is replaced every day. Visitors therefore can't be recognised across days, and the hash can't be recomputed afterwards. Sessions use a 30-minute sliding window. The raw IP address is used to look up the country and is not stored with your analytics data. **What you get:** all core traffic, engagement, source, location, device, funnel and e-commerce reports. **What you don't get:** anything that requires recognising the *same person* across sessions, specifically **returning-visitor rate** and **new vs. returning** breakdowns. ```html [Cookieless (the default)] ``` ## Full tracking With [analytics consent](https://docs.otusanalytics.com/events-goals/tracking-api#setconsent), full tracking stores a session ID (30-minute sliding window) and a persistent visitor ID in a first-party cookie. This lets Otus recognise returning visitors and enables the related metrics. The cookie is set on your root domain (`example.com`), so a visitor keeps the same session and visitor ID when moving between `www.example.com`, `shop.example.com` and `app.example.com`. See [subdomains and multiple domains](https://docs.otusanalytics.com/integrations/subdomains). Because full mode stores identifiers on the device, it only does so once the visitor has granted **analytics consent** via [`otus('setConsent', ...)`](https://docs.otusanalytics.com/events-goals/tracking-api#setconsent). Until then, and for visitors who decline, visits are still recorded exactly like cookieless mode. Returning-visitor metrics are therefore based on consenting visitors only. Full tracking also lets you [identify logged-in users](https://docs.otusanalytics.com/events-goals/tracking-api#identify), so the same person is counted as one user across devices, and their earlier anonymous visits on that browser count towards them too. **Adds on top of cookieless:** [new vs. returning users](https://docs.otusanalytics.com/reports/overview#new-vs-returning-users) breakdowns and user identification. ```html [Full tracking] ``` ## Side by side
Cookieless (default) Full
Cookies None Session ID + visitor ID (and user ID / user properties if you use them) with analytics consent, ad click IDs with marketing consent
Consent banner typically required No (analytics) Yes, for the cookie and visitor ID
Sessions Server-side hash (30-min window) Client session ID with consent, server-side hash without
Core traffic, sources, locations, devices ✅ ✅
Engagement, funnels, e-commerce ✅ ✅
Returning-visitor rate / new vs. returning — ✅
User identification — ✅
Linking events across sessions ✅ with analytics consent ✅ with analytics consent
Conversion forwarding Within the same visit Within each ad platform's conversion window
## Cookies in full tracking These are first-party cookies on your root domain, so they're shared by all your subdomains. List them in your cookie policy. Nothing is set before the visitor gives consent for the category, and withdrawing consent deletes them.
Cookie Purpose Category Expires
otus_ Visitor ID, session ID and time of the last event, plus the user ID if you use it Analytics 13 months
otus__props User properties , if you use them Analytics 13 months
otus__cid Ad click IDs ( gclid , fbclid , …) and when the click happened, for conversion forwarding Marketing 90 days after the click
otus_consent The visitor's consent choice, set when your site calls setConsent Strictly necessary 13 months
otus_ignore Opt-out , only if you set it Strictly necessary 13 months
`` is your site ID, for example `otus_123`. ## How privacy is handled either way Regardless of mode: - **Raw IP addresses are never stored with your analytics data.** They're used to derive the country (via MaxMind) and the daily session hash. If you've connected an [ad platform](https://docs.otusanalytics.com/conversion-forwarding), the IP and user agent are included in conversions forwarded to it (only with marketing consent), and held on our servers for at most 30 minutes while a visitor's marketing consent is still unanswered. - Unknown consent is never treated as granted. See [consent](https://docs.otusanalytics.com/events-goals/tracking-api#setconsent). - Otus stores aggregate, non-identifying attributes such as country (ISO-2), device type, browser and referrer. ## Next step Continue to the [dashboard tour](https://docs.otusanalytics.com/getting-started/dashboard-tour), or learn how to [track custom events and goals](https://docs.otusanalytics.com/events-goals). --- - **Page:** Realtime - **Source:** https://docs.otusanalytics.com/reports/realtime - **Description:** A live view of the sessions on your site right now, refreshed every few seconds. The **Realtime** report shows what's happening on your site **right now**. It refreshes automatically every few seconds, so it's useful for launches, campaigns and verifying a new install. ## Live stat cards Four cards at the top:
Card Meaning
Active Right Now Sessions with activity in the last 5 minutes.
Pageviews / min Pageviews in the last 60 seconds.
Active Sessions / min Sessions with activity in the last 60 seconds.
Countries Number of countries with active sessions.
A session is **active** when it had any activity in the last 5 minutes **and** includes a pageview, the same rule as every other report. Someone reading a long article still counts; a session kept alive only by custom events firing on a timer doesn't. ## Live charts A **pageviews-per-minute** chart shows the last stretch of activity, alongside a **map** of where your active sessions are located. Below the event stream you'll find active sessions by **device**, by **current page** (the page each session is on right now, so every session counts once) and by **source**. Countries, devices and sources come from each session's first pageview, like in the other reports, and shares are calculated against all active sessions. ## Event stream The **event stream** lists the most recent events as they arrive, newest first. Each row is colour-coded by category and shows useful context: - the **event type** (pageview, engagement, outbound click, e-commerce, or a custom event), - the **country** flag and **device** icon, - the **page** path, - the **source**, and - a relative **timestamp** ("a few seconds ago"). Realtime is the quickest way to confirm a fresh installation is working. Open your site in one tab and watch yourself appear here. See [Verify your installation](https://docs.otusanalytics.com/getting-started/verify-installation). ## Related - [Overview](https://docs.otusanalytics.com/reports/overview): aggregated stats over a date range. - [Engagement](https://docs.otusanalytics.com/reports/engagement): depth of interaction. --- - **Page:** Glossary - **Source:** https://docs.otusanalytics.com/reports/glossary - **Description:** Plain-language definitions of every metric and concept in your Otus reports, with the formula behind each number. Every number in Otus is built from the same few definitions. This page explains each one, the formula behind it, and how it relates to the others, so you know exactly what you're looking at. ## Engagement & bounce ### Session A visit to your site: a visitor's activity grouped together until they've been inactive for **30 minutes**. A session only counts when it includes **at least one pageview** in the selected date range. Activity without a pageview (for example engaged time sent just after midnight for a page viewed the day before) belongs to that earlier session and doesn't create a new one. This same definition is used everywhere in Otus: the Sessions numbers, every per-session average, every rate, funnels and realtime. A session **starts** at its first pageview in the range. Its channel, source, landing page, country and device all come from that **first pageview**, so each session counts once in every breakdown and the rows add up to your total sessions. ### Engaged session A session in which the visitor showed real interest. A session is **engaged** when it had at least one of: - more than **10 seconds of active time** (the tab was visible and focused), - **2 or more pageviews**, or - at least one [conversion](#conversions). This is the same definition Google Analytics 4 uses. ### Engagement rate The share of sessions that were engaged. > **Engagement rate** = engaged sessions ÷ sessions On the pages table, a page's engagement rate is the share of the sessions that viewed that page that were engaged. Engagement is judged over the whole session, not only the time spent on that page. ### Bounce rate The share of sessions that were **not** engaged: the visitor left quickly, viewed only one page and didn't convert. > **Bounce rate** = 100% − engagement rate Bounce rate and engagement rate always add up to 100%. A visitor who reads a single article for two minutes is engaged, so that visit is **not** a bounce. This matches Google Analytics 4. Older tools counted every single-page visit as a bounce, so their bounce rates are usually higher. ### Engagement time The **total** active time visitors spent on your site. Only foreground time counts: time in a background tab or with the window minimised is excluded. The averages below are built from this total. Engagement time is the only time metric in Otus: there's no "session duration", which would include idle time. ### Avg. engagement time per session How long visitors actively spend on your site per visit. > **Avg. engagement time per session** = engagement time ÷ sessions Sessions without any engaged time count as 0 seconds. The Overview card can also show it **per user** (engagement time ÷ [users](#users)), which is estimated when some users are counted as sessions. ### Avg. time on page How long visitors actively spend on a page per visit to that page. A *page visit* is one session viewing one page; a session that views three pages has three page visits. > **Avg. time on page** = engagement time ÷ page visits Page visits without any engaged time count as 0 seconds. Engaged time on a page that has no pageview in the selected range (for example a page viewed just before midnight) isn't part of any page visit, so it's left out here. **Why is the time per session higher than the time on page?** Both use the same engaged time, but divide it differently. A session that spends 6 seconds on each of 3 pages has 18 seconds of engagement time per session, and 6 seconds of time on page. The more pages people view per visit, the bigger the gap. ## Dashboard metrics ### Pageviews Every page load, plus every navigation to a new path in a single-page app. A pageview counts on the day the visitor's browser recorded it, even if it reached our servers a moment later (just after midnight, for example). ### Users The number of different people who visited. With [full tracking](#tracking-modes) and analytics consent, a visitor is recognised across sessions. Otherwise each session counts as one user, because Otus can't tell whether two sessions belong to the same person. Reports mark users as **estimated** whenever that happens: always on cookieless sites, and on full-tracking sites when some visitors didn't give analytics consent. The tooltip shows what share of sessions could be identified. Otus only uses the word "users" for counts of people: anything that counts visits is labelled "sessions". ### Sessions The number of [sessions](#session) in the selected period: visits with at least one pageview. ### Views per visit The average number of pages viewed in a session. > **Views per visit** = pageviews ÷ sessions Shown as **Pageviews / Session** on the Engagement report. ### New vs. returning users - **New:** the user's first-ever visit falls within the selected period. - **Returning:** the user came back during the selected period after an earlier visit. A user can be both in the same period. Only sessions with a pageview count. Requires [full tracking](#tracking-modes). See the [Overview report](https://docs.otusanalytics.com/reports/overview#new-vs-returning-users) for details. ### Event totals Conversions, revenue, orders and event counts only include events that happened in a [session](#session) (a visit with at least one pageview in the range), the same rule as every session count. **Refunds** are the exception and always count, because they're usually sent from a back office or server without a pageview. ### Conversions The number of times an event you've marked as a [goal](https://docs.otusanalytics.com/events-goals#goals-conversions) happened, such as `sign_up` or `purchase`. Conversions count **events**: a session that converts twice adds 2. ### Conversion rate The share of sessions with at least one conversion. > **Conversion rate** = sessions with a conversion ÷ sessions A session that converts twice adds 2 to conversions but counts once here, so you can't calculate the rate from the conversions column. ### Share of events On the Events report: the share of all tracked events (excluding pageviews) that are conversions. It's a different metric from the conversion rate, which is about sessions. > **Share of events** = conversions ÷ events ### Completion rate On the [Funnels](https://docs.otusanalytics.com/reports/funnels) report: the share of sessions that entered the funnel and completed every step. > **Completion rate** = sessions that completed the last step ÷ sessions that entered ### Revenue The total `value` of all `purchase` events in the period. See [e-commerce tracking](https://docs.otusanalytics.com/events-goals/ecommerce-tracking). ### Orders and average order value **Orders** count every `purchase` event. **Average order value** = revenue ÷ orders. ### Net revenue > **Net revenue** = revenue − refunds Refunds count in the period they happen, not in the period of the original purchase. ### Landing pages The landing page is the **first page of a session**. Landing totals count sessions per page: for example `/` 100 landings and `/pricing` 75. ### Exit rate How often a page was the last page viewed in a session. > **Exit rate** = sessions whose last pageview was the page ÷ pageviews of the page ### Shares Percentages like "share of sessions" for countries, devices, products or search queries are calculated against the **real total** for the period, not just the rows shown, so they stay correct when a list is cut off. ### Active sessions On the [Realtime](https://docs.otusanalytics.com/reports/realtime) report: sessions with any activity in the last 5 minutes **and** a pageview. Someone reading a long article still counts; a session kept alive only by custom events firing on a timer doesn't. ## Tracking concepts ### Visitor A person browsing your site. Whether Otus can recognise the same visitor across sessions depends on the [tracking mode](#tracking-modes). ### Tracking modes - **Cookieless** (default): no cookies or identifiers are stored in the browser. Sessions are recognised with a daily-changing, server-side hash, so returning visitors can't be recognised. - **Full tracking**: with analytics consent, a visitor ID is stored in the browser, which enables returning-visitor metrics. See [Cookieless vs. full tracking](https://docs.otusanalytics.com/getting-started/tracking-modes). ### Events Anything that happens on your site that Otus records. `page_view`, `engagement` and `outbound_click` are [tracked automatically](https://docs.otusanalytics.com/events-goals/auto-tracked-events); others are [standard](https://docs.otusanalytics.com/events-goals/standard-events) or [custom](https://docs.otusanalytics.com/events-goals) events you send yourself. ### Goals An event you've marked as important in **Site settings → Events & Conversions**. Every occurrence counts as a [conversion](#conversions), and any session with a goal counts as [engaged](#engaged-session). ### Channels The predefined traffic-source categories (Direct, Organic Search, Paid Search, …) assigned to every visit. A session's channel is taken from how it started. See [Channels](https://docs.otusanalytics.com/reports/channels). ### UTM parameters Tags you add to campaign links (`utm_source`, `utm_medium`, `utm_campaign`, …) so Otus can attribute visits to the right source and channel. See [UTM parameters](https://docs.otusanalytics.com/integrations/utm-parameters). ### Comparison period & deltas When you compare against an earlier period, each metric shows a **delta**: the change compared with that period, as a **relative percentage**. For rates that's the relative change of the rate itself: a bounce rate going from 40% to 44% shows as **+10%**, not +4 points. - Deltas are calculated from the exact values, before rounding. An average of 4.04s versus 4.0s shows the same "4s" twice, but a +1% change. - When the earlier value was zero, no percentage is possible and the delta shows **–**. Otus doesn't say "new": a page with views in week 1, none in week 2 and views again in week 3 isn't new. - In tables, every row is compared with its own value in the earlier period, even if it wasn't among the top rows back then. - The [AI Analyst](https://docs.otusanalytics.com/reports/ai-analyst) and AI Chat describe changes in rates in percentage points ("+4pp") in their written text, because that's how analysts talk about rates. ## Date & time ### Site timezone Every report uses the timezone set in your site's settings. Days, and the daily points in charts, run from midnight to midnight in that timezone. ### Date ranges A date range includes the whole start day and the whole end day. "Last 7 days" and the other "Last …" ranges end yesterday, so they only cover complete days. Pick "Today" to see the current day, in your site's timezone. ### Which day things count on In daily charts, counts of **sessions** (sessions, users, engaged sessions, bounce rate, conversion rate) go on the day the session started (its first pageview). Counts of **events** (pageviews, conversions, revenue, engagement time) go on the day the event happened. A visit from 23:50 to 00:10 is one session on the first day, but a pageview at 00:05 counts on the second day. ### Days, weeks and months in charts Charts over time show one point per day by default. Use the selector next to a chart to group by week or month instead. Weeks run from Monday to Sunday. - Users, rates and averages are calculated for the whole week or month, not added up from the days. Someone who visits on three days of a week counts as one user for that week. - The first and last week or month can be partial: they only include the days inside your date range. Hover over a point to see which days it covers. - When comparing periods, the first week (or month) of the current period is compared with the first week (or month) of the previous period, and so on. ### Sessions at the edge of a range Only events inside the date range are counted. A session that runs across the start or end of the range (for example a visit from 23:50 to 00:10) only contributes the events inside the range, and only counts as a session if it has a pageview inside the range. ### Known limitation: visits across midnight (UTC) In cookieless mode, Otus recognises a visit with a privacy-friendly hash that changes every day at **midnight UTC**. A visit that's still going at that moment is split into two sessions. A fix for sites using full tracking is planned. --- - **Page:** AI Traffic - **Source:** https://docs.otusanalytics.com/reports/ai-traffic - **Description:** See how much traffic AI assistants send you, which platforms, landing pages and goals perform best, and which AI agents read your pages. The **AI Traffic** report shows how big AI is as a traffic source for your site. Use it to track your AEO (answer engine optimization) and GEO (generative engine optimization): whether AI assistants like ChatGPT, Perplexity and Claude cite your pages, and whether the people they send convert. It covers two kinds of AI traffic: - **AI referrals:** people who click a link in an AI assistant and land on your site. These are real visits and appear in all your other reports too, under the [AI Assistant channel](https://docs.otusanalytics.com/reports/channels). - **AI agents:** AI products loading your pages themselves, for example ChatGPT fetching a page to answer someone's question. These aren't visits and are kept out of every other report. ## How AI visits are recognised A visit counts as AI traffic when its first page view came from an AI assistant, recognised by: - the **referrer**: the AI assistant's website or app (for example `chatgpt.com`, `perplexity.ai`, `claude.ai`, `gemini.google.com`, `copilot.microsoft.com`), including its subdomains, or - the **utm_source** of the landing page: ChatGPT adds `utm_source=chatgpt.com` to most links it shows. Recognised platforms: ChatGPT, Perplexity, Claude, Gemini, Copilot, Grok, Meta AI, DeepSeek, Mistral, Duck.ai, Poe, You.com and Phind. Ads shown in AI assistants (for example a ChatGPT ad click with `oppref`, or a link tagged `utm_medium=cpc`) count as paid traffic, not as AI traffic. AI traffic is a lower bound. Many AI apps, such as the ChatGPT and Claude desktop and mobile apps, open links without a referrer, so some AI visits show up as Direct. Google's AI Overviews and AI Mode send visitors from `google.com`, which can't be told apart from regular search, so they count as Organic Search. AI traffic is recognised from the moment it's recorded. Visits recorded before the AI Traffic report was released aren't reclassified. ## Stat cards
Metric What it measures
AI Traffic Visits ( sessions ) that started from an AI assistant.
Traffic Share AI visits as a percentage of all visits.
Top Platform The AI platform that sent the most visits, with its share of AI visits.
Platforms Detected How many AI platforms sent at least one visit.
## Executive summary The most important AI traffic signals for the period, picked by fixed rules (no AI is used to write them): - **Traffic leader:** the platform that sent the most AI visits, as a share of all AI visits. - **Best goal performance:** the platform with the highest conversion rate. A platform needs at least **30 visits** to be compared, so one visit that happened to convert can't win with 100%. It also shows how all AI visits convert compared to your site-wide conversion rate. - **Recommended focus:** a suggestion based on your numbers, for example to strengthen the pages that already work for your leading platform, or to improve the landing pages when AI visitors convert below your site average. ## AI traffic trend Daily AI visits, stacked by platform (the top five, with the rest as Other AI). When you compare periods, the chart shows all AI visits against the previous period instead. ## Platform performance Visits, users, engagement time, conversions, conversion rate and revenue per AI platform. The same table is available as the **AI platforms** tab of the Acquisition card in the [Overview report](https://docs.otusanalytics.com/reports/overview). ## Top landing pages from AI The first page of each AI visit: the pages AI assistants link to. Pick a platform to see the pages a single assistant sends people to. Conversion rate is the share of those visits with at least one conversion. ## AI conversions by goal For each of your [conversion events](https://docs.otusanalytics.com/settings-team/custom-events): how many were completed by AI visitors, the share of AI visits that completed it, and the platforms behind them. ## AI agents AI assistants also load pages themselves, for example when someone asks ChatGPT about your product and it fetches your pricing page to answer. This card shows the AI agents that ran the Otus script on your pages: - **User requests:** agents fetching a page while answering someone's question (ChatGPT-User, Claude-User, Perplexity-User, MistralAI-User, Gemini). A strong sign your content is used in AI answers. - **Crawlers:** search and training crawlers (such as OAI-SearchBot, PerplexityBot, GPTBot and ClaudeBot) that ran the script. Only a small share of AI agents shows up here: most don't run scripts, and the Otus script only records visitors that do. Some agents, like ChatGPT agent, Copilot, Grok and AI browsers such as ChatGPT Atlas and Perplexity Comet, look exactly like normal visitors and can't be recognised. Agent page views never count as visits, users or billable events, and filters don't apply to them. ## Filtering by AI platform Use the **AI platform** filter (under Source) to see any report for visitors from one AI assistant only, for example which pages ChatGPT visitors read on the [Engagement report](https://docs.otusanalytics.com/reports/engagement). ## Related - [Channels](https://docs.otusanalytics.com/reports/channels): how the AI Assistant channel is determined. - [Filters & segments](https://docs.otusanalytics.com/reports/filters): filter any report by AI platform. - [Glossary](https://docs.otusanalytics.com/reports/glossary): sessions, conversion rate and other definitions. --- - **Page:** Engagement - **Source:** https://docs.otusanalytics.com/reports/engagement - **Description:** See how deeply visitors interact with your site: engagement time, engagement rate, bounce rate and time on page. Pageviews tell you *how many*; the **Engagement** report tells you *how deeply*. It focuses on the quality of attention your content gets. ## Stat cards
Metric What it measures
Sessions Visits with at least one pageview.
Avg. Engagement Time / Session Total active time ÷ sessions. See avg. engagement time per session .
Engagement Rate Share of sessions that were engaged .
Pageviews / Session Average number of pages viewed per visit.
Hover the **(i)** next to a card for its definition, with a link to the [Glossary](https://docs.otusanalytics.com/reports/glossary). ## Pages table Every page with its views, sessions, users and three engagement metrics: - **Avg. time on page:** active time per page visit (one session viewing the page). Visits without engaged time count as 0 seconds. See [avg. time on page](https://docs.otusanalytics.com/reports/glossary#avg-time-on-page). - **Engagement rate:** share of the sessions that viewed the page that were engaged. - **Bounce rate:** share of those sessions that weren't engaged, so always 100% minus the engagement rate. The bold **Total** row covers every page in the period, not only the visible rows. Its bounce rate is exactly 100% minus the Engagement Rate card. **Why is avg. time on page lower than the engagement time card?** The card divides engaged time by sessions, while the table divides it by page visits. A visitor who views three pages counts once on the card and three times in the table. See the [Glossary](https://docs.otusanalytics.com/reports/glossary#avg-time-on-page) for an example. ## Landing and exit pages - **Landing pages:** the first page of each session. Landing totals count sessions per page. - **Exit pages:** the last page viewed in each session, with the **exit rate**: exits ÷ pageviews of that page. ## New vs. returning users The new vs. returning breakdown is on the [Overview](https://docs.otusanalytics.com/reports/overview#new-vs-returning-users) report. **Returning-user metrics require full tracking.** In the default cookieless mode, Otus doesn't store a visitor identifier, so it can't tell whether someone has visited before. ## Top pages by time on page A ranking of pages by **average time on page** (the same metric as the pages table), showing which articles or product pages hold attention the longest. ## How engagement is measured The tracker records an **engagement** event when a visitor leaves a page or navigates within your SPA, provided they scrolled further or stayed active for at least a few seconds. It carries the active time spent on the page, which powers the time metrics above. ### Engaged sessions A session counts as **engaged** (the same definition as Google Analytics 4) when it: - had more than **10 seconds of active time** (the tab was visible and focused), - had **2 or more pageviews**, or - included at least one [conversion event](https://docs.otusanalytics.com/settings-team/custom-events). **Engagement rate** is the share of sessions that were engaged. **Bounce rate** is the opposite: the share of sessions that weren't engaged, so the two always add up to 100%. ## Related - [Glossary](https://docs.otusanalytics.com/reports/glossary): exact definitions of every metric. - [Tracking modes](https://docs.otusanalytics.com/getting-started/tracking-modes): what enables returning-visitor data. - [Overview](https://docs.otusanalytics.com/reports/overview): headline engagement metrics. --- - **Page:** E-commerce - **Source:** https://docs.otusanalytics.com/reports/ecommerce - **Description:** Track revenue, orders, average order value and your best-selling products. The **E-commerce** report turns purchase events into revenue insight, so you can connect your traffic to actual money. This report is populated by the standard e-commerce events you send from your site, especially `purchase` and `refund`. See [Ecommerce revenue tracking](https://docs.otusanalytics.com/events-goals/ecommerce-tracking) to set them up. ## Stat cards
Metric What it measures
Total Revenue Gross revenue from purchase events.
Orders Every purchase event. The same number is used in the chart and for the average order value.
Avg. Order Value Total revenue divided by orders.
Net Revenue Total revenue minus refunds. Refunds count in the period they happen, not the period of the original purchase.
Amounts are shown in your site's configured currency. Like every event total, purchases only count when they happen in a [session](https://docs.otusanalytics.com/reports/glossary#session) (a visit with at least one pageview). Refunds always count, because they're usually sent from your back office or server without a pageview. ## Revenue & orders over time An area chart plots **revenue** and **orders** across your date range so you can spot trends, seasonality and the impact of campaigns. ## Purchase funnel A funnel view tracks sessions through the shopping steps `view_item` → `add_to_cart` → `begin_checkout` → `purchase`, with the **drop-off** at each stage, so you can see exactly where buyers abandon. It works like the [Funnels](https://docs.otusanalytics.com/reports/funnels) report: within a session the steps must happen **in order**, so a session that adds to cart without viewing an item first only counts for the steps it completed in order. ## Top products Two rankings highlight your bestsellers: - **Top Products by Revenue:** what makes you the most money. - **Top Products by Units Sold:** what sells in the highest volume. A full **All Products** table lists every product with its revenue and units sold. Each product's share is calculated against all products in the period, not only the ones listed. ## Sending the data The report relies on the standard e-commerce events from the [events catalogue](https://docs.otusanalytics.com/events-goals/standard-events), each with typed parameters. For example a purchase: ```js otus('track', 'purchase', { transaction_id: 'T-12345', value: 49.90, currency: 'EUR', items: [ { item_id: 'SKU-1', item_name: 'Pro plan', price: 49.90, quantity: 1 } ] }); ``` See [Ecommerce revenue tracking](https://docs.otusanalytics.com/events-goals/ecommerce-tracking) for the full setup. ## Related - [Ecommerce revenue tracking](https://docs.otusanalytics.com/events-goals/ecommerce-tracking) - [Standard events catalogue](https://docs.otusanalytics.com/events-goals/standard-events) - [Funnels](https://docs.otusanalytics.com/reports/funnels) --- - **Page:** WordPress - **Source:** https://docs.otusanalytics.com/integrations/wordpress - **Description:** Add Otus Analytics to a WordPress site via your theme header or a header-scripts plugin. There are two easy ways to add Otus to WordPress. Use whichever fits your setup. A dedicated Otus WordPress plugin is on the way. Until then, the methods below work on any WordPress site. ## Option 1: A header-scripts plugin (recommended) If you'd rather not touch theme files, install a small plugin that injects code into the ``, such as **WPCode** or **Insert Headers and Footers**. 1. Install and activate the plugin. 2. Open its settings and find the **Header** / **Scripts in header** box. 3. Paste your Otus snippet:```html ``` 4. Save. The snippet will now load on every page. ## Option 2: Edit your theme header If you're comfortable editing theme files, add the snippet to your theme's `header.php` just before ``. Use a **child theme** so your change isn't lost when the parent theme updates. ```php [header.php] ``` ## Caching WordPress sites often sit behind a page cache or CDN. After adding the snippet, **clear/purge your cache** so the updated HTML is served, then [verify your installation](https://docs.otusanalytics.com/getting-started/verify-installation). ## Next step [Verify your installation](https://docs.otusanalytics.com/getting-started/verify-installation), then explore your [reports](https://docs.otusanalytics.com/reports/overview). --- - **Page:** Create your account & add a site - **Source:** https://docs.otusanalytics.com/getting-started/create-account - **Description:** Register for Otus Analytics, add your first website and find your tracking snippet. Before you can collect any data you need an Otus account and at least one site. This takes a couple of minutes. ## Register for an account 1. Go to [app.otusanalytics.com](https://app.otusanalytics.com) and choose **Create account**. 2. Enter your email address and a password. 3. Confirm your email if prompted. New accounts start on a **30-day free trial** of the Starter plan. No card required to begin. See [Plans & limits](https://docs.otusanalytics.com/account-billing/plans) for what each tier includes. ## Add your first website Once you're signed in: 1. Select **Add a site**. 2. Enter your site's **domain** (for example `example.com`). Enter it without `https://` or a trailing slash. 3. Choose your **timezone** so reports line up with your day. 4. Save the site. A "site" in Otus is identified by a numeric **site ID**, which is baked into your tracking snippet. The domain is read from the visitor's browser at runtime, so make sure the snippet is installed on the domain you registered. ## Find your tracking snippet After creating a site you'll be taken to the install screen. You can return to it any time from **Site settings → Tracking snippet**. Your snippet looks like this (your `siteId` will differ): ```html [index.html] ``` ## Next step Head to [Install the tracking script](https://docs.otusanalytics.com/getting-started/install-script) to add the snippet to your site, or pick a platform-specific [integration guide](https://docs.otusanalytics.com/integrations). --- - **Page:** Install the tracking script - **Source:** https://docs.otusanalytics.com/getting-started/install-script - **Description:** Add the Otus tracking snippet to the head of your website to start collecting data. Otus collects data through a single lightweight script. Add it once to every page you want to measure. The best place is inside the `` so it loads early. ## Add the snippet Copy your snippet from **Site settings → Tracking snippet** and paste it just before the closing `` tag: ```html [index.html] ``` Replace `siteId: 123` with **your** site ID. Everything else can stay as-is. The first line loads the tracker. The second defines `otus()` right away, so calls like `otus('track', ...)` or `otus('setConsent', ...)` work anywhere on the page, even before the tracker has finished loading: they're queued and sent once it has. The script loads `async` and is under 4 KB, so it won't block rendering or slow your page down. ## Options Pass these to `otus.init({ ... })`:
Option Required Description
siteId Yes Your numeric site ID. Without it, tracking is skipped.
endpoint No Ingestion URL. Defaults to https://ingest.otusanalytics.com/e .
trackingMode No "cookieless" (default) or "full" . See Tracking modes .
hash No true for hash-based routing ( /#/about ), see Single-page apps .
consentDefault No "granted" to treat unanswered consent as granted, for sites that don't need a consent banner. See consent .
consentWait No Hold the first pageview up to this many milliseconds (max 10000) for your consent banner to call otus('setConsent', ...) .
trackLocalhost No true to also track visits on localhost , for testing.
## Enabling full tracking Cookieless is the default. To enable [full tracking](https://docs.otusanalytics.com/getting-started/tracking-modes) (which enables returning-visitor metrics), add `trackingMode: "full"`: ```js otus.init({ siteId: 123, endpoint: "https://ingest.otusanalytics.com/e", trackingMode: "full" }) ``` ## Single-page apps (SPAs) You don't need to do anything extra. The tracker automatically records a pageview on the initial load **and** on every client-side route change to a new path (`pushState` and back/forward navigation), so frameworks like Vue, React, Svelte and Angular work out of the box. Query-string changes, `#anchor` links and redirects via `replaceState` aren't counted as new pageviews. If your app uses hash-based routing (URLs like `/#/about`), add `hash: true` to `otus.init()`. Hash changes are then tracked as pageviews, with the hash included in the page path. ## Opting yourself out To stop the tracker recording your own visits in a browser, run this in the console once: ```js document.cookie = "otus_ignore=true; domain=example.com; path=/; max-age=34128000"; ``` Replace `example.com` with your own domain (without `www.`), so the opt-out applies to all your subdomains. ## Next step Once the snippet is live, [verify your installation](https://docs.otusanalytics.com/getting-started/verify-installation). Using a tag manager or CMS instead? See the [integration guides](https://docs.otusanalytics.com/integrations). --- - **Page:** Script tag (add to <head>) - **Source:** https://docs.otusanalytics.com/integrations/script-tag - **Description:** The universal way to install Otus: paste the snippet into your site's head. Adding the script tag directly to your HTML is the most reliable way to install Otus. It works on every platform that lets you edit the page ``. ## Steps 1. In the Otus dashboard, open **Site settings → Tracking snippet** and copy your snippet. 2. Paste it just before the closing `` tag on every page of your site. 3. Deploy your site. 4. [Verify the installation](https://docs.otusanalytics.com/getting-started/verify-installation). ```html [index.html] ``` Use a **shared layout/template** so the snippet appears on every page automatically, rather than pasting it page by page. ## Where to put it in popular frameworks ### Next.js (App Router) Add both parts in `app/layout.tsx` using `next/script`: ```tsx [app/layout.tsx] import Script from 'next/script' export default function RootLayout({ children }: { children: React.ReactNode }) { return ( {children} ) } ``` ### Nuxt Add it in `nuxt.config.ts` so it renders into the head on every page: ```ts [nuxt.config.ts] export default defineNuxtConfig({ app: { head: { script: [ { src: 'https://cdn.otusanalytics.com/otusanalytics/otus.js', async: true }, { innerHTML: `window.otus=window.otus||function(){(otus.q=otus.q||[]).push(arguments)},otus.init=otus.init||function(i){otus.o=i||{}}; otus.init({ siteId: 123, endpoint: "https://ingest.otusanalytics.com/e" })` } ] } } }) ``` ### Plain HTML / static sites Paste the snippet into the shared `` of your template or include file. If you use a static site generator (Hugo, Eleventy, Astro, Jekyll), add it to the base layout. ## Single-page apps No extra setup is needed. Otus automatically tracks pageviews on initial load and on every client-side route change. See [Install the tracking script](https://docs.otusanalytics.com/getting-started/install-script#single-page-apps-spas). ## Next step [Verify your installation](https://docs.otusanalytics.com/getting-started/verify-installation), then explore your [reports](https://docs.otusanalytics.com/reports/overview). --- - **Page:** Funnels - **Source:** https://docs.otusanalytics.com/reports/funnels - **Description:** Build a sequence of steps and see how many sessions make it through each one, and where they drop off. A **funnel** measures how sessions move through a sequence of steps, and where they drop off. Use it for conversion paths like *landing → pricing → sign up* or *product → cart → checkout → purchase*. ## How funnels are counted - **Per session.** Each session is checked on its own. A session ends after 30 minutes of inactivity, so the steps of a funnel need to happen in the same visit. - **In order.** A session reaches a step only when it has completed all earlier steps, in that order. A session that goes to step 3 before step 2 hasn't reached step 3 until it does step 3 again after step 2. - **Other activity is fine.** Visitors can view other pages and trigger other events between steps. Repeating a step doesn't break the funnel either. - **Every step is required.** There are no optional steps. - **Within the date range.** Only activity inside the selected date range counts. If a session started before the range, or carried on past its end, the steps outside the range are not counted. Funnels work the same way in [cookieless and full tracking mode](https://docs.otusanalytics.com/getting-started/tracking-modes). ## Build a funnel Open **Reports → Funnels** and click **New funnel**: 1. Add **2 to 8 steps**, in order. 2. For each step, choose a type:
Type Matches Example
Page path A pageview of this path, on any hostname. /pricing
Full URL A pageview of this path on this hostname. Use it when several (sub)domains share paths. Enter the hostname and path, without https:// or a query string. shop.example.com/checkout
Event A standard or custom event with this name. sign_up
3. Click **Analyze** to see the results for the selected date range. Matching is exact, with two exceptions: - A trailing slash is ignored, so `/pricing` and `/pricing/` are the same step. - For full URLs, a leading `www.` and the case of the hostname are ignored. Paths themselves are case-sensitive: `/About` and `/about` are different pages. ### Wildcards Use `*` in any step to match any characters, including none:
Step Matches
/blog/* Every page under /blog/ , e.g. /blog/launch and /blog/2026/recap
/products/*/checkout /products/shoes/checkout , /products/a/b/checkout
*.example.com/checkout /checkout on any subdomain of example.com
form_* Events such as form_submit and form_start
Because the trailing slash is ignored, `/blog/*` does not match `/blog` itself. Use `/blog*` to include it (this also matches pages like `/blogroll`). ## Saved funnels Give a funnel a name and click **Save funnel** to keep it. Saved funnels are shared with everyone on the site and appear in the funnel picker at the top of the page. The page opens on the funnel you looked at last. - **Owners and editors** can save, edit, rename and delete funnels. - **Viewers** can open saved funnels. They can also build and analyze their own funnels, but can't save them. - Names are unique per site. A site can have up to 50 saved funnels. Change the date range at any time and the funnel updates. ## Stat cards
Metric What it measures
Funnel Entry Sessions that completed the first step.
Completions Sessions that completed every step.
Completion Rate Completions ÷ entries. Called completion rate (not conversion rate) because conversion rate means converting sessions ÷ sessions everywhere else.
Biggest Drop-off The step that loses the largest share of the sessions that reached the step before it.
## Funnel chart and table The chart shows each step with the number of sessions that reached it. The table below it lists, for every step, the sessions and the **drop-off** from the previous step, as a number and a percentage. ## Tips - Keep early steps broad and later steps specific to see where intent fades. - Funnels count within a single session. To follow journeys that span several visits, compare the steps' totals in your other reports instead. - Events don't have to be registered to be used as a step, but registering them under [Custom events](https://docs.otusanalytics.com/settings-team/custom-events) lets you mark them as conversions. ## Related - [Events & Goals](https://docs.otusanalytics.com/events-goals): the events you can use as steps. - [E-commerce](https://docs.otusanalytics.com/reports/ecommerce): the purchase funnel. - [AI Chat](https://docs.otusanalytics.com/reports/ai-chat): ask about a saved funnel by name. --- - **Page:** AI Analyst - **Source:** https://docs.otusanalytics.com/reports/ai-analyst - **Description:** A written weekly report that summarises what changed on your site and why it matters. The **AI Analyst** turns your numbers into words. Every week it writes a short, plain-language report on how your site performed. The AI Analyst's weekly summary is included on **every plan**, from Starter upward. Compare tiers in [Plans & limits](https://docs.otusanalytics.com/account-billing/plans). ## What you get Each weekly report includes: - a **summary** paragraph summarizing the week, - a list of **observations**: notable changes worth your attention, - a **key metrics** table comparing pageviews, sessions, users and [bounce rate](https://docs.otusanalytics.com/reports/glossary#bounce-rate) with the week before (the same definitions as your reports; rate changes are written in percentage points), - **top movers** tables for the pages, sources, channels, countries and devices that changed most, and - metadata: the period covered, the model used, and when it was generated. Previous weeks stay available: use the week selector (or the arrows) at the top of the report to browse earlier reports. ## When it runs A new report is generated **every Monday**, covering the previous week. The first report arrives after Otus has gathered a full week of data. If you've just started, you'll see a "your first report is on its way" message. ## How it works The AI Analyst reads the same aggregated metrics you see in your reports (traffic totals, top pages, sources, channels, countries and devices) and summarises the meaningful movements. It works only with your aggregated analytics, never with personal data. ## Want answers on demand? The weekly report is a scheduled summary. If you want to *ask* questions about your data whenever you like, use the [AI Chat](https://docs.otusanalytics.com/reports/ai-chat). ## Related - [AI Chat](https://docs.otusanalytics.com/reports/ai-chat): a conversational analyst. - [Plans & limits](https://docs.otusanalytics.com/account-billing/plans): where AI features are included. --- - **Page:** Channels - **Source:** https://docs.otusanalytics.com/reports/channels - **Description:** The predefined traffic-source channels Otus assigns to every visit, and exactly how each one is determined. Every visit is classified into one of a fixed set of **channels** (Direct, Organic Search, Paid Search, and so on). Unlike some analytics tools, you can't rename or reconfigure these: they're predefined so that "Paid Search" means the same thing on every Otus account, and so the [Overview report](https://docs.otusanalytics.com/reports/overview) and [channel breakdown](https://docs.otusanalytics.com/reports/overview#breakdown-chart) are comparable across sites. The channel is decided **once, when the event is recorded** (not recalculated later), based on the page's UTM parameters, ad click IDs and referrer. A session's channel is the channel of its **first page view**, so each session counts in exactly one channel. The recognised paid search click IDs are `gclid`, `gbraid` and `wbraid` (Google Ads), `msclkid` (Microsoft Ads) and `oppref` (ChatGPT ads). `fbclid` and `ttclid` are ignored for the channel, because Facebook and TikTok also add them to links shared organically, so they don't prove a paid click. ## The channels
Channel How it's detected
Paid Search utm_medium is cpc , ppc , paidsearch or paid-search , or a paid search click ID ( gclid , gbraid , wbraid , msclkid , oppref ) is present with no UTM at all.
Paid Social utm_medium is paidsocial or paid-social .
Organic Social utm_medium is social , social-organic or organic-social , or utm_source is a recognised social platform (Facebook, Instagram, LinkedIn, X/Twitter, TikTok, Pinterest, Snapchat, Reddit, Threads, YouTube) with no paid medium set.
Email utm_medium is email , e-mail or newsletter .
Affiliate utm_medium is affiliate .
Display utm_medium is display , banner or cpm .
Organic Search utm_medium is organic , or utm_source is a recognised search engine, or, with no UTM at all, the referrer's domain is a recognised search engine (Google, Bing, Yahoo, DuckDuckGo, Baidu, Yandex, Ecosia, Startpage).
AI Assistant utm_source names a known AI assistant (e.g. chatgpt.com , which ChatGPT adds to the links it shows) with no recognised medium, or, with no UTM and no paid search click ID, the referrer is a known AI assistant or one of its subdomains (ChatGPT, Gemini, Claude, Perplexity, Copilot, Grok, Meta AI, DeepSeek, Mistral, and others). See AI Traffic .
Referral No UTM, no paid search click ID, and the referrer is any other external site.
Direct No UTM, no paid search click ID, no referrer at all (e.g. a bookmark, typed URL, or a link from an app that strips referrer information).
Other UTM parameters are present but don't match any of the medium/source rules above. Rare: it means a campaign was tagged with a utm_medium / utm_source combination outside the recognised set.
## Precedence When more than one signal is present, they're evaluated in this order: 1. **UTM parameters always win.** If `utm_source` or `utm_medium` is set, it decides the channel, even if a click ID is also present on the URL (see below). 2. **A paid search click ID with no UTM** is treated as Paid Search. This covers Google Ads' and Microsoft Ads' auto-tagging, which append a click ID to the landing URL whether or not you've also added manual UTMs. A tagged link whose `utm_source` is an AI assistant counts as AI Assistant, unless its `utm_medium` marks it as paid (for example `cpc`): ads in AI assistants stay under the paid channels. 3. **Referrer-based rules** (AI Assistant, Organic Search, Referral) only apply when there's no UTM and no paid search click ID. A tagged campaign always takes priority over what the referrer happens to be. 4. **Direct** is the fallback when there's nothing to go on at all. ## Source for ad clicks without UTMs When a visit has a paid search click ID but no UTM parameters, Otus also fills in its **source / medium**, so the source matches the Paid Search channel even when the browser didn't send a referrer (iOS apps often strip it):
Click ID Source / medium
gclid , gbraid , wbraid google / cpc
msclkid bing / cpc
oppref chatgpt.com / cpc
This only affects the source shown in reports. The [UTM parameters](https://docs.otusanalytics.com/integrations/utm-parameters) breakdown still only shows links you tagged yourself. Visits recorded before this was introduced keep their original source. Because UTMs always win, an ad campaign that's missing or has incorrect UTM parameters can land in the wrong channel (or in **Other**). See [UTM parameters](https://docs.otusanalytics.com/integrations/utm-parameters) for why tagging every campaign link matters, even when a platform auto-tags clicks for you. ## Where you'll see it The **Channel** dimension in the [Overview report](https://docs.otusanalytics.com/reports/overview)'s breakdown chart and donut chart. ## Related - [UTM parameters](https://docs.otusanalytics.com/integrations/utm-parameters): how to tag your campaigns so they're classified correctly. - [Overview report](https://docs.otusanalytics.com/reports/overview): where channel breakdowns appear. --- - **Page:** Ecommerce revenue tracking - **Source:** https://docs.otusanalytics.com/events-goals/ecommerce-tracking - **Description:** Send purchase and refund events so Otus can attribute revenue to your traffic. To see revenue in Otus, send the standard e-commerce events from your store. At minimum you need `purchase`; add the earlier funnel steps to populate the [purchase funnel](https://docs.otusanalytics.com/reports/ecommerce#purchase-funnel). Otus uses the same e-commerce format as GA4: every e-commerce event carries its products in an `items` array, and order-level details (`value`, `currency`, `transaction_id`, ...) sit next to it. If you already send GA4 e-commerce events, you can send the same objects to Otus. ## The essential event: purchase Fire a `purchase` event when an order completes, usually on your order-confirmation page: ```js otus("track", "purchase", { transaction_id: "T-12345", // unique per order value: 49.9, // order total currency: "EUR", // ISO 4217 code items: [ { item_id: "SKU-1", item_name: "Pro plan", price: 49.9, quantity: 1 }, ], }); ``` Always include a unique `transaction_id`. The transactions table groups purchases by it, so a reloaded confirmation page shows as one transaction. **Orders** count every `purchase` event, so make sure your confirmation page only sends it once. ## Refunds When an order is refunded, send a `refund` event with the original transaction ID. Refunds are subtracted to produce **net revenue**. For a partial refund, list the refunded products in `items`; for a full refund you can leave `items` out: ```js otus("track", "refund", { transaction_id: "T-12345", value: 49.9, currency: "EUR", items: [{ item_id: "SKU-1", price: 49.9, quantity: 1 }], }); ``` ## The full purchase funnel Send the intermediate steps to measure where buyers drop off: ```js const item = { item_id: "SKU-1", item_name: "Pro plan", price: 49.9, quantity: 1, }; otus("track", "view_item", { currency: "EUR", value: 49.9, items: [item] }); otus("track", "add_to_cart", { currency: "EUR", value: 49.9, items: [item] }); otus("track", "begin_checkout", { currency: "EUR", value: 49.9, items: [item], }); otus("track", "add_payment_info", { currency: "EUR", value: 49.9, payment_type: "card", items: [item], }); otus("track", "purchase", { transaction_id: "T-12345", currency: "EUR", value: 49.9, items: [item], }); ``` ## Event reference Every event needs an `items` array, except `refund`, where it's optional. **Single** events take exactly one item.
Event Items Event parameters
view_item Single currency , value
view_item_list Multiple item_list_id , item_list_name
select_item Single item_list_id , item_list_name
add_to_cart Multiple currency , value
remove_from_cart Multiple currency , value
view_cart Multiple currency , value
add_to_wishlist Multiple currency , value
begin_checkout Multiple currency , value , coupon
add_shipping_info Multiple currency , value , coupon , shipping_tier
add_payment_info Multiple currency , value , coupon , payment_type
purchase Multiple transaction_id (required), currency , value , tax , shipping , coupon , affiliation
refund Multiple (optional) transaction_id (required), currency , value , tax , shipping , coupon , affiliation
view_promotion Single promotion_id , promotion_name , creative_name , creative_slot , location_id
select_promotion Single promotion_id , promotion_name , creative_name , creative_slot , location_id
### Item parameters Each item requires an `item_id`. All other fields are optional:
Parameter Description
item_id Your product ID or SKU.
item_name Product name. The products tables group by this.
price Unit price.
quantity Number of units.
discount Discount per unit.
coupon Coupon applied to this item.
affiliation Store or supplier.
index Position of the item in a list.
item_brand Brand.
item_category … item_category5 Category hierarchy, from broad to specific.
item_variant Variant, e.g. colour or size.
item_list_id , item_list_name The list the item was shown in.
location_id Physical location, e.g. a store ID.
promotion_id , promotion_name , creative_name , creative_slot The promotion associated with the item.
You can add your own fields to an item too. Items hold up to 40 fields, and an event up to 100 items. Values must be plain strings, numbers or booleans, and follow the same [parameter limits](https://docs.otusanalytics.com/events-goals/tracking-api#parameter-limits) as other parameters. An event can be at most 32 KB in total, and a larger one is rejected. ## Currency Send a consistent ISO 4217 `currency` code (e.g. `EUR`, `USD`) on every revenue event, matching your site's configured currency, so totals add up correctly. ## What you'll see Once `purchase` events arrive, the [E-commerce report](https://docs.otusanalytics.com/reports/ecommerce) shows total and net revenue, orders, average order value, revenue over time, your top products and the purchase funnel. ## Related - [E-commerce report](https://docs.otusanalytics.com/reports/ecommerce) - [Standard events catalogue](https://docs.otusanalytics.com/events-goals/standard-events) - [Tracking API](https://docs.otusanalytics.com/events-goals/tracking-api) --- - **Page:** Filters & Segments - **Source:** https://docs.otusanalytics.com/reports/filters - **Description:** Narrow every report down to the sessions you care about, such as visitors from one country, one campaign or one landing page, and save filter combinations as segments. Filters narrow the reports down to the sessions you're interested in: visitors from the Netherlands, traffic from a newsletter campaign, sessions that viewed your pricing page, and so on. Save a combination of filters as a [segment](#segments) to apply it again with one click. ## How filters work - **Filters select sessions.** A filter keeps the sessions that match it, and every number on the report is calculated over those sessions only. For example, with *Page is /pricing*, the report shows sessions that viewed /pricing, including everything else they did in those sessions (their other pageviews, events and revenue). - **Session attributes come from the first page view.** Source, channel, UTM tags, location, device, browser, OS, language and hostname are taken from the session's first page view, the same way every report breaks sessions down. So *Country is Netherlands* matches exactly the sessions in the Netherlands row of the countries table. - **Several values are OR'ed.** *Country is Netherlands, Belgium* matches sessions from either country. - **Several filters are AND'ed.** *Country is Netherlands* and *Device is Mobile* matches mobile sessions from the Netherlands. - **One filter per field.** Choosing a field that already has a filter opens that filter so you can change it. - **Comparisons are filtered too.** When you compare with an earlier period, the earlier period uses the same filters. Filters apply to the **Overview**, **Engagement**, **Events**, **E-commerce** and **Funnels** reports. They stay active while you move between reports, and are cleared when you reload the page. **Realtime**, **AI Analyst** and **AI Chat** aren't filtered; the active filters are shown greyed out there. ## Add a filter 1. Click **Filter** at the top of a report, next to the date range. 2. Choose a field, for example **Location → Country**. 3. Choose an operator and pick one or more values. The list shows the most common values in the selected period, and takes your other filters into account. Type to search. 4. Click **Apply** (or press Enter). Active filters appear as pills below the header. Click a pill to change it, click **×** to remove it, or click **Clear** to remove all filters. You can use up to 20 filters at once. ## Operators
Operator Matches
is Exactly one of the values.
is not None of the values.
contains A value that contains one of the texts, ignoring case. You can type any text, also when it's not in the list.
does not contain No value that contains any of the texts.
For **Page**, **Event / conversion** and properties, *is not* and *does not contain* mean the session **never** matched. *Page is not /pricing* keeps sessions that didn't view /pricing at all. A value shown as **(none)** means the field was empty, for example sessions without a UTM source or with an unknown city. ## Fields
Group Field Matches
Page Page Sessions that viewed the page.
Entry page The first page of the session.
Exit page The last page of the session within the selected period.
Hostname Hostname The hostname of the first page view, for sites tracked on several (sub)domains.
Source Source The source of the session: UTM source, else the paid-search click source, else the referring site, else direct .
Channel The channel of the session.
Referrer The referring site of the session (without www . ).
AI platform The AI assistant the session came from (ChatGPT, Perplexity, Claude, ...).
UTM tags UTM source , medium , campaign , term , content The UTM parameters of the first page view.
Location Country , Region , City Where the visitor was.
Device Device Desktop, mobile, tablet or other.
Browser Browser , Browser version
Operating system Operating system , OS version
Language Language The browser language.
Event / conversion Event / conversion Sessions that triggered the event or conversion.
Visitor type Visitor type New or returning visitors. Only visitors tracked in full tracking mode can be classified, so cookieless sessions are left out when this filter is used.
Properties Event property Sessions with an event that has this event parameter value.
User property Sessions with an event that has this user property value.
Property values are compared as text, so a number or `true`/`false` matches the text you pick. Parameters that Otus sets itself (engagement time, scroll depth and the outbound link URL) and list parameters such as `items` can't be used as filters. With a filter active, refunds only count when they belong to a matching session. Without filters, refunds always count, because they're often sent from a back office without a page view. ## Segments A **segment** is a saved set of filters with a name, such as *Dutch mobile visitors* or *Newsletter readers*. Segments are shared with everyone on the site. They don't include a date range, so you can apply a segment to any period. ### Save a segment 1. Add the filters you want. 2. Click **Save as segment** next to the filters. 3. Give the segment a name and click **Save segment**. The segment is applied right away and replaces the separate filters. ### Apply a segment Click **Filter → Segments**, search for the segment or pick it from the list. Its filters apply to every report, just like separate filters. A segment and separate filters can't be combined: while a segment is applied, the other fields in the Filter menu are disabled. Clear the segment, or edit it, to change the filters. You can switch to another segment at any time. ### Manage a segment Click the segment above the report to open its menu:
Action What it does
View filters Shows the filters the segment uses.
Edit filters Shows the segment's filters as normal filters. Change, add or remove filters, then click Save segment , or Cancel to keep the segment as it was.
Rename Gives the segment a new name.
Delete Removes the segment for everyone on the site.
Clear segment Stops applying the segment (it isn't deleted).
- **Owners and editors** can save, edit, rename and delete segments. - **Viewers** can apply segments and view their filters. - Names are unique per site. A site can have up to 50 segments, with up to 20 filters each. --- - **Page:** Standard events catalogue - **Source:** https://docs.otusanalytics.com/events-goals/standard-events - **Description:** A reference of Otus's pre-defined standard events for common and e-commerce actions. Otus ships with a catalogue of **standard events**: pre-defined names for actions that most sites care about. Using them means your data lines up with Otus's built-in reports (conversions, e-commerce, funnels) without any custom configuration. Standard events don't need registering, and any of them can be marked as a conversion in **Site settings → Events & Conversions** (`form_submit`, `sign_up`, `login`, `search` and `share` are on by default). Send any standard event with the [tracking API](https://docs.otusanalytics.com/events-goals/tracking-api): ```js otus('track', 'sign_up', { method: 'email' }); ``` ## General events
Event Typical use
login A user signs in.
sign_up A user creates an account.
search A site search is performed (pass the query).
form_submit A form is submitted (leads, contact, etc.).
share Content is shared.
select_content A content item is selected.
## E-commerce events These power the [E-commerce report](https://docs.otusanalytics.com/reports/ecommerce) and revenue tracking. They follow the GA4 e-commerce format: every event carries its products in an `items` array. See [Ecommerce revenue tracking](https://docs.otusanalytics.com/events-goals/ecommerce-tracking) for the parameters of each event.
Event Typical use Items per event
view_item A product is viewed. Single
view_item_list A list/category of products is viewed. Multiple
select_item A product is selected from a list. Single
add_to_cart A product is added to the cart. Multiple
remove_from_cart A product is removed from the cart. Multiple
view_cart The cart is viewed. Multiple
add_to_wishlist A product is added to a wishlist. Multiple
begin_checkout Checkout starts. Multiple
add_shipping_info Shipping details are added. Multiple
add_payment_info Payment details are added. Multiple
purchase An order is completed. Multiple
refund An order is refunded. Multiple
view_promotion A promotion is shown. Single
select_promotion A promotion is clicked. Single
## Event parameters Standard events accept typed parameters. For example, `purchase` expects a transaction ID, a value, a currency and a list of items: ```js otus('track', 'purchase', { transaction_id: 'T-12345', value: 49.90, currency: 'EUR', items: [ { item_id: 'SKU-1', item_name: 'Pro plan', price: 49.90, quantity: 1 } ] }); ``` Stick to the standard names where one fits your use case. It keeps your reports consistent. For anything not covered, define a [custom event](https://docs.otusanalytics.com/events-goals). ## Related - [Ecommerce revenue tracking](https://docs.otusanalytics.com/events-goals/ecommerce-tracking) - [Tracking API](https://docs.otusanalytics.com/events-goals/tracking-api) - [Custom events & goals](https://docs.otusanalytics.com/events-goals) --- - **Page:** AI Chat - **Source:** https://docs.otusanalytics.com/reports/ai-chat - **Description:** Ask questions about your analytics in plain language and get instant answers. **AI Chat** is a conversational analyst for your site. Ask a question in plain language, such as "How did my traffic change over the last 30 days?", and get an answer grounded in your real data. AI Chat is available on the **Growth plan and above**. On Starter the feature is shown behind an upgrade gate. See [Plans & limits](https://docs.otusanalytics.com/account-billing/plans). ## What you can ask The assistant is good at questions like: - "What are my top 5 pages right now?" - "How did my traffic change over the last 30 days?" - "Which traffic source converts best?" - "Where are my visitors located this week?" Suggested prompts are offered to get you started. ## How it works Behind the scenes the assistant can read your analytics through a set of **read-only** tools: overview metrics, engagement, funnels and realtime. It can only *read* aggregated data for sites you have access to; it can never change settings or see personal data. ## Monthly message allowance Each plan includes a number of AI Chat messages per month: **Growth** 100, **Business** 300 and **PRO** 1,000 (Enterprise is custom). Every question you send counts as one message; if the assistant can't answer because of an error, the message isn't counted. The allowance is shared by all websites and team members in your account and resets on the 1st of every month (UTC). The chat page shows how many messages you've used this month. When you reach the limit, you can't send new messages until the allowance resets, unless you upgrade to a higher plan. ## Shared history Your conversation is saved per site and shared with other members of that site, so your team builds a shared thread of questions and answers over time. You can clear the history at any time. ## Related - [AI Analyst](https://docs.otusanalytics.com/reports/ai-analyst): scheduled weekly written reports. - [Plans & limits](https://docs.otusanalytics.com/account-billing/plans): where AI features are included. --- - **Page:** Tracking API - **Source:** https://docs.otusanalytics.com/events-goals/tracking-api - **Description:** The client-side otus() API for sending custom events, identifying users, linking events and passing consent. The [tracking snippet](https://docs.otusanalytics.com/getting-started/install-script) defines a global `otus()` function for sending your own events and attaching context. You can call it anywhere on the page at any time: calls made before the tracker has loaded are queued and sent once it has (queued consent is applied before the first page view). ## track Send a custom or standard event. ```js otus('track', eventName, params?, linkingId?) ```
Argument Type Description
eventName string The event name. Must match ^[a-z0-9][a-z0-9_]{0,63}$ : lowercase letters, numbers and underscores, up to 64 characters, not starting with an underscore. Invalid names are dropped.
params object (optional) Key/value metadata for the event. See Parameter limits .
linkingId string (optional) A key that connects this event to related events in other sessions or on other devices. See Linking events .
```js // Simple custom event otus('track', 'newsletter_signup'); // With parameters otus('track', 'signup_completed', { plan: 'growth', method: 'email' }); // A standard e-commerce event otus('track', 'add_to_cart', { currency: 'EUR', value: 49.9, items: [{ item_id: 'SKU-1', item_name: 'Pro plan', price: 49.9, quantity: 1 }] }); ``` ## identify Tells Otus which logged-in user the visitor is, so the same person is recognised as one user across devices and sessions. Call it after login, and on every page load while the user is logged in (calling it again with the same ID does nothing). ```js otus('identify', userId, props?) ```
Argument Type Description
userId string A stable, pseudonymous internal ID (1–128 characters), such as a database ID. Never an email address or name.
props object (optional) User properties to set at the same time.
```js otus('identify', 'u_8f3a2c', { plan: 'growth', role: 'admin' }); ``` User identification is only available in [full tracking](https://docs.otusanalytics.com/getting-started/tracking-modes) mode, and only takes effect once the visitor has granted [analytics consent](#setconsent):
Analytics consent What happens
Granted The user ID is stored in a cookie on your root domain, so it's shared by your subdomains, and sent with every following event.
Not answered yet The call is kept in memory and applied if the visitor grants consent on the same page. Nothing is stored or sent before that.
Denied The call is ignored.
In cookieless mode the call is ignored, with a warning in the browser console. Otus never stores the ID you send: it's replaced by a pseudonym on our servers before it's saved, and that pseudonym is what reports and [ad platforms](https://docs.otusanalytics.com/conversion-forwarding) see. Values that look like an email address are rejected. Once a browser has been identified, its earlier anonymous visits (with analytics consent) are counted towards the same user. Unique user counts for past periods can therefore drop slightly after someone logs in for the first time. If `identify` is called with a different ID than the one stored in the browser, Otus first runs [`reset`](#reset), so two people sharing a device are never merged. ## setUserProperties Attach persistent properties that are then sent with **every subsequent event** from that visitor. Useful for plan tier, account type, or experiment group. ```js otus('setUserProperties', { plan: 'growth', role: 'admin' }); ``` User properties follow the same rules as [`identify`](#identify): full tracking mode only, stored and sent once the visitor has granted analytics consent, and kept in memory until then. They're remembered in a cookie, so you don't need to set them again on every page. You don't need to call `identify` to use them. Together they can take up about 4 KB; if they're larger, they're kept for the current page only and a warning is logged in the browser console. Keep user properties and event parameters to non-identifying attributes: no names, email addresses or other personal data. Properties and parameters whose value looks like an email address are dropped. To link a person, use [`identify`](#identify). To compare logged-in visitors with everyone else, set a user property when they log in, for example `otus('identify', userId, { account_type: 'customer' })`, and filter reports on that property. ## reset Forgets the identified user and their properties, and starts a new visitor and session. Call it on logout so the next person on the same device isn't counted as the previous user. ```js otus('reset'); ``` ## Linking events The `linkingId` argument of [`track`](#track) connects events that belong together but don't happen in the same session, such as a checkout that completes in another browser after a bank app redirect, or a quote that's accepted days later on another device. Use any ID your site already has for the thing the events share:
Flow Linking ID Events
Checkout completes in another browser Cart or checkout ID begin_checkout → purchase
B2B quote Quote ID form_submit → quote_accepted
Demo request Form submission ID form_submit → demo_booked
Support Ticket ID chat_started → ticket_resolved
```js // Laptop: checkout page otus('track', 'begin_checkout', { value: 89, currency: 'EUR' }, 'cart_7f2a'); // Another browser: confirmation page after the bank app otus('track', 'purchase', { transaction_id: 'T-1042', value: 89, currency: 'EUR' }, 'cart_7f2a'); ``` When an event shares a linking ID with an earlier event in a different session (within 30 days), its conversion and revenue are credited to the earlier session's source, campaign and landing page. The purchase above is attributed to the campaign that started the checkout instead of showing up as direct traffic or a referral from the bank. - A linking ID is only kept when the visitor has granted [analytics consent](#setconsent), in either tracking mode. If you want to link events, ask for consent. - It's never stored in the browser and never sent to ad platforms. - It must not identify a person: no user ID, email address or customer number. Values that look like an email address are dropped. People are linked with [`identify`](#identify). - You don't need it for events in the same session, for a logged-in user (use `identify`), or to connect a `refund` to its `purchase` (`transaction_id` does that). ## Parameter limits These limits apply to event parameters, [user properties](#setuserproperties) and the fields of e-commerce `items`. Values that break a rule are dropped (or shortened), but the rest of the event is still recorded. The one exception is an event that's too large: it's lost completely.
What Limit When it's exceeded
Event name Lowercase letters, numbers and _ , 1–64 characters, not starting with _ The event isn't sent
Parameters per event 25 Parameters after the 25th are dropped
User properties 25 (only the first 25 are kept) Properties after the 25th are dropped
Parameter name Up to 128 characters, no . The parameter is dropped
Parameter value A string, number or boolean Other values are dropped (see below)
Text values Up to 1024 characters The text is cut off at 1024 characters
Number values Between -9,007,199,254,740,991 and 9,007,199,254,740,991 The parameter is dropped
items Up to 100 items, each with up to 40 fields that follow the same rules Extra items and fields are dropped
Event size 32 KB in total (as JSON) The whole event is lost
User ID, linking ID Up to 128 characters The ID isn't used
Email addresses Not allowed in parameters, user properties or IDs The value is dropped
Things that are dropped as values: `null`, nested objects, and lists of plain values such as `['a', 'b']`. The only list allowed is `items`, a list of objects. Send large IDs, such as order numbers or IDs from your database, as **strings**: `{ order_id: '1234567890123456789' }`. Browsers can't hold very large whole numbers exactly, so Otus drops numbers outside the range above instead of storing a rounded value. User properties are remembered in a cookie and new ones are added to the end, so once a visitor has more than 25, properties set later are never sent. Reuse a fixed set of property names instead of creating new ones, or call [`reset`](#reset) to clear them. ## setConsent Tells Otus which categories of processing a visitor has consented to. Call it from your cookie banner / consent management platform (CMP) whenever the visitor makes or changes a choice, the same way you'd call Google Consent Mode's `gtag('consent', 'update', …)`. ```js otus('setConsent', { analytics, marketing }) ```
Argument Type Description
analytics boolean (optional) Consent to store identifiers in the browser for analytics (the session ID, visitor ID, user ID and user properties used by full tracking ) and to link events across sessions.
marketing boolean (optional) Consent to keep ad click IDs ( gclid , fbclid , …) and forward events to your connected ad platforms for server-side conversion tracking (CAPI).
Only the categories you pass are changed. The choice is remembered in the `otus_consent` cookie, so you only need to call `setConsent` when the visitor makes or changes a choice, not on every page load. ### What happens before and after consent Each category is **granted**, **denied** or **not answered yet**. Otus never assumes consent: until the visitor answers, a category is treated as not granted. Visits are still counted either way, so you don't lose traffic data while a banner is open or when a visitor declines.
Analytics granted Analytics not answered / denied
Events recorded All All, anonymously
Stored in the browser Per tracking mode Nothing
Sessions Per tracking mode Server-side, cookieless-style
Returning visitors (full mode) ✅ —
User ID and user properties (full mode) ✅ — (not answered: kept in memory until granted on the same page)
Linking IDs ✅ —
Marketing granted Marketing not answered Marketing denied
Ad click IDs Full tracking: kept for 90 days in a cookie. Cookieless: read from the landing URL only Read from the landing URL only, nothing stored in the browser Ignored
Ad platform (CAPI) forwarding Immediate Held on our servers for up to 30 minutes, then forwarded if marketing is granted in that time, otherwise deleted Never
So when a visitor lands from an ad and accepts the banner a few pages later, the conversion is still attributed to the original click, and nothing was sent to the ad platform before they agreed. Withdrawing consent (`true` → `false`) removes what Otus stored for that category: the session ID, visitor ID, user ID and user properties for analytics, and stored click IDs for marketing. ```js // Visitor accepted everything otus('setConsent', { analytics: true, marketing: true }); // Visitor accepted analytics only: full reports, but nothing is ever // forwarded to Google/Meta/TikTok/OpenAI conversion APIs otus('setConsent', { analytics: true, marketing: false }); // Update one category; the other keeps its current value otus('setConsent', { marketing: false }); ``` ### Waiting for your CMP If your CMP loads at the same time as Otus, the first page view may be sent before the CMP has reported a stored choice. Add `consentWait` (milliseconds, max 10000) to `otus.init()` to hold the first page view and any events until `setConsent` is called or the time runs out, similar to Google's `wait_for_update`. It only applies when the visitor has no stored choice yet. ```js otus.init({ siteId: 123, endpoint: "https://ingest.otusanalytics.com/e", consentWait: 500 }) ``` ### Sites that don't need consent If your site is not subject to consent requirements (for example, no EU/UK visitors), add `consentDefault: "granted"`. Categories the visitor hasn't answered are then treated as granted. An explicit `setConsent` call still takes precedence. Make sure this matches your legal obligations. ```js otus.init({ siteId: 123, endpoint: "https://ingest.otusanalytics.com/e", consentDefault: "granted" }) ``` The overview report shows the share of sessions that granted, denied or never answered each category. ## Opting a visitor out To stop the tracker recording in a given browser, set the `otus_ignore` cookie on your root domain: ```js document.cookie = "otus_ignore=true; domain=example.com; path=/; max-age=34128000"; // stop tracking document.cookie = "otus_ignore=; domain=example.com; path=/; max-age=0"; // resume tracking ``` ## How events are sent Events are delivered with `fetch` and `keepalive: true`, so they survive page unloads and navigations. Requests never include cookies: the tracker reads its own cookies and sends only the values it needs. Delivery is fire-and-forget: failures never throw or interrupt your page. ## Firing events from Google Tag Manager You can call `otus('track', ...)` from a GTM Custom HTML tag tied to a trigger. See the [GTM guide](https://docs.otusanalytics.com/integrations/google-tag-manager#tracking-custom-events-from-gtm). ## Related - [Custom events & goals](https://docs.otusanalytics.com/events-goals) - [Standard events catalogue](https://docs.otusanalytics.com/events-goals/standard-events) - [Ecommerce revenue tracking](https://docs.otusanalytics.com/events-goals/ecommerce-tracking) --- - **Page:** Auto-tracked events - **Source:** https://docs.otusanalytics.com/events-goals/auto-tracked-events - **Description:** The events the Otus tracker records automatically, with no setup, triggers or configuration required. Once the tracker is installed, three events are recorded automatically for every visitor. They feed the [Overview](https://docs.otusanalytics.com/reports/overview) and [Engagement](https://docs.otusanalytics.com/reports/engagement) reports, before you send a single custom event. ## `page_view` Fires on the initial page load, and again on every subsequent navigation, including client-side (SPA) route changes to a new path, which the tracker detects by patching `pushState` and listening for `popstate` (or `hashchange` with [`hash: true`](https://docs.otusanalytics.com/getting-started/install-script#single-page-apps-spas)). You don't need to call anything from your router; this works the same whether your site is fully server-rendered or a single-page app. Each `page_view` also carries the page's [UTM parameters](https://docs.otusanalytics.com/integrations/utm-parameters) and referrer, which is how visits are assigned a [channel](https://docs.otusanalytics.com/reports/channels). ## `engagement` Fires when a visitor leaves a page (tab switched away, page hidden, or navigates on), capturing: - **duration_ms:** active time spent on the page. Time in a backgrounded or hidden tab doesn't count. - **scroll_depth_pct:** the deepest point scrolled, as a percentage of the page height. To avoid noisy duplicate events, an `engagement` event only fires again for the same page view if there's new signal: at least 3 more seconds of active engagement, or a deeper scroll than previously recorded. Tabbing away and back repeatedly on the same page doesn't generate a new event every time. This event powers **engagement time** and **time on page**, and decides whether a session is [engaged](https://docs.otusanalytics.com/reports/glossary#engaged-session) (more than 10 seconds of active time), which drives **engagement rate** and **bounce rate**. ## `outbound_click` Fires when a visitor clicks a link to another website, with the destination URL attached. Use this to see which external links or partner sites your visitors follow, without instrumenting every link by hand. Links to your own domain and its subdomains (for example from `www.example.com` to `app.example.com`) aren't outbound clicks: the visit simply continues there. See [subdomains and multiple domains](https://docs.otusanalytics.com/integrations/subdomains). ## What's not automatic Page views, engagement and outbound clicks cover navigation and attention. They don't know about actions specific to your product or store. For everything else: - **Standard events:** a catalogue of pre-defined events for common actions (`sign_up`, `login`, `search`) and e-commerce (`view_item`, `add_to_cart`, `purchase`, `refund`). Send the ones that apply to your site. - **Custom events:** anything specific to your product, sent via the [tracking API](https://docs.otusanalytics.com/events-goals/tracking-api). ## Related - [Custom events & goals](https://docs.otusanalytics.com/events-goals): the full events overview, and how to turn an event into a conversion. - [Standard events catalogue](https://docs.otusanalytics.com/events-goals/standard-events): the pre-defined event names. - [Tracking API](https://docs.otusanalytics.com/events-goals/tracking-api): how to send standard and custom events. --- - **Page:** Team & access - **Source:** https://docs.otusanalytics.com/settings-team/team-access - **Description:** Invite teammates to a site, set their roles and manage who can see your stats. Invite colleagues to a site, give them the right level of access, and collaborate on the same data, including a shared [AI Chat](https://docs.otusanalytics.com/reports/ai-chat) history. Team members are unlimited on every plan, including Starter. Invite as many teammates as you need at no extra cost. ## Invite a member 1. Open **Site settings → Team**. 2. Choose **Invite member** and enter their email address. 3. Pick a **role**. 4. Send the invitation. They'll get an email to join. ## Roles Roles determine what a member can do, from view-only access to full management of a site's settings and team. Give people the least access they need to do their job, and reserve management roles for those who configure tracking and billing. ## Agencies & freelancers If you manage analytics for clients, add each client site to your account and invite the relevant people per site. Members only see the sites they've been invited to. ## Related - [Site settings](https://docs.otusanalytics.com/settings-team) - [Plans & limits](https://docs.otusanalytics.com/account-billing/plans) --- - **Page:** Overview - **Source:** https://docs.otusanalytics.com/conversion-forwarding - **Description:** Send conversions to Google Ads, Meta, TikTok and ChatGPT from Otus's servers, without ad pixels on your site. **Conversion forwarding** sends your conversions to Google Ads, Meta, TikTok and ChatGPT from Otus's servers instead of from pixels in your visitors' browsers. Your campaigns keep optimising, and nothing from those platforms loads on your site. Conversion forwarding is available on the **Business plan and above**. See [Plans & limits](https://docs.otusanalytics.com/account-billing/plans). ## How it works 1. **Connect a platform** in **Site settings**. For Google you sign in with your Google account; for Meta, TikTok and ChatGPT you paste in an access key from their ad manager. 2. **Choose what to send.** Every event is off until you switch it on, per platform. 3. **Otus does the rest.** Standard events are translated into each platform's own format, and anything else is sent as a custom event under the name you already use. ## Only for visitors who agreed to marketing Conversions are only forwarded for visitors who gave **marketing consent**. Everyone else is still counted in your own analytics, but nothing about them goes to an ad platform. Your site therefore needs a consent banner that asks for marketing consent and passes the answer to Otus. See [consent](https://docs.otusanalytics.com/events-goals/tracking-api#setconsent). How long an ad click can be matched to a later conversion depends on the site's tracking mode. See [Attribution and tracking modes](https://docs.otusanalytics.com/conversion-forwarding/attribution). ## Matching without personal details Otus doesn't support "enhanced conversions": it never hashes and sends your customers' email addresses or phone numbers. Conversions are matched on the click ID the ad platform adds to your ad links:
Platform Click ID
Google Ads gclid , gbraid or wbraid
Meta fbclid
TikTok ttclid
ChatGPT (OpenAI Ads) oppref
## Existing pixels Otus and an ad pixel don't share an event ID, so if both send the same conversion, the platform counts it twice. For each event, either remove the pixel or switch the event off in Otus. Your site only becomes fully pixel-free once the pixels are gone. ## Next steps Link Google Ads, Meta, TikTok or ChatGPT. Switch events on per platform. How long a click can be matched to a conversion. Delivery stats, retries and paused connections. --- - **Page:** Excluding pages & traffic - **Source:** https://docs.otusanalytics.com/settings-team/exclusions - **Description:** Keep internal visits and noisy paths out of your reports. Sometimes you don't want certain visits in your stats: staging paths, admin areas, or your own team's browsing. The **Exclusions** tab in site settings lets you filter them out. ## Exclude pages Add page paths you don't want counted (for example `/admin`, `/preview` or internal tools). Matching pageviews are excluded from your reports. ## Exclude your own visits To stop the tracker recording your own browsing in a particular browser, set the opt-out cookie once in the console: ```js document.cookie = "otus_ignore=true; domain=example.com; path=/; max-age=34128000"; ``` Replace `example.com` with your own domain (without `www.`), so the opt-out applies to all your subdomains. This is the most reliable way to exclude yourself, since it stops events being sent at all. Remove it with: ```js document.cookie = "otus_ignore=; domain=example.com; path=/; max-age=0"; ``` ## Related - [Site settings](https://docs.otusanalytics.com/settings-team) - [Tracking modes](https://docs.otusanalytics.com/getting-started/tracking-modes) --- - **Page:** Events & conversions - **Source:** https://docs.otusanalytics.com/settings-team/custom-events - **Description:** Choose which standard events count as conversions, and register custom events. The **Events & Conversions** tab in site settings is where you decide which events count as **conversions** (goals) and register your custom events. ## Standard events [Standard events](https://docs.otusanalytics.com/events-goals/standard-events) (`sign_up`, `purchase`, `add_to_cart`, …) don't need registering and don't use custom event slots. Each one has a **Conversion** toggle. New sites start with `form_submit`, `sign_up`, `login`, `search` and `share` counted as conversions. Switch any of them off, or switch on others such as `purchase` or `begin_checkout`. ## Register a custom event 1. Open **Site settings → Events & Conversions**. 2. Add the event **name** exactly as you send it from your site (e.g. `signup_completed`). Names must be lowercase letters, numbers and underscores, up to 64 characters, and can't start with an underscore. 3. Optionally add a **description** so teammates know what it represents. Custom events that aren't registered are dropped. Standard event names can't be registered as custom events. ## What a conversion does Toggle **Conversion** on a standard or custom event to make it a goal. Conversions: - are counted in **Conversions** on the [Overview](https://docs.otusanalytics.com/reports/overview) and Events reports and in the channel and referrer tables, and make a session count towards the **conversion rate**, - get their own card on the Events report and are flagged in its events table, and - make a session count as **engaged**. To send conversions to Google Ads, Meta, TikTok or ChatGPT, see [Conversion forwarding](https://docs.otusanalytics.com/conversion-forwarding). Any event, conversion or not, can be used as a step in [funnels](https://docs.otusanalytics.com/reports/funnels). ## Event limits by plan The number of registered custom events you can keep depends on your plan:
Plan Custom event limit
Starter 10
Growth 50
Business 200
Enterprise Unlimited
See [Plans & limits](https://docs.otusanalytics.com/account-billing/plans) for the full comparison. ## Sending the events Registering an event here doesn't send it. Your site does that with the [tracking API](https://docs.otusanalytics.com/events-goals/tracking-api): ```js otus('track', 'signup_completed', { plan: 'growth' }); ``` ## Related - [Custom events & goals](https://docs.otusanalytics.com/events-goals) - [Tracking API](https://docs.otusanalytics.com/events-goals/tracking-api) - [Funnels](https://docs.otusanalytics.com/reports/funnels) --- - **Page:** Connect a platform - **Source:** https://docs.otusanalytics.com/conversion-forwarding/connect-platforms - **Description:** Link Google Ads, Meta, TikTok or ChatGPT (OpenAI Ads) to forward conversions. Open a site, go to **Site settings** and find the ad platform connections. Each platform is connected separately, and each site has its own connections. Connecting a platform requires the **Business plan or above**. See [Plans & limits](https://docs.otusanalytics.com/account-billing/plans). ## Google Ads 1. Choose **Connect** next to Google Ads and sign in with the Google account that has access to your Google Ads account. 2. Pick the **conversion action** that Otus should report conversions to. Conversions are matched on the click ID Google adds to your ad links: `gclid`, `gbraid` or `wbraid`. Turn on auto-tagging in Google Ads so these are added. ## Meta 1. In Meta Events Manager, find your **dataset ID** (also shown as the pixel ID) and create an **access key** for the Conversions API. 2. Paste both into the Meta connection in Otus. Conversions are matched on the click ID Meta adds to your ad links (`fbclid`), together with the visitor's browser type, which Meta requires. ## TikTok 1. In TikTok Events Manager, find your **pixel ID** and generate an **access key** for the Events API. 2. Paste both into the TikTok connection in Otus. Conversions are matched on the click ID TikTok adds to your ad links (`ttclid`). ## ChatGPT (OpenAI Ads) 1. In OpenAI Ads Manager, find your **pixel ID** and create an **API key**. 2. Paste both into the ChatGPT connection in Otus. Conversions are matched on the reference OpenAI adds when someone clicks your ad (`oppref`). ## Keys are stored encrypted Access keys are encrypted before they're stored, and Otus never shows a full key again after you've saved it: only the last four characters. To replace a key, paste in the new one. Disconnecting a platform removes its stored credentials. ## Next step [Choose which events to send](https://docs.otusanalytics.com/conversion-forwarding/choose-events) to the platform you just connected. --- - **Page:** Choose what to send - **Source:** https://docs.otusanalytics.com/conversion-forwarding/choose-events - **Description:** Switch events on per platform, and see how Otus translates them into each platform's format. Every event is **off until you switch it on**. You decide per platform what it receives, for example purchases to Google and leads to Meta. ## Switch events on 1. Open **Site settings** and go to the platform you've [connected](https://docs.otusanalytics.com/conversion-forwarding/connect-platforms). 2. Switch on the events you want that platform to receive. Only the events you switch on are forwarded, and only for visitors who agreed to marketing. ## How events are translated [Standard events](https://docs.otusanalytics.com/events-goals/standard-events) are translated into each platform's own event names automatically:
Otus event Meta TikTok ChatGPT
purchase Purchase CompletePayment order_created
sign_up CompleteRegistration CompleteRegistration registration_completed
form_submit Lead SubmitForm lead_created
add_to_cart AddToCart AddToCart items_added
begin_checkout InitiateCheckout InitiateCheckout checkout_started
view_item , view_item_list ViewContent ViewContent contents_viewed
add_payment_info AddPaymentInfo AddPaymentInfo custom event
search Search Search custom event
For Google Ads, every forwarded event is reported to the conversion action you picked when connecting. Anything else, including [custom events](https://docs.otusanalytics.com/settings-team/custom-events), is sent as a custom event under the name you already use. ## Revenue If an event carries a `value` and `currency`, such as a `purchase` with revenue, Otus includes them so the platform can report conversion value. See [e-commerce tracking](https://docs.otusanalytics.com/events-goals/ecommerce-tracking). ## Avoid double counting If a pixel on your site still sends the same event, the platform counts it twice. For each event, either remove the pixel or switch the event off in Otus. --- - **Page:** Attribution and tracking modes - **Source:** https://docs.otusanalytics.com/conversion-forwarding/attribution - **Description:** How long an ad click can be matched to a conversion, in cookieless and full tracking mode. Conversion forwarding only sends conversions for visitors who agreed to marketing. How long a click ID (`gclid`, `gbraid`, `wbraid`, `fbclid`, `ttclid`, `oppref`) can be matched to a later conversion depends on the [tracking mode](https://docs.otusanalytics.com/getting-started/tracking-modes) of the site:
Tracking mode Visitor agreed to marketing Attribution
Full tracking Yes Click ID kept in a first-party cookie for 90 days after the click. Conversions in later visits are forwarded with it, and each ad platform applies its own conversion window.
Cookieless Yes Session-based. The click ID isn't stored in the browser, so it is only matched to conversions in the same visit (30 minutes of inactivity ends a visit).
Either No Nothing is forwarded.
## Cookieless mode In cookieless mode, Otus doesn't store click IDs or identifiers in your visitors' browsers, not even when a visitor agrees to marketing. Conversion forwarding still works for those visitors, but only within the same visit: a click ID can only be matched to a conversion that happens before the visit ends. ## Full tracking mode If you want conversions in later visits to count, use full tracking mode. The click ID is then kept in a first-party cookie (`otus__cid`) for 90 days after the click, the same as the ad platforms' own cookies, and sent with every conversion. Each platform only counts conversions within its own conversion window. For Meta, Otus also sends when the click happened, as Meta requires. ## Before the visitor answers Visitors often answer the consent banner a few seconds or pages after landing, while the click ID is only in the URL of the landing page. Until the visitor answers, Otus holds that visit's conversions on its servers. They're forwarded once the visitor agrees to marketing, and deleted if they decline or don't answer before the visit ends. --- - **Page:** Delivery and troubleshooting - **Source:** https://docs.otusanalytics.com/conversion-forwarding/delivery - **Description:** Check delivery stats, and what happens when a platform is unavailable or rejects your access key. ## Delivery stats Each connection shows how many conversions were **sent** and how many **failed** in the last 7 days. ## Temporary errors are retried If a platform is temporarily unavailable or asks Otus to slow down, the delivery is retried automatically, following the platform's own retry hint when it gives one. A conversion that still fails after several attempts is counted as failed. ## Rejected access keys If a platform rejects your access key, for example because it was revoked or expired, Otus **pauses that connection** and flags it in **Site settings**. Retrying with the same key can't succeed, so nothing is sent until you fix it: 1. Create a new access key in the platform's ad manager (for Google, sign in again). 2. Paste it into the connection in Otus. This way your conversions don't quietly stop arriving. ## Nothing arrives at the platform? - **Plan:** conversion forwarding needs the Business plan or above. - **Events:** check that the event is [switched on](https://docs.otusanalytics.com/conversion-forwarding/choose-events) for that platform. - **Consent:** conversions are only sent for visitors who agreed to marketing. Check that your consent banner passes marketing consent to Otus. See [consent](https://docs.otusanalytics.com/events-goals/tracking-api#setconsent). - **Click ID:** the visitor must have arrived through an ad link with the platform's click ID. For Google Ads, make sure auto-tagging is on. - **Attribution window:** in cookieless mode, the conversion must happen in the same visit as the ad click. See [Attribution and tracking modes](https://docs.otusanalytics.com/conversion-forwarding/attribution). --- - **Page:** Account settings - **Source:** https://docs.otusanalytics.com/account-billing - **Description:** Manage your personal Otus account: email, password and two-factor authentication. Your **account settings** apply to you as a person, across every site you have access to. They're separate from [site settings](https://docs.otusanalytics.com/settings-team), which configure an individual website. ## What lives here - **Email address:** your login address. - **Password:** change it any time. - **Two-factor authentication (2FA):** add a second step at sign-in for extra security. - **Subscription & billing:** your plan, usage and invoices. ## Two-factor authentication We strongly recommend enabling 2FA. Once set up, signing in requires both your password and a one-time code from your authenticator app, so a leaked password alone isn't enough to access your account. ## Changing your email or password You can update your login email and your password from account settings at any time. For security you may be asked to re-authenticate. ## Related - [Plans & limits](https://docs.otusanalytics.com/account-billing/plans) - [Billing & invoices](https://docs.otusanalytics.com/account-billing/billing) --- - **Page:** Plans & limits - **Source:** https://docs.otusanalytics.com/account-billing/plans - **Description:** Compare Otus Analytics tiers: monthly event limits, AI features, data export, conversion API access and data retention. Otus has five plans. They differ in your **monthly event allowance**, how many **websites** and **custom events** you can register, access to **AI Chat**, **data export**, the **Conversion API**, **data retention**, and the level of **support**. There are no overage fees, and going over your event allowance never locks your dashboard. ## Compare plans
Starter Growth Business PRO Enterprise
Monthly €9 €24 €49 €99 Custom
Yearly €90 €240 €490 €990 Custom
Events/mo 100,000 500,000 1,000,000 5,000,000 5,000,000+
Websites 1 3 10 Unlimited Unlimited
Custom events 10 50 200 500 Unlimited
AI Weekly summary Weekly summary + AI Chat Weekly summary + AI Chat Weekly summary + AI Chat Custom limits
AI Chat messages/mo – 100 300 1,000 Custom
Data export – ✅ ✅ ✅ ✅
Data retention 1 year 2 years 3 years 5 years Custom
Conversion forwarding – – ✅ ✅ ✅
Support – Email Email Email + implementation Dedicated + extensive implementation
Pay yearly and get **two months free** compared to paying monthly. Prices exclude VAT/sales tax, which is calculated at checkout based on your location (see [Billing & invoices](https://docs.otusanalytics.com/account-billing/billing)). The **monthly event cap is account-level**. It's shared across all the websites in your account, not per site. The **website limit** is also account-level: Starter includes 1 site, Growth 3, Business 10, and PRO and Enterprise are unlimited. **Team members are unlimited on every plan.** Invite as many teammates as you need. See [Team & access](https://docs.otusanalytics.com/settings-team/team-access). ## What counts as an event Every tracked action counts toward your allowance: pageviews, engagement events, outbound clicks and any custom or standard events you send. Keep this in mind if you send a lot of custom events. Go over your allowance and we tell you. There are no overage fees and your dashboard is never locked. ## AI features Every plan includes the [AI Analyst](https://docs.otusanalytics.com/reports/ai-analyst)'s weekly written summary. [AI Chat](https://docs.otusanalytics.com/reports/ai-chat), the conversational analyst, is included from **Growth** upward. Each plan includes a monthly number of AI Chat messages: **Growth** 100, **Business** 300 and **PRO** 1,000. Enterprise plans can negotiate custom usage limits for AI features. Like the event cap, the allowance is **account-level**: it's shared by all websites and team members in your account. It resets on the 1st of every month (UTC), and you can see how much you've used in AI Chat and under **Account → Subscription**. ## Data export CSV data export is included from **Growth** upward. Starter doesn't include data export. ## Conversion API Server-side ad conversion forwarding (Conversion API) is included from **Business** upward. See [Conversion forwarding](https://docs.otusanalytics.com/conversion-forwarding). ## Data retention Each plan determines how far back you can query your analytics: **Starter** keeps 1 year, **Growth** 2 years, **Business** 3 years, **PRO** 5 years, and **Enterprise** is custom. Reports won't return data older than your plan's window. **Year-over-year comparisons** need at least 24 months of history, so they're available on **Growth and above**. Starter's 1-year window is too short. Upgrade to add year-over-year. ## Free trial New accounts get a **30-day free trial** so you can explore Otus before subscribing. See [Trial & billing](https://docs.otusanalytics.com/account-billing/billing) for what happens when the trial ends. ## Changing plans Upgrade or downgrade any time from **Account → Subscription**. Upgrades take effect immediately so you get the higher limits and features right away. You can also switch between monthly and yearly billing at any time. ## Related - [Billing & invoices](https://docs.otusanalytics.com/account-billing/billing) - [Managing custom events](https://docs.otusanalytics.com/settings-team/custom-events) - [AI Analyst](https://docs.otusanalytics.com/reports/ai-analyst) · [AI Chat](https://docs.otusanalytics.com/reports/ai-chat) --- - **Page:** Billing & invoices - **Source:** https://docs.otusanalytics.com/account-billing/billing - **Description:** Manage your subscription, payment method and download invoices. Manage everything about your subscription from **Account → Subscription & billing**. ## Who bills you Our order process is run by **Paddle.com**, our online reseller and merchant of record. Paddle handles checkout, payments, sales tax/VAT, invoices and payment-related customer service. Your bank statement and invoices will show Paddle as the seller. ## From trial to paid New accounts start on a **30-day free trial**, no card required. Before it ends, choose a [plan](https://docs.otusanalytics.com/account-billing/plans) and complete the checkout to keep your data flowing. Subscribing during the trial charges you right away and ends the trial. If the trial ends without a subscription, tracking for your sites pauses until you subscribe. Your dashboards stay available. ## Prices, currency and tax Our list prices are in EUR and **exclude VAT/sales tax**. At checkout Paddle shows the price in your local currency and adds the tax that applies where you are. Buying for a business? Enter your **VAT number** at checkout; where reverse charge applies, no VAT is charged. You can pay by card, PayPal, Apple Pay or Google Pay. ## Monthly or yearly Every plan can be billed **monthly** or **yearly**. Paying yearly gets you **two months free** compared to paying monthly for the same plan. You can switch between the two from the billing screen at any time. ## Change your plan Switch plans from the billing screen at any time. We show you exactly what will be charged or credited before you confirm. - **Upgrades** apply immediately. You pay the prorated difference for the rest of the current billing period. - **Downgrades** also apply immediately. The unused part of your current plan is credited against your next invoices. You can't downgrade to a plan whose limits you're already over (for example more sites than the plan allows). Remove the extra sites or custom events first. ## Payment method and billing details Use **Update payment method** and **Billing details** on the billing screen to change your card, billing address or VAT number. These open Paddle's secure customer portal. ## Failed payments If a renewal payment fails, Paddle retries it automatically over the following weeks and emails you so you can update your payment method. Your plan stays fully active in the meantime. If the payment still can't be collected, the subscription is cancelled and tracking pauses until you subscribe again. ## Cancelling Use **Cancel subscription** on the billing screen. Your plan stays active until the end of the period you've paid for. After that, tracking stops and your dashboards remain available. You can subscribe again at any time. ## Invoices Paddle emails you a receipt with an invoice for every charge. You can also download every invoice as a PDF from the billing screen. ## Usage & limits Your plan includes a monthly event allowance shared across all your sites. There are no overage fees and going over your allowance never locks your dashboard. See [Plans & limits](https://docs.otusanalytics.com/account-billing/plans). ## Related - [Plans & limits](https://docs.otusanalytics.com/account-billing/plans) - [Account settings](https://docs.otusanalytics.com/account-billing) --- - **Page:** MCP server - **Source:** https://docs.otusanalytics.com/ai/mcp - **Description:** Connect Claude, Cursor, VS Code and other AI tools to the Otus Analytics docs with MCP. The Otus Analytics docs include an [MCP](https://modelcontextprotocol.io/) (Model Context Protocol) server. Connect it to your AI assistant and it can search and read these docs while it answers your questions. This helps when you're installing the tracker, setting up events or troubleshooting. The MCP server gives access to the **documentation** only. It can't read your analytics data or change your account. ## Server address The server uses the Streamable HTTP transport and needs no authentication: ```txt https://docs.otusanalytics.com/mcp ``` ## Available tools
Tool What it does
list_pages Lists the docs pages with their titles and descriptions.
search_pages Searches all pages for a word or phrase, such as consent mode or ecommerce .
get_page_markdown Returns the full content of one page as Markdown.
You don't need to call these yourself. Your assistant chooses when to use them, for example when you ask "How do I track purchases with Otus?" ## Setup ### Claude Code Run: ```bash claude mcp add --transport http otus-docs https://docs.otusanalytics.com/mcp ``` ### Claude (web and desktop) 1. Open **Settings** > **Connectors**. 2. Click **Add custom connector**. 3. Enter `Otus Analytics Docs` as the name and `https://docs.otusanalytics.com/mcp` as the URL. ### ChatGPT 1. Open **Settings** > **Apps & Connectors** and turn on **Developer mode** under **Advanced settings**. 2. Click **Create** and enter `https://docs.otusanalytics.com/mcp` as the MCP server URL, with no authentication. ### Cursor Create or update `.cursor/mcp.json` in your project, or `~/.cursor/mcp.json` to use it in every project: ```json [.cursor/mcp.json] { "mcpServers": { "otus-docs": { "type": "http", "url": "https://docs.otusanalytics.com/mcp" } } } ``` ### Visual Studio Code Make sure GitHub Copilot Chat is installed, then create or update `.vscode/mcp.json`: ```json [.vscode/mcp.json] { "servers": { "otus-docs": { "type": "http", "url": "https://docs.otusanalytics.com/mcp" } } } ``` ### Windsurf 1. Open **Windsurf Settings** > **Cascade** and click **Manage MCPs**. 2. Select **View raw config** and add: ```json [mcp_config.json] { "mcpServers": { "otus-docs": { "serverUrl": "https://docs.otusanalytics.com/mcp" } } } ``` ### Zed Add a context server to your Zed settings: ```json [settings.json] { "context_servers": { "otus-docs": { "url": "https://docs.otusanalytics.com/mcp" } } } ``` ### Other tools Any MCP client that supports remote servers over HTTP works with the address above. If your tool only supports local (stdio) servers, use [`mcp-remote`](https://www.npmjs.com/package/mcp-remote): ```bash npx mcp-remote https://docs.otusanalytics.com/mcp ``` ## Without MCP If your assistant doesn't support MCP, you can still give it the docs: - Add `.md` to the end of any docs URL to get the page as Markdown. - Use [`/llms.txt`](https://docs.otusanalytics.com/llms.txt) for an index of every page, or [`/llms-full.txt`](https://docs.otusanalytics.com/llms-full.txt) for the complete docs in one file. - Use **Copy page**, **Open in ChatGPT** or **Open in Claude** at the top of any page. ## Discovery AI agents that support automatic discovery can find the server through its server card at [`/.well-known/mcp.json`](https://docs.otusanalytics.com/.well-known/mcp.json).