Data Normalization

Your ESPs finally speak the same language

SendGrid calls it "delivered." Mailgun calls it "accepted." PowerMTA calls it "success." Without normalization, comparing them is a nightmare. Engagor translates everything into one consistent format — so you can stop wrestling with data and start making decisions.

One format. Every provider. Finally comparable.

Before: Chaos
SendGrid"event": "delivered"
Mailgun"event": "accepted"
PowerMTA"status": "success"
SparkPost"type": "delivery"
X Can't compare. Can't aggregate. Can't analyze.
After: Clarity
Delivered4 providers
Bounced4 providers
Opened4 providers
Clicked4 providers
Compare anything. Analyze everything.
The Problem

Every ESP invents its own language

You'd think "email delivered" would be a universal concept. It's not. Each provider has its own terminology, formats, and quirks.

Event names differ

One ESP says "delivered," another says "accepted," another says "success." Same thing, three different names.

Timestamps vary

Unix timestamps, ISO strings, custom formats, different timezones. Good luck lining them up.

Bounce reasons are inconsistent

Each ESP categorizes bounces differently. Comparing bounce rates across providers? Nearly impossible.

Metrics don't match

Open rates, click rates, engagement scores — every provider calculates them slightly differently.

The result?

You can't get a single view of your email program. You can't compare ESPs fairly. You can't ask "how are we doing?" without manually stitching together data from multiple sources.

What We Normalize

Everything that needs to be comparable

Engagor automatically translates and standardizes these elements from every connected ESP.

Event Types

Delivered, bounced, opened, clicked, unsubscribed, complained — consistent naming across all providers.

"accepted" / "success" / "delivered" Delivered

Timestamps

All timestamps converted to a single timezone and format. No more manual conversions.

1703184000 / "Sat, 21 Dec..." 2024-12-21 16:00 UTC

Bounce Categories

Hundreds of SMTP codes and provider-specific reasons mapped to clear, actionable categories.

"550 5.1.1" / "user unknown" Invalid Recipient

ISP Identification

gmail.com, googlemail.com, and dozens of variants all recognized as "Gmail."

hotmail.com / outlook.com / live.com Microsoft

Engagement Metrics

Open rates, click rates, and engagement scores calculated consistently, regardless of source.

Different calculation methods Standardized formulas

Provider Attribution

Every event tagged with its source ESP, so you always know where data came from.

Mixed, unlabeled data Clear provider tags
What This Enables

The questions you can finally answer

"Which ESP delivers better to Gmail?"

Compare SendGrid vs. Mailgun vs. PowerMTA delivery rates to any ISP — in one chart, with consistent methodology.

"What's our overall delivery rate?"

Get a single number across your entire email program, not separate stats from each provider.

"Why did bounces spike last Tuesday?"

AI can analyze all your ESPs at once and find the pattern — impossible when data isn't normalized.

"Should we switch ESPs?"

Make apples-to-apples comparisons before and after migration. No more "the numbers look different because..."

Real Scenarios

How teams use normalized data

One dashboard for everything

Marketing sees all email performance in one place — no logging into three different ESP dashboards.

AI that actually works

Ask natural questions like "what's causing our Gmail issues?" and get answers across all providers.

ESP migration confidence

When you switch from SendGrid to Mailgun, your historical data stays comparable.

Anomaly detection that sees everything

Alerts based on your total program, not siloed per-ESP thresholds.

Cross-ESP Comparison
SendGrid
98.4%
Mailgun
97.8%
PowerMTA
98.1%
Get Started

Ready for one source of truth?

See how normalized data transforms your email analytics.