Activation Insights is not enabled automatically when you start using Piano Analytics. Each site that you want covered must be connected manually, on the back end.
Prerequisites
Before requesting Activation Insights enablement for a site, make sure the following are in place:
-
Composer SDK installed. The Composer SDK (
piano.jsortinypass.js) must be deployed on the site. -
Piano Analytics SDK version 6.13 or higher — if you want to send page.display or any other events from the PA SDK. Earlier SDK versions are not compatible with the current Activation Insights data stream. Verify your deployed version before requesting activation.
-
Consent Management Platform (CMP) integration — not compulsory if Privacy is not in place in your country. Your CMP must expose an "Analytics Measurement" purpose. Activation Insights uses this purpose to determine whether to forward events to Piano Analytics. Without it, no Activation Insights data will be sent regardless of how the site is otherwise configured.
-
A Piano Application ID (AID). Activation Insights is enabled per AID, so you'll need the AID for each site you want to connect (connecting 2 AID to 1 Piano Analytics site ID is also possible).
Granularity: AID-to-Site-ID mapping
Activation Insights connects a Composer Application ID (AID) to a Piano Analytics Site ID. The mapping is many-to-one: a single Site ID can receive data from several AIDs, but a single AID cannot be split across multiple Site IDs.
The practical implications:
-
One AID → one Site ID. Each AID's data flows into exactly one Site ID. You cannot route the same AID's data to two different Site IDs (for example, to keep separate production and reporting copies) — choose the Site ID up front.
-
Multiple AIDs → one Site ID is fine. If you're adding a new AID and already have a Site ID that's the right scope for it, you can reuse the existing Site ID rather than creating a new one. The new AID's data will join the existing Site ID's stream alongside any other AIDs already mapped to it.
-
No sub-Site-ID granularity. Activation Insights cannot be enabled for a specific platform, subdomain, or section within a Site ID. Any segmentation finer than the Site ID has to be done through properties on the events themselves, not through the AID-to-Site-ID mapping.
When deciding whether to reuse an existing Site ID or request a new one for a fresh AID, ask: will the audiences, content, and reporting needs of the new AID be analyzed alongside the existing ones, or separately? If alongside, reuse the Site ID; if separately, request a new one during the enablement process.
Supported environments
|
Environment |
Activation Insights enablement |
|---|---|
|
Production |
Supported |
|
Staging / pre-production |
Supported (per request) |
|
Composer Sandbox |
Not supported — the Activation Insights connector is not activated for the Sandbox environment, and data from the Sandbox cannot be sent to Piano Analytics via Activation Insights. |
If you need to test Activation Insights behavior, use a pre-production or staging site (with the prerequisites above met), not the Composer Sandbox.
Step-by-step enablement
For each new site:
-
Confirm all prerequisites above are met.
-
Collect the required information: the Application ID, the corresponding Piano Analytics Site ID, and the environment (production / staging).
-
Inform your Account Manager. Provide the AID, the Site ID, the environment, and any specific board access requirements (for example, A/B test data integration — see "Integrating A/B test data" below).
-
Piano back-end connection. Support performs a one-time backend connection between the Composer Application ID and the Piano Analytics Site ID. This is what the per-site enablement actually consists of.
-
Verify data flow. Once the connection is in place, Activation Insights data should begin appearing in Piano Analytics. Allow at least a few hours after enablement before troubleshooting missing data; see the dedicated troubleshooting article for what to check.
Decoupling Activation Insights from a test environment
If you have enabled Activation Insights on a test environment for evaluation and now want to prevent data from flowing into Piano Analytics from that environment, contact Piano Support to deactivate the connector for that AID. This is the only way to fully stop the data flow — it is not configurable from the Piano Analytics interface.