Piano Analytics

Datafly Signal delivers events to Piano Analytics (formerly AT Internet) server-to-server using the Collection API. This sends page views, on-site search, clicks, and the full Sales Insights ecommerce funnel directly from your infrastructure — no client-side SDK, immune to ad blockers and browser tracking prevention.

Prerequisites

Before configuring Piano Analytics in Signal, you need an active Piano Analytics property and two pieces of information.

Step 1: Find your Site ID

1. Sign in to Piano Analytics.
2. Open the property you want to send data to.
3. Note the numeric Site ID (also called s) from your property settings. It looks like 123456789.

Step 2: Find your Collection Domain

Piano assigns each organisation a dedicated collection domain so data is only ingested on hosts you own.

1. In Piano Analytics, go to Data Collection > Collection Domains.
2. Copy your assigned domain (for example xxxxxxxx.pa-cd.com).
3. Use the domain without https:// and without a trailing slash.

Configure in Signal

Configuration Fields

Management UI Setup

API Endpoint

POST https://{collection_domain}/event?s={site_id}&idclient={visitor_id}
Content-Type: text/plain

The request body is a JSON object containing an events array. Each event has a dotted name and a data object of snake_case properties:

{
  "events": [
    {
      "name": "page.display",
      "data": {
        "page": "Homepage",
        "page_full_name": "https://example.com/",
        "user_id": "user-123"
      }
    }
  ]
}

Identity Signals

Piano Analytics matches events to a visitor using the idclient value — a stable per-visitor identifier passed as a URL query parameter.

How to identify a user

Call datafly.identify() when a user logs in or registers:

datafly.identify("user-123");

Signal sends the supplied ID as user_id. The visitor’s idclient remains stable across sessions so logged-out and logged-in activity are linked.

Consent

Signal maps the visitor’s canonical marketing consent to Piano’s two consent properties on every event, so your Piano privacy treatment and exemption rules apply correctly:

Event Mapping

Default preset

Retail preset

To customise, edit the integration’s Field Mappings in the Management UI.

Example: Purchase event

Datafly.js call:

datafly.track("Order Completed", {
  order_id: "TXN-001",
  cart_id: "CART-9",
  revenue: 129.99,
  currency: "EUR",
  coupon: "SUMMER10",
  payment_method: "card"
});

Piano Analytics Collection API request sent by Signal:

POST https://xxxxxxxx.pa-cd.com/event?s=123456789&idclient=9e8d6d5f-143a-4a21-a7d5-7348b56e130d
Content-Type: text/plain

{
  "events": [
    {
      "name": "transaction.confirmation",
      "data": {
        "idclient": "9e8d6d5f-143a-4a21-a7d5-7348b56e130d",
        "cart_id": "CART-9",
        "transaction_id": "TXN-001",
        "cart_currency": "EUR",
        "cart_turnovertaxincluded": 129.99,
        "transaction_promocode": "SUMMER10",
        "payment_mode": "card",
        "visitor_privacy_mode": "optin",
        "visitor_privacy_consent": "true"
      }
    }
  ]
}

Testing

Troubleshooting