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.

Why route Piano Analytics through Datafly Signal

• Your numbers stop depending on what the browser allows. Client-side analytics loses every visit where the tag is blocked or the page unloads early. Signal delivers from the server, so Piano Analytics receives the complete event stream.
• Delivery is batched, rate-limited, and retried. Signal buffers to Kafka, respects the Piano Analytics rate limit, and retries on 429 or transient failure rather than dropping the event.
• Presets for Default and Retail. The mapping starts from a working configuration for your vertical instead of a blank field map.
• One consent decision governs every destination. Piano Analytics is gated by the same consent state as the rest of your stack, so a withdrawal applies everywhere at once.

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

Signal uses the Collection API’s documented GET form, which carries the per-visitor idclient in the query string with the site ID and the events:

GET https://{collection_domain}/event?s={site_id}&idclient={visitor_id}&events=[{"name":"page.display","data":{...}}]

(events is URL-encoded.) One Signal event per request; a purchase carries transaction.confirmation and a product.purchased whose items_list Piano splits into one event per product, in the same events array. Only what the preset maps is sent.

Identity Signals

No personal data is sent.

Consent

Signal maps the visitor’s analytics consent to Piano’s consent properties on every event:

exempt requires Piano’s ePrivacy exemption to be enabled on your account. Adjust the value map on the installed integration if your organisation uses other modes.

Event Mapping

Every event carries user_id, device_timestamp_utc (event time, Unix seconds), src_medium and src_campaign (from the UTM medium and campaign) and the two consent properties.

Custom events and properties must exist in your Piano data model. Currency is upper-cased.

Example: purchase

datafly.track("purchase", {
  transaction_id: "TXN-001", value: 129.99, currency: "eur", coupon: "SUMMER10",
  items: [{ item_id: "SKU-A", price: 129.99, quantity: 1 }]
});

GET https://xxxxxxxx.pa-cd.com/event?s=123456789&idclient=9e8d6d5f-143a-4a21-a7d5-7348b56e130d
    &events=[{"name":"transaction.confirmation","data":{"transaction_id":"TXN-001","cart_currency":"EUR",
    "cart_turnovertaxincluded":129.99,"cart_quantity":1,"cart_nbdistinctproduct":1,"transaction_promocode":["SUMMER10"],
    "user_id":"user-123","device_timestamp_utc":1717628400,"visitor_privacy_mode":"optin","visitor_privacy_consent":true}},
    {"name":"product.purchased","data":{"transaction_id":"TXN-001","transaction_promocode":["SUMMER10"],
    "items_list":[{"product_id":"SKU-A","product_pricetaxincluded":129.99,"product_quantity":1}],
    "user_id":"user-123","device_timestamp_utc":1717628400,"visitor_privacy_mode":"optin","visitor_privacy_consent":true}}]

Testing

Troubleshooting