Piwik PRO implementation · privacy · data control

A Piwik PRO implementation with data privacy at the centre.

I design and implement analytics systems for organisations that need stronger control over how data is collected, stored and used. This is particularly relevant in healthcare, finance, the public sector and other high-privacy environments.

I connect Piwik PRO Analytics, Tag Manager and Consent Manager with a measurement plan, testing and documentation. The scope is agreed with IT, analytics and privacy stakeholders.

Describe the current measurement Compare GA4 and Piwik events
Plan before configurationKPIs, events and sources of truth are agreed
Consent connected to tagsconsent states and measurement behaviour are tested
QA and accountabilitytest report, documentation and change owners

Qualification

When Piwik PRO is the right direction.

We do not select a platform merely because it is European or different from GA4. First we verify data, consent, reporting and maintenance requirements.

Location and retention matter

The organisation needs an explicit choice of region, hosting option, retention and access conditions.

Consent must work with measurement

Consent states, categories, tags and collected data must form one testable process.

The environment has high requirements

Finance, healthcare, the public sector or a large organisation needs roles, documentation and auditable changes.

GA4 needs migration or comparison

We need to choose the events, map definitions and decide how long both systems should run.

Data must feed BI

Reporting requires an API, export or integration with Power BI, Looker Studio, BigQuery or another store.

Several teams use the data

Marketing, product, analytics and compliance need shared definitions, permissions and a change process.

When should you not begin with a platform change?

When the main issues are disputed KPIs, an unstable dataLayer or no measurement owner. A new tool would reproduce old problems in a new interface.

See measurement planning

Platform scope

Modules connect around one measurement model.

The exact scope depends on the Piwik PRO plan and organisational needs. Not every project requires every layer from day one.

01 · Core

Analytics

Sites and apps, events, goals, e-commerce, campaigns, segments and reports aligned to agreed KPIs.

02 · Collection

Tag Manager

Tags, triggers, variables, environments and a publishing standard tied to the dataLayer specification.

03 · Consent

Consent Manager

Consent interface, categories, tag behaviour and scenarios based on the model approved by the client.

04 · Optional

Data Activation

Activation and marketing integrations when available in the selected plan and justified by the use case.

Integrations selected per projectGoogle Ads, Google Search Console, Power BI, Looker Studio, BigQuery and other options supported by the chosen plan.
Compare analytics platforms

Choose the path

New implementation, migration or dual tracking.

The decision affects the schedule, dataLayer, comparison method and the point at which the previous system is retired.

No stable measurement

New implementation

We build the event model and configuration without copying historic errors.

Priority: plan and dataLayer
GA4 is to be replaced

Migration

We map events and reports, test differences and retire GA4 only after acceptance.

Priority: continuity and mapping
Systems run in parallel

Dual tracking

We define shared inputs, system-specific definitions and rules for interpreting discrepancies.

Priority: cost and source of truth

Process

From requirements to measurement the team can maintain.

  1. 01

    Qualification and requirements

    Objectives, current analytics, Piwik PRO plan, hosting, retention, consent, integration and access requirements.

    Outcome: scope and architecture
  2. 02

    Measurement model and mapping

    KPIs, events, parameters, goals, e-commerce, campaigns and GA4 mapping where migration is in scope.

    Outcome: specification
  3. 03

    Module configuration

    Analytics, Tag Manager, Consent Manager and the agreed integrations and reports.

    Outcome: test environment
  4. 04

    QA and reconciliation

    Consent scenarios, events, parameters, duplicates, e-commerce and comparison with a reference system.

    Outcome: acceptance report
  5. 05

    Release and handover

    Documentation, roles, training, change process, monitoring and a decision about the future of GA4.

    Outcome: maintainable measurement

Tangible outcome

One event, one shared definition and two systems.

For migration or dual tracking, names alone are not enough. We agree meaning, trigger, parameters and test method.

Critical eventpurchasee-commerce
DefinitionConfirmed order

Sent after a stable transaction identifier is assigned.

Piwik PROE-commerce order

Order ID, revenue, currency, products and agreed fields.

GA4purchase

transaction_id, value, currency, items and relevant parameters.

TestOne transaction, one event

Complete values, no duplicates and reconciliation with the backend.

Acceptance criteria

Ready means tested, documented and assigned.

Exact tolerances depend on sources, consent and the selected path. We agree them before configuration begins.

Events match the specificationtrigger, name, scope and parameters pass the QA scenarios
Consent states are testedtags react according to the approved consent model
E-commerce has a reference sourcetransactions and revenue reconcile with the backend or ERP
Cross-system discrepancies are explainedGA4 and Piwik PRO need not report identical values
Access matches the rolespublishing, configuration and reporting have appropriate owners
Changes are reproducibledocumentation covers configuration, tests and maintenance

Honest limitations

What the platform alone does not guarantee.

  • It does not automatically provide legal compliance.The consent model, legal basis and policies are approved by the client or its adviser.
  • It does not automatically mean EU hosting.Region and hosting option must be confirmed for the chosen plan and contract.
  • It does not recreate historical data.New measurement starts at publication; report migration requires a separate plan.
  • It will not produce identical results to GA4.The systems differ in sessions, attribution, consent, filters and processing.
  • It does not repair dataLayer gaps.The platform needs reliable input data and stable identifiers.
  • Not every plan includes every integration.Availability, limits and data direction are verified before pricing.
Krzysztof Surowiecki

One accountable consultant

I connect business requirements, configuration and data acceptance.

I lead the project personally at the intersection of marketing, analytics, compliance and development. The Piwik PRO configuration therefore follows agreed definitions—not a feature checklist.

20+years of experience
150+analytics and data projects
50+clients

Figures cover my broader analytics and data practice, not only Piwik PRO implementations.

Before we talk

Frequently asked questions.

Can Piwik PRO replace GA4 completely?

It can become the primary analytics platform, but the decision depends on reporting, advertising integrations, team needs and data use. Requirements are mapped before the point at which GA4 is retired.

Is dual tracking worth running?

Yes, when you need a comparison period, a safer migration or both systems have different roles. It also increases implementation, QA and interpretation cost, so it needs an end date and exit criterion.

Does Consent Manager provide GDPR compliance?

Not on its own. I implement the approved consent model and tag behaviour. Legal basis, interface copy and policies are approved by the client or legal adviser.

Can we reuse the current GA4 dataLayer?

Often yes. I first assess stability and completeness, then map it to the Piwik PRO model. A separate dataLayer is not required merely because the analytics tool changes.

Can the implementation include Power BI or BigQuery?

It may include agreed integrations or exports supported by the selected plan. A BI report and data model are scoped separately from the analytics configuration.

How long does implementation take?

It depends on sites, events, integrations, migration path, dataLayer condition and developer availability. After qualification I define stages, dependencies and a realistic schedule.

First step

Start with requirements—not by copying tags.

Describe the current analytics, hosting and consent requirements, number of sites and reports that must work after the change.

Discuss the implementation See ongoing support

Prepare for the project

Check mapping and requirements.

GA4 and Piwik PRO mappingevents, parameters and model differencesOpen the mapping Analytics platforms comparisonGA4, Piwik PRO and other measurement optionsCompare platforms DataLayer generatorsample e-commerce event structureGenerate a dataLayer