Security, Privacy, AI and CSR information for all Piano products now lives in one place. Explore our Compliance Center.
Analytics
English French
English French

What is a Visitor?

When talking about Digital Analytics, a “visitor” is not a person per se. It's a browser or an app on a device, which Piano Analytics identifies by its browser ID or phone ID. One person can reach your content on a computer, a smartphone and a tablet, so they can be counted as several visitors. For example, a reader who checks your site on their phone in the morning and on their laptop at work counts as two visitors.

A visitor is counted as soon as they generate at least one event. The Visitors metric counts unique visitors. It's a distinct count of visitor IDs over the selected period.

Identification on browsers

On web and mobile browsers, Piano Analytics creates a unique visitor ID in one of two ways:

  • Server-side cookie: Piano Analytics stores the ID in a cookie (idrxvr, atid or atidx) on one of two domains, .xiti.com or .ati-host.net. The ID is sent in the headers of Piano Analytics hits, and it lets you report across domains.

  • Client-side cookie: Piano Analytics stores the ID in a cookie on your own domain. The ID is unique per domain (or subdomain), so it doesn't let you report across domains.

If a visitor clears their cookies or uses private browsing, they may be counted as a new visitor next time.

All Piano Analytics cookies are listed in the developer documentation.

Identification in mobile apps

In mobile apps, Piano Analytics uses an ID based on the phone and the app. The ID is stored on the phone, sent in the &idclient= parameter of the app's hits, and unique to each phone and app pair. You can choose which ID to use:

OS

ID

Behavior

Android

Android ID

Provided by the phone. It stays the same even if the app is deleted and reinstalled.

Android

Advertising ID

Provided by Google. It's unique, but the user can reset it. If the user turns off ad tracking, they can't be identified.

Android

UUID

Your own ID. See Custom visitor IDs.

iOS

IDFV

Shared across all apps from the same publisher.

iOS

IDFA

Unique to the phone.

iOS

UUID

Your own ID. See Custom visitor IDs.

Custom visitor IDs

To identify visitors with your own ID, for example to count the same person as one visitor across devices, generate the ID yourself:

  • On browsers: store it in the _pcid cookie if you use the Piano Analytics SDK. You can also set it with a native SDK method. When you use client-side cookies, the ID must be sent in the &idclient= parameter. If a hit contains this parameter, it takes priority over the server-side cookie.

  • In mobile apps: define your own ID, called the UUID.

For implementation details, see Visitor identification.

Visitors without cookies

If a visitor's browser refuses cookies, no ID can be sent through the idrxvr cookie or the &idclient= parameter. The exception is the consent exemption with a client-side cookie.

Otherwise, Piano Analytics identifies the visitor from their IP address combined with their User-Agent, or with their Client Hints if the User-Agent isn't available. See this documentation for details. This is less reliable than cookies, so Piano Analytics limits it to daily granularity.

When cookies are blocked, a visitor's ID can't be kept reliably from one visit to the next. This can increase the number of unique visitors, for example by counting a new visitor at each visit. Analyses that depend on identifying visitors, such as per-visitor metrics and attribution, may also be affected.

Visitor analysis

To see how many visitors you have, use the Visitors metric. To see what individual visitors did, use the Visitor ID property.

The Visitor ID property is hidden when you use the consent exemption.

Last updated: