CRMEnrichment

Gender Enrichment

Add a probabilistic gender field to lead and customer profiles when users have not provided one.

Start with 500 free creditsDocumentation

Email gender · 1 credit per lookup · no monthly fee

jane.doe@acme.com
+ Gender fieldFemale · 98%

The problem

Your CRM has millions of email addresses and almost no demographic context. Sales and marketing want to understand who is actually in the database, but asking every contact to self-report gender is intrusive, low-response, and often skipped entirely, so the field sits empty and every segment built on it is guesswork.

With Encrata

Call the gender endpoint with the email address and Encrata returns a likely gender, a likely country, and a probability score, all inferred from the name and address, so no one has to fill in a form. Store the verdict as a probabilistic field, keep a neutral fallback for low-confidence results, and you get demographic texture across the whole database without a single survey.

How it works

1

Send the address

Call the gender endpoint with just an email address; the name in the local part is enough to work from.

2

We infer the verdict

Encrata reads the name embedded in the address and returns a likely gender and country with a confidence score.

3

Use it with care

Segment, personalise or enrich on the verdict, always keeping neutral fallbacks and letting people override. One credit per lookup.

One call, structured answer

Gender Enrichment runs on the email gender lookup at 1 credit per lookup. Same API key, same JSON shape as every other Encrata lookup.

  • A single male / female / unknown verdict with a 0-100 confidence score
  • Country signal included, so ambiguous names resolve by region
  • 1 credit per lookup, with free repeats for six months
  • unknown is returned honestly when a name is ambiguous, never a guess
Terminal
curl -X POST "https://app.encrata.com/api/email/gender" \
  -H "Authorization: Bearer YOUR_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{"email": "jane.doe@example.com"}'
response.json
{
  "email": "jane.doe@example.com",
  "gender": "female",
  "country": "US",
  "probability": 98,
  "credits": 1
}

Enrich without asking a soul

Wire the gender endpoint into the same enrichment step you already run on new contacts: one call returns the inferred gender, the likely country, and a probability score, which you write into dedicated fields rather than overwriting anything a person supplied. Gate on confidence, store high-probability verdicts as-is, and mark low-probability ones as uncertain so no segment mistakes a coin-flip for a fact.

Demographic texture, database-wide

The payoff is demographic context across the whole database without ever running a survey or adding a form field. Keep it honest by treating the field as probabilistic everywhere it is used, and always let a self-reported value take precedence, the inference fills the gaps that self-identification left empty, it does not overrule the people who told you directly.

More email gender use cases

View all

Newsletter reach

58%
42%
Female 58%Male 42%

Audience Analytics

Understand campaign reach by inferred gender in aggregate across lists, subscribers, and event signups

MarketingAnalytics
Women's collection12,480
Men's collection9,020
2 segments built

Marketing Segmentation

Tailor content, product recommendations, or creative tests where gender relevance is legitimate

EcommerceMarketing

Respondents

Skew detected

72% one group · rebalance before you run

Research Sampling

Balance respondent groups or detect demographic skew before running interviews, polls, or user studies

ResearchSampling
Start with 500 free credits
$curl https://encrata.com/api/agent/lookup -H "Authorization: Bearer YOUR_API_KEY" -d '{"e": "satya@microsoft.com"}'