UTM tracking in Piwik PRO
Piwik PRO is a privacy-oriented analytics suite (the commercial relative of Matomo) with built-in consent management. Its Analytics module reads standard UTM parameters to attribute campaigns and also supports configuring custom campaign parameter names, so you can report acquisition channels in a consent-aware, EU-hostable stack.
Recognized campaign parameters
Piwik PRO Analytics recognizes standard UTM parameters (utm_source, utm_medium, utm_campaign, utm_content, utm_term) for acquisition reporting. It also lets administrators configure additional campaign parameter names, which is useful when migrating from legacy tagging schemes.
Because attribution derives from the URL, the parameters must be present on the landing pageview that Piwik PRO records.
- Standard UTM parameters recognized out of the box
- Custom campaign parameter names configurable
- Attribution derived from the landing pageview URL
Consent interaction
Piwik PRO's Consent Manager can gate analytics processing. If a visitor declines analytics consent, the campaign pageview may not be recorded in full, so campaign totals reflect consented traffic per your configuration.
Document this so stakeholders read campaign numbers as consent-scoped, and keep UTM tags lowercase and consistent for clean acquisition rows.
How it appears in analytics and logs
A campaign appearing in Piwik PRO's acquisition reports confirms the landing URL carried recognized campaign parameters; if a campaign is missing, the parameter name may not be in the recognized set or consent gated the pageview.
Diagnostic use case
Attribute campaigns in a consent-first Piwik PRO deployment using standard UTM parameters, optionally extending the recognized parameter set for legacy tags.
What WebmasterID can help detect
WebmasterID aligns with Piwik PRO's consent-aware posture by recording the UTM-tagged landing hit as a campaign touch server-side, without cookies or a cross-site identifier.
Common mistakes
- Using non-standard parameter names without registering them in Piwik PRO.
- Reading campaign totals as full traffic when consent gating applies.
- Inconsistent casing fragmenting acquisition reports.
Privacy and accuracy notes
Piwik PRO is built around consent and data ownership; UTM values describe the campaign, not the person. Where consent is declined, processing is limited accordingly, and WebmasterID likewise records the touch without exact location or visitor identity.
Related pages
- UTM tracking in Matomo
Matomo supports campaign tracking through its own mtm_ parameters and can also be configured to read the standard utm_ parameters. The mtm_campaign and mtm_keyword tags map to Matomo's Campaigns reports, while utm_ values can be mapped via Matomo's campaign parameter settings. This page covers how Matomo consumes both schemes and where the data surfaces.
- UTM and cookie consent banners
Cookie consent banners often block analytics scripts from running until a visitor consents. Because UTM attribution happens when the analytics script reads the landing URL, a consent gate can cause the campaign to be missed if the visitor navigates away or the UTM is gone before consent is granted. This page explains the interaction and mitigations.
- UTM parameters and consent
Consent banners and consent-mode setups change when and how campaign data is recorded. UTM parameters live in the URL regardless of consent, but whether they are written into a cookie-based analytics tool depends on the visitor's choice. This page explains keeping UTM attribution privacy-safe and consent-aware.
- Privacy-first analytics
Attribute campaigns in a consent-aware analytics model.
Sources and verification notes
- Piwik PRO Help — Campaign tracking parametersDocuments recognized UTM parameters and custom campaign parameter configuration.
Last reviewed 2026-06-24. Facts are checked against primary/official sources where available; uncertain specifics are marked “Data not yet verified” rather than guessed.