Piano collects and utilizes data related to your subscribers as a method of measuring user engagement, tracking conversions, and better understanding audience demographics among other use cases. This data may then be leveraged to optimize conversion funnels or for ancillary reporting purposes.
When users first browse to a Piano-powered site, we generate and install cookies related to the user authentication state, browser, access state, and session timeout. For an overview of each of these cookies and their specific uses, please see here.
Page Load Data
|
Data |
Description |
|
Zone |
Indicates the zone of the site used for AAM reporting. |
|
User Agent |
Specifies which platform (e.g. mobile/desktop), OS (e.g. iOS/Windows), and browser (Edge/Safari) used to view the page. |
|
URL |
The URL of the pageview. |
|
Timestamp |
The UTC time at which the pageview occurred. |
|
User |
Refers to the associated user. |
|
Tags |
Publisher-defined tags for organizing and segmenting content. |
|
Submission Type |
Records if the pageview was submitted by 1st-party Piano tools or by customer-driven workflows (e.g. APIs) |
|
Submission Count |
Used for correctly calculating first and last page attributions, as well as the number of times a given page has been viewed. |
|
Source |
Indicates if the pageview event occurred within Composer or within within Piano’s JS SDK. |
|
Accessible Resources |
Tracks which resources a user has access to at the time of the pageview. |
|
Region |
Region based on IP address. |
|
Referrer |
Indicates the referring site for the user (e.g. Facebook, Google, Reddit…) |
|
Referrer Segment |
Indicates the user segment based on the referral source (e.g. Search, Social, Direct….) |
|
Pageview |
Uniquely identifies a pageview by a given end user |
|
First Visit |
Identifies users browsing to the page who have not previously been on the site |
|
IP |
The client browser’s IP address |
|
Content Access |
Indicates whether or not the user has any active access on the site |
|
DMA Code |
Indicates the DMA of the end user. |
|
Custom Parameters |
Custom publisher data related to the user, the content they are viewing, or integration-specific data. |
|
Country |
Country based on client IP address. |
|
Content Section |
Publisher-driven content tags (http://vx.piano.io/javascript-tracking) |
|
Native Content |
Indicates if content is native or if it is sponsored (e.g. advertisements) |
|
Content |
Allows the publisher to uniquely identify the currently displayed content piece from others |
|
City |
Identifies the city of the end user based on their IP address |
|
AMP URL |
Identifies the Google AMP project URL when integrated |
|
Ad Blocker Status |
Indicates if the browser has an adblocker, and whether or not ad blocking is enabled |
|
Accessed Resources |
Identifies which resources of the site a given user has visited |
Address Data
|
Data |
Description |
|
User |
Refers to the associated user. |
|
User Address(es) |
Maintains a list of known addresses for the user, including Street, City, State/Region, Zip Code, Phone Number, and Country. |
User Consent
|
Data |
Description |
|
Timestamp |
Time/date the consent was checked in UTC |
|
User |
Refers to the associated user. |
|
Grant |
The specific consent item for which access is granted/not granted |
Payment Data
|
Data |
Description |
|
Base Amount |
The actual amount of the transaction. Note that this value tracks the absolute value of transaction. For example, this value may indicate a refund versus an actual purchase |
|
Tax Amount |
The amount of sales tax charged |
|
Base Currency |
The currency of the transaction. Example values include: USD, EUR, and GBP |
|
Payment Method |
Information on the type of payment (e.g. Credit Card/Visa, Paypal, etc…) for the transaction and any associated expiry date(s) |
|
Payment Status |
Whether the payment was completed. Possible values include: disputed, and verified |
|
Payment Type |
Indicates the type of transaction. Possible values include: user payment, auto-renewal, and refund |
|
Resource |
Maintains a list of Piano resources to which access is either granted or locked depending on subscription status |
|
Subscription |
Maintains the relationship between a given payment and associated subscription records. |
|
Term |
Indicates the term selected during conversion. |
|
User |
Refers to the associated user. |
|
Timestamp |
Time and date in UTC when the record was created at source |
Subscription Data
|
Data |
Description |
|
Timestamp |
This is the time and date in UTC when the subscription in Subscription Management + Billing was processed. |
|
Start Date |
The start date and time of the current subscription (UTC). |
|
End Date |
This is the planned end date and time (UTC) of the subscription at the time of creation of this subscription event. |
|
Migrated Date |
The date the subscription was migrated from a third-party system |
|
Auto Renew |
A boolean flag that, if set, indicates that the subscription is set to auto-renew. |
|
User |
Refers to the associated user. |
|
Resource |
Details any resources that are included as part of the subscription, and whether or not access should be allowed or blocked (in case of any refunds). |
|
Trial End Date |
Indicates if the subscription is a trial subscription and the date on which it expires. |
|
Term |
Maintains information related to the converted term, including length of access, billing intervals, currency, and amount charged. |
|
Promotion |
Manages information related to any promotional terms used during conversion, including type of discount, and the promo code used (if applicable). |
|
Billing Period |
Details the length of a given billing period. |
|
PSC |
Contains information related to print subscriber data, whether or not a PSC record was successfully matched automatically, and the associated PSC data. |