EnterpriseMarketing

Account Matching

Match individual users to their companies and map them against your target account list.

Email identity · 1,000 credits per lookup · no monthly fee

ana@vercel.com Vercel
raj@stripe.com Stripe
2 target accounts matched

The problem

Your ABM strategy names 200 target accounts, but signups arrive as personal work emails with no company field. Somewhere in this week's signups are three users from named accounts, and nobody knows.

With Encrata

Resolve each signup's email to a company and match it against your target-account list automatically. When someone from a named account touches your product, the account owner gets pinged the same hour, with the person's actual role attached, not just a domain guess.

How it works

1

Send the address

Call the identity endpoint with just an email address, no name, no company, nothing else required.

2

We resolve the person

Encrata matches the address against public profiles and returns name, role, company, location and social accounts.

3

Use the profile

Route, personalise, verify or investigate with a full picture of who is behind the address. Fields you ask for are the fields you get.

One call, structured answer

Account Matching runs on the email identity lookup at 1,000 credits per lookup. Same API key, same JSON shape as every other Encrata lookup.

  • A match on 99.86% of addresses, near-zero dead lookups
  • Every field is labelled found or not found, so you never guess what to trust
  • Ask only for the fields you need with the fields parameter
  • One API call replaces minutes of manual research per contact
Terminal
curl -X POST "https://encrata.com/api/agent/email-identity" \
-H "Authorization: Bearer YOUR_API_KEY" \
-H "Content-Type: application/json" \
-d '{"email": "jane@example.com"}'
response.json
{
"email": "jane@example.com",
"person": {
"first_name": "Jane",
"last_name": "Doe",
"company": "Acme Inc",
"job_role": "Head of Product",
"city": "San Francisco",
"socials": {
"linkedin": "linkedin.com/in/janedoe"
}
},
"credits": 1000
}

Match on domain and identity

Resolve each signup to a company, then match against your account list on domain plus resolved company name, the two together catch subsidiaries and personal-domain signups that domain matching alone misses. Pipe matches into the account owner's Slack with the person's role attached, so the alert is actionable without a CRM visit.

Footholds you already had

ABM teams usually discover their target accounts were already in the product: individual engineers and analysts who signed up quietly months ago. Surfacing those existing footholds changes outreach entirely, 'three people on your data team already use us' is a warmer opener than any cold sequence, and expansion conversations start from evidence.

More email identity use cases

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