Event scope or visit scope?
The event scope is opposed to the visit scope for several aspects of Piano Analytics.
Properties
A property with an event scope may vary for each event of the visit. For example, the "Page" property is at event scope, with each new page loaded the property value can change.
A visit scope property retains the same value throughout a visit. For example, the "Source" property is a visit scope property. The value assigned to this property does not change regardless of the event analyzed in the visit. If we receive multiple sources from a visit, we will always keep the first one.
New: pageview scope (between event and visit)
In addition to event and visit, some properties can be available at pageview scope:
Pageview scope properties are propagated to all events occurring during the same page load, identified by
pageview_id.
Pageview scope is typically available for events coming from the JavaScript SDK (where a browser page load is clearly identifiable). In environments where pageview_id is not available (commonly mobile SDKs), properties generally behave closer to event scope (values can differ from one event to another within the same visit).
Metrics
The operation is similar for metrics, the visit scope does not change within a visit and the event scope can change with each event of the visit.
For example, the "Page Views" metric counts the page loads made during the visit and will vary in function of the analyzed element.
While the "Visits" or the "Bounce Rate" metrics are calculated on complete visits and not event by event.
Segments
In order to offer you all the flexibility, the segmentation offers you 7 types of scope:
The visit scope, which corresponds to identifying a criterion (or several) and reporting all the events carried out during the visit corresponding to the criterion.
The visitor scope, which corresponds to identifying one (or more) criteria and reporting all the events carried out by the visitor corresponding to the criterion.
The user scope, which corresponds to identifying one (or more) criteria and to reporting all the events carried out by the user corresponding to the criterion.
The event scope, which corresponds to identifying one (or more) criteria and reporting all the events corresponding to the criterion. This segmentation is comparable to a filter.
The audio/video session scope, which corresponds to identifying one (or more) criteria and reporting all the events corresponding to the criterion during a single av_sessionid.
The carts scope, which corresponds to identifying one (or more) criteria and reporting all the events corresponding to the criterion during a single cart_id.
The page scope, which corresponds to identifying one (or more) criteria and reporting all the events corresponding to the criterion during a single page_viewid.
The different scopes of the segments are covered in this article of our documentation.