Integrations / Analytics
Piwik PRO
Server-side event tracking via the Piwik PRO Tracking HTTP API (ppms.php). Delivers pageviews, custom events, and ecommerce orders to your own Piwik PRO instance with IP-resolved geo (cip), user-agent (ua), visitor-ID stitching (_id/cid), User ID (uid), and locale (lang).
Datafly Signal delivers first-party events to Piwik PRO server-to-server from infrastructure you control, using a pre-built blueprint that maps your event schema to the payload Piwik PRO expects.
Why route Piwik PRO 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 Piwik PRO receives the complete event stream.
Client IP and user agent are carried in the payload
Both are taken from the original visitor request rather than your server, which is what Piwik PRO needs to attribute the event to the right session.
One consent decision governs every destination
Piwik PRO 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_cartpagepurchasesearchsign_upview_itemVertical presets
Default. 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 Piwik PRO documentation.
Frequently asked questions
Does Datafly Signal integrate with Piwik PRO?
Yes. Datafly Signal delivers first-party events to Piwik PRO server-to-server from infrastructure you control, using a pre-built blueprint that maps your event schema to the payload Piwik PRO expects. The integration is included in every deployment at no additional cost.
How is server-side Piwik PRO tracking different from the Piwik PRO tag?
The Piwik PRO 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 Piwik PRO from your server, so delivery does not depend on browser conditions.
Which events can Signal send to Piwik PRO?
The blueprint ships with mappings for add_to_cart, page, purchase, search, sign_up, view_item. Any event in your schema can be mapped to Piwik PRO through pipeline configuration without a code change.
Do I need to keep the Piwik PRO tag on my site?
No. Signal delivers to Piwik PRO from the server, so no client-side Piwik PRO script is required on your site.
Other analytics integrations
Ready to move Piwik PRO server-side?
See how Datafly Signal delivers first-party events to Piwik PRO from infrastructure you control, with hashed identity and consent enforcement built in.