A canonical email address is the single normalized form of an address that a system uses to compare, dedupe and match contacts, while the original value is kept for display and audit.
Two strings can point to one mailbox. Canonicalization maps them to one key so your list counts the person once.
Why it matters for outbound
Duplicates cost you twice. The same prospect gets two sequences, or a person on your suppression list slips back in because the address was spelled differently.
The risk runs the other way too. Normalize too hard and you merge two real people into one row, then suppress the wrong one.
Safe steps are narrow. Trim whitespace and lowercase the domain, because domains are not case sensitive (RFC 5321, September 2026). Treat the local part (the text before the @) with care. RFC 5321 says it must be treated as case sensitive, though most providers ignore case in practice.
Provider rules are not universal. Gmail ignores dots in personal addresses, but a Google Workspace address on a company domain does not (Gmail Help, September 2026). Strip dots only for domains where you know the rule.
Example
Three inputs from three imports, all placeholders:
Jane.Doe@ACME.com
jane.doe@acme.com
jane.doe+event@acme.comSafe canonicalization trims the space and lowercases the domain. The first two now match as Jane.Doe@acme.com and jane.doe@acme.com, and a case-insensitive key on the local part also merges them.
The plus-tagged third address is a judgment call. Many providers deliver +event to the same inbox, but acme.com may treat it as a separate mailbox. Keep it as its own row until you have checked that domain.
Store the key in a separate column and never overwrite the original.
In LeadOcean data
LeadOcean has no canonical email field. Each address carries a deliverability status (verified, catch_all_valid, catch_all, risky, unknown and others), shown as email_status on search rows (openapi.json, September 2026). That is a verification result, not a normalization.
In exports, addresses arrive as email_1_address, email_1_status, email_2_address and so on (POST /v1/exports, September 2026). Build your dedupe key from those columns on your side. Match on the lowercased address, and apply provider rules only where you have confirmed them.
Check email_status before you send. LeadOcean does not refund bounced emails. See /pricing for the Free and Pro plans.
More definitions sit in the glossary hub.
Related terms
Start with a list you can dedupe and verify
Free to start. No credit card. 1,000 records to spend whenever you like.
Get your free API key →