Separate three decisions
Treat sending, accessing information on a device and building a personal engagement record as three connected but distinct activities. PECR's electronic-mail marketing rules govern the message. Where a pixel stores information on, or obtains information from, a recipient's device, the storage-and-access rules in regulation 6 also matter. The UK GDPR applies where the resulting information identifies a person.
This distinction is practical. A newsletter signup may explain the content and frequency while saying nothing about recording which articles a named subscriber reads. A sentence buried in a privacy notice is not, by itself, a valid consent mechanism where consent is required. Equally, do not assume every form of aggregate measurement requires the same treatment as an individual profile.
Understand the implementation before deciding
Ask the supplier how an open is detected, what identifier is included, what information is returned and how long the raw events remain. Find out whether the feature can be disabled for the whole account, an individual campaign or particular recipients. Request a test message and check its HTML rather than relying solely on the dashboard label.
Click measurement needs its own examination. A plain link, a server-side redirect and a link that passes identifiers or causes additional device access are not interchangeable. It would be misleading to say every redirect automatically needs device-access consent. Establish the mechanics first, then assess the applicable rules and the purpose for retaining any identifiable click history.
Choose measurement that supports a decision
Our practical recommendation is to start with the decisions the business genuinely needs to make. If the question is whether an article attracts readers, aggregate website visits from a campaign may be sufficient. If the question is whether a particular customer opened three emails, the business is making a more intrusive choice and should be able to explain why.
Record the proposed metric, the business decision it informs and whether a less identifying alternative works. Do not retain detailed recipient histories simply because the platform offers them. Consider a small measurement register alongside the mailing-list register, identifying the feature owner, settings, notices, retention and any consent requirement.
Make the choice understandable and workable
If consent is the appropriate requirement, explain the tracking purpose distinctly and provide a genuine choice. The operational design matters as much as the wording: a recipient who declines should not silently receive the same tracking anyway. Test the actual campaign output for both choices, including messages generated by automations.
Where a claimed exception or another lawful basis is proposed, document its conditions rather than assuming that the absence of cookies resolves the issue. Personal engagement records still need a lawful basis, appropriate transparency, security and retention. A vendor's general compliance statement does not establish that the customer's configuration meets these requirements.
A useful question for the supplier
Ask whether disabling reporting also disables collection. A dashboard may hide a metric while the underlying events are still recorded. Request a precise explanation of what stops, what remains and whether historical records are retained. Keep that answer with the configuration evidence so the next person managing campaigns does not unknowingly reverse the decision.
Avoid treating an open as a fact about the person
For operational reporting, distinguish a recorded technical event from a reliable statement that a human read an email. Before using engagement scores to suppress contacts, trigger sales calls or label someone uninterested, ask the provider how its measurement handles automated requests and privacy features. The answer may affect both the usefulness and fairness of the metric.
A sensible audit therefore ends with a short configuration record, not just a revised notice. Keep the supplier's explanation, the tested settings, a sample of the resulting message and the decision on what the business will collect. Review it when templates, providers or automation features change. Privacy-conscious measurement should be designed into the communication process, not appended afterwards.
Sources and further reading
Primary guidance behind this briefing. Requirements depend on the facts; check the current guidance before making a decision.
This is general guidance, not a legal opinion on your circumstances or a guarantee of compliance. An individual assessment may be needed, particularly where sensitive information, disputed rights or regulatory action is involved.