There are two types of metering controlled by Piano:
-
Client-side - for anonymous visitors and logged-in/authenticated users
-
Server-side - only for logged-in/authenticated users
Server-side metering, sometimes called cross-device metering, centralizes pageview counting for logged-in users so their meter stays consistent across devices and browsers.
By default, metering is client-side: the count is stored in a browser cookie on each device. A logged-in user can effectively reset their meter by switching browsers, devices, or using private browsing. Server-side metering stores the meter value against the user's Piano identity instead, so the count follows the user across surfaces.
The only difference between server-side and client-side metering is that client-side metering works only per device. That means that logged-in users will not share the meter count across devices. This is only possible with server-side metering.
This feature can be enabled for the app from Piano's side without any additional configuration steps on your end. To enable server-side metering please reach out to Piano Support at support@piano.io.
Server-side metering only works for registered/signed-in users and is supported for Identity Management, Identity Linking, and UserRef user management integrations. For anonymous visitors, client-side metering is applied. We will merge the client meter with the sever meter, which means that the existing meter will not be reset.
It’s important, that the xbc cookie is not deleted or reset, as these are domain-based and not based on the individual subdomain.
The meter management works on sub-domains.
Server-side metering operates everywhere Piano scripts run, including:
-
Your website (desktop and mobile browsers)
-
Mobile SDK (apps)
-
AMP
-
Facebook Instant Articles
What to expect after enabling
-
Cross-device meter tracking works immediately for logged-in users.
-
Existing meters are not reset. When server-side metering is turned on, the existing client-side meter is merged with the new server-side meter. Logged-in users continue from where they left off rather than starting fresh.
-
Meter reset schedule is unchanged. Your meter configuration still governs how often the meter resets (for example, every 30 days, depending on your setup).