Integrations / Analytics
Piano Analytics
Server-side event collection to the Piano Analytics (formerly AT Internet) Collection API. Delivers page displays, on-site search, clicks, and the Sales Insights ecommerce funnel (product impressions, cart, transaction) as dotted Piano events with snake_case data properties, plus visitor consent state (visitor_privacy_mode / visitor_privacy_consent).
Datafly Signal delivers first-party events to Piano Analytics server-to-server from infrastructure you control, using a pre-built blueprint that maps your event schema to the payload Piano Analytics expects.
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.
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.
What ships in the blueprint
Mapped events
add_to_cartelement_clickedpagepurchasesearchview_cartview_itemVertical presets
Default, Retail. Each preset starts from a working configuration for that vertical rather than a blank field map.
Full field mappings, configuration fields, and troubleshooting are in the Piano Analytics documentation.
Frequently asked questions
Does Datafly Signal integrate with Piano Analytics?
Yes. Datafly Signal delivers first-party events to Piano Analytics server-to-server from infrastructure you control, using a pre-built blueprint that maps your event schema to the payload Piano Analytics expects. The integration is included in every deployment at no additional cost.
How is server-side Piano Analytics tracking different from the Piano Analytics tag?
The Piano Analytics tag runs in the visitor's browser, so it is subject to ad blockers, tracking prevention, and page-unload races. Signal collects the event through a first-party endpoint on your own domain and delivers it to Piano Analytics from your server, so delivery does not depend on browser conditions.
Which events can Signal send to Piano Analytics?
The blueprint ships with mappings for add_to_cart, element_clicked, page, purchase, search, view_cart, view_item. Any event in your schema can be mapped to Piano Analytics through pipeline configuration without a code change.
Do I need to keep the Piano Analytics tag on my site?
No. Signal delivers to Piano Analytics from the server, so no client-side Piano Analytics script is required on your site.
Other analytics integrations
Ready to move Piano Analytics server-side?
See how Datafly Signal delivers first-party events to Piano Analytics from infrastructure you control, with hashed identity and consent enforcement built in.