Connect Piwik Pro
In the client’s workspace, open Sources, add Piwik Pro and choose the account to sync. If you don’t have access to the account, send the client a connect link where the platform supports one.
Analytics integration
Turn event-level analytics, sessions, and attribution data into 102 governed metrics for dashboards, agent answers, and cross-channel reporting.
What you can do with Piwik Pro in Maven
Maven models Piwik Pro into 102 governed metrics from the semantic layer. Track Key Events, Acquisition Active Users, Acquisition Conversions, Acquisition Engaged Sessions and Acquisition Engagement Duration, break results down by Account, Source, Medium and Channel, and report Piwik Pro alongside Google Ads, Facebook Ads and Google Search Console without rebuilding exports or metric logic for every report.
What you can measure
Maven keeps Piwik Pro numbers consistent across dashboards, reports, and answers so the team is not debating which spreadsheet is right.
GA4 key events; for Piwik Pro this mirrors mapped lead/form-submit conversion events.
Active users by source/medium/channel/campaign acquisition scope
Conversions by source/medium/channel/campaign acquisition scope
Engaged sessions by source/medium/channel/campaign acquisition scope
Engagement duration by source/medium/channel/campaign acquisition scope
Events by source/medium/channel/campaign acquisition scope
New users by source/medium/channel/campaign acquisition scope
Pageviews by source/medium/channel/campaign acquisition scope
Sessions by source/medium/channel/campaign acquisition scope
Users by source/medium/channel/campaign acquisition scope
Re-aggregatable distinct first-time users by acquisition scope via HLL sketch
Re-aggregatable distinct users by source/medium/channel/campaign acquisition scope via HLL sketch
Active web analytics users
Share of sessions that were not engaged (1 - engaged sessions / sessions) from the primary web provider. Aggregate (GA4 Data API / grouped import) definition that serves web_bounce_rate for workspaces whose web analytics source is data_api.
Web conversion events from GA4 or mapped Piwik Pro lead and form events. Aggregate (GA4 Data API / grouped import) definition that serves web_conversions for workspaces whose web analytics source is data_api.
Engaged web analytics sessions. Aggregate (GA4 Data API / grouped import) definition that serves web_engaged_sessions for workspaces whose web analytics source is data_api.
User engagement duration in seconds from the primary web provider. Aggregate (GA4 Data API / grouped import) definition that serves web_engagement_duration for workspaces whose web analytics source is data_api.
Engaged sessions divided by sessions from the primary web provider. Aggregate (GA4 Data API / grouped import) definition that serves web_engagement_rate for workspaces whose web analytics source is data_api.
Web analytics events from the primary provider unless grouped by platform. Aggregate (GA4 Data API / grouped import) definition that serves web_events for workspaces whose web analytics source is data_api.
First-time users from the primary web analytics provider. Aggregate (GA4 Data API / grouped import) definition that serves web_new_users for workspaces whose web analytics source is data_api.
Page views from the primary web analytics provider unless grouped by platform. Aggregate (GA4 Data API / grouped import) definition that serves web_pageviews for workspaces whose web analytics source is data_api.
Sessions from the primary web analytics provider unless grouped by platform. Aggregate (GA4 Data API / grouped import) definition that serves web_sessions for workspaces whose web analytics source is data_api.
GA4 purchase revenue in reporting_currency from the primary web analytics provider
GA4 ecommerce purchase events from the primary web analytics provider
GA4 total revenue in reporting_currency from the primary web analytics provider
Users from the primary web analytics provider unless grouped by platform
GA4 transaction events with purchase revenue from the primary web analytics provider
Re-aggregatable distinct first-time users via HLL sketch
Re-aggregatable distinct users via HLL sketch (Piwik and GA4-export workspaces) that stays correct across dates and dimensions unlike the non-additive web_total_users
Analytics-observed transaction shipping in reporting_currency, from the primary web provider. GA4 Data API only today; null for raw-event and unsupported sources. This is tracked transaction shipping, not operational order-system shipping. Matomo ecommerceOrder is a follow-up candidate; abandoned carts are excluded.
Analytics-observed transaction tax in reporting_currency, from the primary web provider. GA4 Data API only today; null for raw-event and unsupported sources. This is tracked transaction tax, not operational order-system tax. Matomo ecommerceOrder is a follow-up candidate; abandoned carts are excluded.
Common key/conversion event count inferred from event naming.
Event count.
Event value when the provider reports one.
Opt-ins divided by unique page views
Opt-ins attributed to ClickFunnels pages
All ClickFunnels page views
Recurring sales attributed to ClickFunnels pages
Recurring sales value attributed to ClickFunnels pages
Sales attributed to ClickFunnels pages
Sales divided by unique page views
Sales value attributed to ClickFunnels pages
Unique ClickFunnels page views
Active users by page or landing-page context
Conversions by page or landing-page context
Engaged sessions by page or landing-page context
Engagement duration by page or landing-page context
Events by page or landing-page context
New users by page or landing-page context
Sessions by page or landing-page context
Users by page or landing-page context
Re-aggregatable distinct first-time users by page or landing-page context via HLL sketch
Re-aggregatable distinct users by page or landing-page context via HLL sketch
Page views by page or landing-page context
Share of sessions that were not engaged (1 - engaged sessions / sessions). Raw events; the primary raw source unless grouped by platform, bot/internal/non-production traffic excluded by default.
Conversions divided by sessions. Raw events; the primary raw source unless grouped by platform, bot/internal/non-production traffic excluded by default.
Events matching the conversion-definition history (GA4 key events, Piwik PRO goals, PostHog actions). Raw events; the primary raw source unless grouped by platform, bot/internal/non-production traffic excluded by default.
Sessions the source marks engaged. Raw events; the primary raw source unless grouped by platform, bot/internal/non-production traffic excluded by default.
Engagement time in seconds as recorded by the source. Raw events; the primary raw source unless grouped by platform, bot/internal/non-production traffic excluded by default.
Engaged sessions divided by sessions. Raw events; the primary raw source unless grouped by platform, bot/internal/non-production traffic excluded by default.
Every recorded event. Raw events; the primary raw source unless grouped by platform, bot/internal/non-production traffic excluded by default.
Devices whose first visit the source recorded (the source's new-user flag, else first_visit / first_open), counted once. Raw events; the primary raw source unless grouped by platform, bot/internal/non-production traffic excluded by default.
page_view events, attributed to the session landing page. Raw events; the primary raw source unless grouped by platform, bot/internal/non-production traffic excluded by default.
Event revenue as recorded by the source. Raw events; the primary raw source unless grouped by platform, bot/internal/non-production traffic excluded by default.
Sessions, counted once on their entry date. Raw events; the primary raw source unless grouped by platform, bot/internal/non-production traffic excluded by default.
Distinct resolved people (login when known, else device) with a session, counted once across the range and grouping. Raw events; the primary raw source unless grouped by platform, bot/internal/non-production traffic excluded by default.
Sessions that started on the page. Raw events; the primary raw source unless grouped by platform, bot/internal/non-production traffic excluded by default.
Exits divided by page views of the page. Raw events; the primary raw source unless grouped by platform, bot/internal/non-production traffic excluded by default.
Sessions that ended on the page. Raw events; the primary raw source unless grouped by platform, bot/internal/non-production traffic excluded by default.
Page and screen views inside a session, by the page that was viewed. Raw events; the primary raw source unless grouped by platform, bot/internal/non-production traffic excluded by default.
Sessions that started on the page. Raw events; the primary raw source unless grouped by platform, bot/internal/non-production traffic excluded by default.
Sessions that ended on the page. Raw events; the primary raw source unless grouped by platform, bot/internal/non-production traffic excluded by default.
Exits divided by page views of the page. Raw events; the primary raw source unless grouped by platform, bot/internal/non-production traffic excluded by default.
Fractional conversion credit under the first-touch model by conversion touchpoint
Fractional conversion credit under the last-touch model by conversion touchpoint
Fractional conversion credit under the linear model by conversion touchpoint
Fractional conversion credit under the data-driven Markov removal-effect model by conversion touchpoint
Fractional conversion credit under the position-based model by conversion touchpoint
Fractional conversion credit under the data-driven Shapley-value model by conversion touchpoint
Fractional conversion credit under the time-decay model by conversion touchpoint
Canonical conversion/lead events counted through normalized last-touch weights
Source-neutral interactions that were answered
Average duration in seconds among answered interactions
Average session duration in seconds with each session counted once
Touchpoints that opened a session
Share of represented interactions that were answered
Source-neutral interactions represented as attribution touchpoints
Touchpoints that closed a session
Phone interactions that were neither answered nor sent to voicemail
Total interaction duration in seconds
Journey touchpoint events recorded before conversion credit allocation
Source-neutral interactions that reached voicemail
Tracked Piwik or native GA4 event occurrences at event grain; filter event_name and platform as needed. Not unique lead submissions.
Event-name aggregate of web key/conversion events inferred from event names.
Event-name aggregate from GA4 or Piwik Pro; use web_events for channel/source analysis.
Event-name aggregate of provider-reported event value.
Questions you can ask
Maven’s agent answers in plain language with the right metric definitions applied automatically. These are real, verified questions it can run today.
How many sessions did each channel drive in the last 30 days?
Show web events by channel
Show web engagement duration by landing page
Compare linear attribution weights by channel
Show attribution touchpoints by source
Connection and sync
You connect Piwik Pro with API credentials from the Piwik Pro account. Maven stores them encrypted. The first Piwik Pro sync pulls the most recent 30 days so the workspace fills quickly. A follow-up backfill then adds older history, up to 2 years in total. After that, each scheduled sync re-reads the last 3 days, so late changes are picked up.
Raw event-level data — pageviews, custom events, ecommerce actions.
Fields: timestamp, event URL, event title, event type, event index, custom event category, custom event action, custom event name, custom event value, device type, and 51 more
Daily snapshot of goal (conversion) definitions.
Fields: goal uuid, name, description, trigger type, pattern, pattern type, case sensitive, allow multiple, revenue, definition hash, and 1 more
Daily snapshot of custom dimension definitions; names the event_custom_dimension_N / session_custom_dimension_N keys in piwik_pro_events.custom_dimensions.
Fields: dimension uuid, scope, slot, name, description, active, data type, case sensitive, created at, updated at, and 1 more
How it works
No SQL or warehouse setup. Connect the source, then build the client’s report by asking Claude or ChatGPT.
In the client’s workspace, open Sources, add Piwik Pro and choose the account to sync. If you don’t have access to the account, send the client a connect link where the platform supports one.
Maven pulls the client’s Piwik Pro data (1 objects) and models it into documented tables. No SQL, warehouse or pipeline setup.
Build the client’s report or deck by asking Claude or ChatGPT through the MCP, set alerts on what matters, and publish to the client’s portal once you approve it.
Works well with
FAQ
Maven exposes 102 governed Piwik Pro metrics, including Key Events, Acquisition Active Users, Acquisition Conversions, Acquisition Engaged Sessions, Acquisition Engagement Duration and Acquisition Events — each defined once so it means the same thing in every report.
You can break Piwik Pro metrics down by Account, Source, Medium, Channel, Campaign, Landing page, Device and Country, and more.
Yes. Piwik Pro sits in the same client workspace as sources like Google Ads, Facebook Ads, Google Search Console, Shopify and HubSpot, so one report or question can use them together.
Maven syncs piwik Pro web analytics events from Piwik Pro.
Maven refreshes Piwik Pro on a schedule after the source is connected, and shows each source’s last sync time in the client’s workspace, so you can check the data is current before a report goes out.
Yes. Maven encrypts integration credentials and tokens, scopes access to the workspace, and uses the connection only to sync the reporting data needed for governed analytics.
Set up your first client, build their report by asking Claude or ChatGPT, and publish it to their portal.
Nothing is charged unless you subscribe.