Skip to main content
An event is one thing that happened: a pageview, a product view, an add to cart, a completed order. Events are what every report is built from. A person is Soran’s view of one customer across those events. Soran assigns a visitor an identifier stored in a first-party cookie on your domain, so returning visits join the same person rather than starting a new one. When your store spans more than one domain, that identifier is carried across the hop, so a visitor who crosses from your site to your checkout stays one person instead of becoming two. Once someone identifies themselves — by ordering, most often — Soran ties the anonymous history that preceded it to the same person. That is what makes it possible to look at a customer and see the whole path that led to the purchase, not just the session that closed it.

​
Where to see them

Event logs shows raw events as they arrive, which is the screen to use when you are checking whether tracking works. Persons lets you look up one customer and read their history.

Sessions and touchpoints

How events group into visits, and which visit gets credit.