What is the Core Email File?

A verified email-address universe with identity linkage: 314M single-match (one email per person) and 585M multi-match (multiple verified emails per person) records. Built from licensed sources, deliverability-tested, and refreshed monthly.

What's deliverability look like?

Single-match records target 90%+ deliverability for verified-tier emails, with bounce-tested validation in the prior refresh window. Match-rate against any given input file depends on the input, sample testing is part of standard onboarding.

What attributes attach to each email record?

Identity-graph linkage (HEM is the primary key, with MAID, IP, postal, household ID where available), demographic attributes (age, income, household composition), and selected behavioral overlays. Full attribute lists are scoped per use case.

What use cases is this for?

Cold-prospect email outreach (where permitted under CAN-SPAM and state law), CRM enrichment and reactivation, suppression-file maintenance, identity-resolution onboarding, and audience-onboarding for hashed-email activation across ad platforms.

Is the file CCPA / CPRA compliant?

Yes. Email data is processed under documented legal bases; consumer sale or sharing opt-out and do-not-sell requests are honored as soon as feasible and within 15 business days. State-by-state delivery restrictions (where applicable) are applied at file generation.

Core Email File, 314M Single / 585M Multi-Match

Since 2018

Privacy-safe enterprise data

VOSB & SDVOSB

U.S. Veteran-Owned, Service-Disabled

SCC Transfers

EU/UK/CH per privacy policy

GDPR · CCPA · CPRA

Consent-first data sourcing

Overview

A verified identity file offered in two shapes: 314M single-match records (one verified email per person) and 585M multi-match records (multiple verified emails per person). Each record links individual names, postal addresses, and verified email addresses for CRM enrichment, audience matching, direct mail-to-digital bridging, and identity resolution at scale.

Want the buying guide?

If you’re evaluating vendors or writing an RFP, this guide lays out what to ask for (coverage, refresh, governance) and links to the best references.

Identity resolution buying guide

Need an API key + JSON sample?

For technical evaluation, we can provide a sample payload, schema notes, and delivery options (S3/SFTP/Snowflake) aligned to your workflow.

Request API key + JSON sample Developer hub

Data Types

Full name
Postal address
Email address
Phone (where available)

Delivery Formats

CSVTXTXLS

Key Features

314M single-match
585M multi-match
Deterministic matching
Monthly refresh

Sample fields

A representative slice of the Core Email File schema. The data dictionary shared during evaluation lists every field with its type, nullability, join keys, and refresh cadence.

Field	What it contains
person_id	Stable internal identifier for the identity record.
full_name	Normalized full name associated with the record.
postal_address	Current normalized postal address when available.
email	Verified email address associated with the person.
phone	Phone number appended when available.
verification_date	Most recent verification or hygiene-processing date.

How the Core Email File Is Built

GSDSI's Core Email File is built through deterministic matching of consumer identity data points collected from public records, permissioned opt-in sources, and commercial data partnerships. The single-match universe contains 314M records with one verified email per person; the multi-match universe contains 585M records where multiple verified emails per person are retained when available. Each record links an individual's full name to their current postal address and verified email address(es), with phone numbers appended where available. Both shapes go through monthly hygiene processing that includes NCOA (National Change of Address) updates, email deliverability validation, and deceased record suppression, keeping the file accurate and deliverable for digital audience matching and direct mail campaigns that require current, verified consumer contact information.

Common Applications for Identity Data

CRM enrichment is the most common use case. Brands upload their customer files and match against the Core Email File to append missing email addresses, update outdated postal addresses, and fill gaps in their first-party data. Digital audience platforms use the file for offline-to-online identity resolution, matching postal-based customer lists to digital identifiers for programmatic activation. Direct mail marketers bridge physical and digital channels by matching email engagement data against postal records to create coordinated multichannel campaigns. Identity verification providers use the deterministic name-address-email linkage as a reference dataset for fraud detection, verifying that applicant-provided information is consistent with known consumer records in the single-match or multi-match universe as appropriate to the use case.

Vendor comparisons

Use these buyer guides to compare this feed category with adjacent vendor offerings.

How buyers diligence email and identity files

Email-file buyers should separate append use cases from outbound use cases. Procurement should review verification recency, single-match vs. multi-match shape, suppression handling, and sender-compliance constraints.

Test single-match and multi-match append rates separately against a known seed file.
Review verification recency, bounce-risk controls, and suppression-list handling.
Confirm CAN-SPAM, state privacy, and opt-out obligations for any activation workflow.
Define whether the file is used for identity resolution, enrichment, direct outreach, or suppression.

Request a Quote Sourcing methodology Request a matched sample

Core Email File