Check it’s working

A few minutes, end to end: a visit, an event, and a sale traced back to the visit.

The first visit#

Open your site in a private window (your everyday browser may be the one you told odo to ignore). In odo, Settings → Websites says Receiving visits with the time of the last one, and the Traffic dashboard takes over from its setup screen as soon as the first visit arrives. You’re on the live map, and among the visitors online: anyone active in the last 3 minutes.

Nothing yet? In the private window, check that:

1. The page’s source has odo’s tag, with your site’s id in data-site.
2. The browser’s network tab shows odo.js loading and a request to /api/event answered with 202.
3. The page isn’t on localhost (add data-local to measure there), and its domain is the site’s, one of its subdomains, or one of its other hosts.
4. No ad blocker stops it. See ad blockers.

An event#

In the private window’s console, send one:

odo('Test', { from: 'console' })

It shows in the Events card within a few seconds. Tap it to see the properties it came with.

A sale#

With a source connected, a sale reaches the counter when the source next syncs: within a minute for Stripe. To check the tracing too, buy something through your own checkout from the private window. Stripe’s test mode works for this: connect a test key as a source of its own (it counts as self-reported) and pay with the card 4242 4242 4242 4242.

The sale then shows with the visit it was traced to: where that visitor came from, and the pages before they paid. If it couldn’t be traced, the Sales from visits card says so, and why when it knows (a Stripe key that can’t read what tracing needs, say). See trace each sale to its visit.

From an AI assistant#

Once an assistant is connected, ask it: “What does odo see on my site today?” It calls list_projects and get_traffic, and should name today’s visitors and where they came from.