Skip to main content

Activation Insights

Activation Insights offers analysis dedicated to your Activation performance. This article will present you how it works and how to get the best out of your implementation.

How it works

Activation Insights merge data from various Piano products into Piano Analytics data model. To provide a comprehensive understanding of how Activation Insights work, let's break down the process step-by-step:

  1. Piano SDKs implemented on the application (web, mobile, ...) send events to Piano backends. These events include user interactions and other relevant data points that help track the activation journey. All those events share 2 key IDs allowing us to correlate them across different systems:
    1. Browser ID: also called Visitor ID, represent a unique ID linked to a specific browser. (idclient querystring property)
    2. Pageview ID: this unique ID is generated for each pageview or screen view within an application and links all events that occur on the same page or screen. (pageview_id event property)
  2. Activation backends process these events, enrich them and send them to Piano Analytics.
  3. These events are then processed by Piano Analytics, which uses advanced algorithms to analyze patterns, user journeys, and interactions.

Implementation

Javascript SDKs automatically share Pageview ID (pageview_id) and Browser ID (idclient) since version 6.7.0.