The question “can we measure more?” is incomplete. The right discussion starts with why each piece of data is needed, who will use it and which decision it will change. When the purpose is unclear, collection expands without improving understanding.
Write down the decision you want to support
For every event or field, record the business question. If nobody can say which action will change, the data is a candidate for removal. Usefulness alone does not justify every kind of processing, but a lack of usefulness is a clear warning sign.
Make consent understandable
Choices should explain what happens in language users understand. Avoid vague categories and designs that push people towards acceptance. Refusal and withdrawal need to be real choices, rather than theoretical options hidden behind a difficult journey.
Design for the minimum necessary
Collect only the level of detail and retention period required for the specific use. An aggregate signal is often sufficient where a user identifier creates unnecessary risk. Limit access, retention and copying across tools.
Record the loss of visibility
Reports should explain which behaviour remains unobserved. Do not present a partial dataset as a complete picture. Use ranges, comparable trends and qualitative signals, avoiding arbitrary “reconstruction” of people who did not consent.
Align marketing, legal and development
An event's name, its technical transmission and the explanation given to users should refer to the same reality. A shared register of purpose, fields, destinations, retention and responsibility reduces gaps between teams.
Test implementation, not just the banner
Test what loads before and after each choice, what happens on withdrawal and whether changes reach downstream destinations. Compliance depends on the behaviour of the whole data chain, rather than the appearance of a popup.
This consent-aware measurement framework is an original editorial methodology developed by DigitalNow and does not replace specialist legal advice.