Start with the questions you need to answer
Installing tools without a measurement plan produces many events and little direction. The first document should list the decisions the data needs to support: which channel brought the visit, which offer the visitor saw, which action initiated contact, whether customer service followed up, and which outcome was confirmed.
Every question needs a source and an owner. The browser observes one part of the journey; the advertising platform observes another; the customer-service team understands lead quality; and finance confirms revenue. No single dashboard automatically captures the full picture.
- The business question being answered.
- The event or record that provides evidence.
- Source system and identifier available.
- The owner, review frequency, and known limitations.
Name events after what actually happened
A useful event describes an observable action, such as a submitted form, a phone-number click, or a conversation started. Avoid names that assume commercial value, such as “qualified lead,” when qualification has not yet occurred in the responsible system.
Parameters complement context: form, page, campaign or contact type. Taxonomy needs to be short, documented and stable. Rename events without migration breaks comparisons and can duplicate signals.
- A clear verb and object.
- A reproducible trigger condition.
- Required parameters without undue personal data.
- Rule for versions, changes and deactivation.
Preserve source data without promising perfect attribution
UTMs and click identifiers help transport context between ad and page. Redirections, consent, browsers, multiple devices and long journeys may interrupt this reading. Therefore, attribution is a model with limits, not an absolute reconstruction of reality.
Standardize names, preserve parameters on required routes and capture only what has been authorized and is useful. In the service, ask origin when appropriate and reconcile with technical records without forcing a non-existent correspondence.
- A minimal, documented UTM convention.
- Parameter testing after redirects or route changes.
- Consent choices respected before applicable tags load.
- Report with unknowns and visible limitations.
Validation and governance keep the system reliable
Tags break when forms, themes, domains or integrations change. Create a test routine that runs the journey, registers evidence, and compares tool, destination, and service. Permissions and ownership of accounts are also part of quality.
The plan should tell who can publish tags, who approves purposes, where the versions are and when to review. Responsible measurement collects what is necessary, respects consent choices and does not transform the absence of data into an estimated number without explanation.
- Inventory of tags, events and destinations.
- Testing after website or campaign changes.
- Organization-owned access and the principle of least privilege.
- History of changes, incidents and corrections.
Reference sources
- Google Analytics — — accessed on 6 September 2026.
- Google Analytics — Recommended Events — accessed on 6 September 2026.
- ANPD — Guides and Guidelines — accessed on 6 September 2026.