Email Tracking Privacy Starts With Your ESP

Email service providers offer extensive tracking. It helps marketers measure campaign performance, but privacy laws limit what you can collect and how long you can keep it. The harder problem is that most ESPs don't give you the controls you would need to honor those limits for the individual subscriber who asks.

Each tracking metric carries a different privacy cost

Most programs lean on three metrics. Open tracking tries to measure views with a tracking pixel. Modern mail clients either block those pixels or load them without the recipient doing anything, which makes open data increasingly unreliable for decisions.

Click tracking is a stronger signal. It routes the subscriber through a redirect before they reach your content, and that redirect is a data collection point with its own questions about scope and retention.

Conversion tracking connects email engagement to what happens on your website. It's valuable for measuring return, but following an individual across systems deserves extra scrutiny. You have to document both the business reason and the safeguards.

An assessment shows you what you're collecting and why

Start with a Data Protection Impact Assessment (DPIA). Even where the law in your jurisdiction doesn't explicitly require one, the process forces you to catalog what you collect and justify it.

Your list holds the basics you need to send mail: names, email addresses, and preferences. Many programs also hold demographic data that serves no clear purpose. If you never segment by ZIP code, storing ZIP codes is risky with no return.

Engagement data (opens and clicks) is necessary for measuring effectiveness, but keeping it forever almost certainly exceeds any legitimate need. Set retention limits that match your reporting cycles.

Post-click website data serves ROI reporting. Tracking individuals across systems to get it adds privacy exposure, and in many cases aggregate data would answer the same question with less risk.

Most ESPs can't honor a single subscriber's tracking choice

In my experience, the best an ESP usually offers is three levels of tracking control. Account settings set your platform-wide defaults. Domain settings let you configure tracking per sending domain. Send settings let you turn tracking off for one job.

That is the whole menu. There are no list-level controls, no subscriber-level settings, and no rules that follow a subscriber's consent. When a subscriber asks for minimal tracking, you can't flip a switch for that person. You have to route their mail through a workaround, usually a dedicated segment tied to a job or set of jobs with tracking turned off.

Handling it at the domain level creates its own problems. Each sending domain needs its own suppression maintenance, and an unsubscribe on one domain may not automatically carry over to the others.¹ Every domain needs its own SPF, DKIM, and DMARC setup. Reporting gets messy when you have to stitch data together across domains by hand.

Document what you decided, because someone will ask

Do the DPIA first. You need to know exactly what you collect, why, and what difference it makes. Many marketing teams find they collect far more than they ever use.

Then learn exactly what your ESP can and can't control, because the answer varies a lot between platforms, and stakeholders need realistic expectations.

Write down your tracking configuration, your retention rules, and your reporting process. When a regulator, an auditor, or your ESP's compliance team asks, you will want a record of what you decided and why. Revisit it on a schedule, since platforms, regulations, and your own needs all change.

Perfect measurement was never available anyway. The goal is enough reliable data to make good decisions, collected in a way you can defend, and sometimes that means accepting you won't measure everything.