// use case · Product managers, data analysts and growth engineers who report on signups, activation and conversion.
Keep fake signups and test accounts out of your product metrics
Look up each new user once and store category and verdict.is_spam as user properties in your analytics tool. Then filter spam out of activation and conversion reports and break results down by company versus webmail. For B2B products, company.industry and employee_size_estimate give you firmographic segments without asking users.
The problem
- Our activation rate dropped and it turned out to be a bot wave.
- We cannot tell whether work-email users convert better than Gmail users.
- Internal test accounts and throwaway signups inflate our top-of-funnel numbers.
- Sales asks which industries use the product and we have no answer.
How pingutil solves it
- 1
Enrich once per user
Call /v1/lookup when the user signs up, from your backend or a queue worker, not on every event.
- 2
Store as user properties
Send category, verdict.is_spam and, for company users, company.industry and company.employee_size_estimate to your analytics tool.
- 3
Filter and segment
Exclude is_spam users from funnel reports and add category as a breakdown in activation and retention charts.
Fields you will use
| Response field | What to do with it |
|---|---|
| verdict.is_spam | Exclude from funnel and activation reports |
| category | Break down metrics by work, webmail, student or ISP |
| company.industry | Segment B2B usage by industry |
| company.employee_size_estimate | Segment by company size |
| domain | Group users from the same company |
const res = await fetch('https://pingutil.com/v1/lookup', {
method: 'POST',
headers: {
Authorization: `Bearer ${process.env.PINGUTIL_KEY}`,
'Content-Type': 'application/json',
},
body: JSON.stringify({ input: user.email }),
}).then((r) => r.json());
analytics.identify(user.id, {
email_category: res.category,
is_spam: res.verdict.is_spam,
company_domain: res.category === 'company' ? res.domain : null,
industry: res.company?.industry ?? null,
company_size: res.company?.employee_size_estimate ?? null,
});Compared with the alternatives
Some analytics tools offer reverse-IP or company enrichment add-ons, and data teams often build an email-domain classifier in SQL with a webmail list. The SQL approach misses disposable and random addresses unless someone maintains the lists. pingutil keeps those lists current and adds the company profile from the same call.
See provider comparisons →Limits to plan for
- Enrichment happens per user at signup. There is no bulk lookup endpoint, so backfilling historical users means a throttled script.
- Spam signals catch disposable and gibberish addresses, not bots using real webmail accounts.
- Company fields are LLM-derived estimates; aggregate them for trends rather than trusting a single record.
Common questions
- Should I delete spam users from my analytics?
- Tag them instead. Keeping them with is_spam set lets you measure the abuse itself and filter it from everything else.
- Can I call it from the browser analytics snippet?
- No. Your API key must stay server-side. Call it from the backend at signup and send the result as user properties.
- How do I see multiple users from the same company?
- Group by the domain field. It is the registrable domain, so mail.acme.com and acme.com land in the same group.
Read next
- Guide: Enrich new signups with company data for onboarding and sales
Turn a signup email into a company profile (industry, size, HQ, funding) to personalize onboarding and alert sales, and know when not to trust the result.
- Guide: How to stop fake and throwaway signups in your SaaS app
Screen every signup email with one API call: block disposable domains and gibberish addresses, flag role accounts, and keep real users moving without friction.
- Keeping fake and internal signups out of product analytics
Tag every signup as real, suspect, fake or internal when the account is created, then filter on that tag in PostHog, Mixpanel, Amplitude or plain SQL.
- Personalizing onboarding from the signup email domain
Branch onboarding on the signup email domain: team setup for company addresses, a solo flow for Gmail, an education plan for .edu. Code, UX copy and privacy rules.
- Spotting multiple signups from the same company
Detect teammates who sign up separately: group signups by registrable domain, skip webmail and schools, then send a team invite or a sales alert.