Use Case: B2B Lead Scoring
Screening lead-capture forms and CRM imports, where a role-based or free-provider address means something different than it does for a consumer signup.
Recommended configuration
| Setting | Recommendation |
|---|---|
| context | "b2b_lead" for a live lead-capture form; "crm" for bulk contact import — both weight role-based and free-provider addresses higher than generic, b2b_lead more strongly |
| mode | "standard" for live forms; bulk endpoint with any mode for CRM import batches |
| Pattern | Blocking is usually fine here — lead forms aren't as latency-sensitive as high-traffic consumer signup |
What to look at beyond the score
- domain.type — business vs. consumer vs. disposable
- domain.infrastructure — known business mail infrastructure vs. self-hosted/unknown
- local_part_analysis.name_like — whether the local part reads as an actual person's name
Further reading
- How to Detect Fake Leads Using Email Data — the full worked example of how context changes scoring for the same address
- Email Risk Scoring Explained — the underlying context-multiplier mechanics