Email Service tracking

Owned product, API, and UX design work for Cloudflare Email Service tracking features, including a mockup for enabling click and open tracking.

Problem

Email Service customers needed clearer visibility into what happened after an email was sent. Tracking raised product and developer experience questions around how to expose useful event data without making setup or integration feel heavy.

My role

I owned early product scoping for tracking improvements, connecting customer pain points, usage signals, and technical constraints into a clearer product direction.

What I produced

• A tracking requirements brief that defined the customer problem, expected user value, and first version success criteria
• API design recommendations for how tracking data should be exposed to developers, including key events, objects, and response patterns customers would need
• A UX mockup for enabling click and open tracking, focused on making the setup path clear without adding unnecessary configuration
• A breakdown of tracking events customers would need to understand delivery and engagement, including where those events should appear in the product experience
• Developer experience notes for setup, configuration, and debugging flows, focused on reducing unclear next steps
• Engineering-ready tasks that translated broad tracking needs into scoped implementation work
• Customer pain point synthesis from usage patterns, customer conversations, and competitive expectations around email observability

Key decisions / tradeoffs

I focused the work on practical customer adoption: enough visibility to make the feature useful, without overcomplicating the first version or exposing unnecessary implementation detail.

Outcome

The work helped turn a broad tracking need into a more actionable set of product improvements for Email Service.

What I learned

Small developer experience details can decide whether a useful infrastructure feature feels adoptable or frustrating.