// automation and data tools
Via APIPostHog email verification with pingutil
PostHog funnels and retention charts count every signup, including temp-mail accounts and machine-generated addresses, which makes activation look worse and experiments noisier. Classify each new user with pingutil on the server and set the result as person properties, so you can filter fake signups and split company from personal users in any insight.
Where it connects: posthog-node capture with $set person properties, sent from your signup handler or a backfill job
What goes wrong without it
- Our signup-to-activation funnel is dragged down by throwaway accounts that never come back.
- We cannot tell how many of last week's signups were real work emails.
- Experiment results are noisy because bot and trial-abuse accounts land in both variants.
What you can do with PostHog and pingutil
Filter fake signups out of funnels
Set email_is_spam as a person property at signup and add "email_is_spam is not true" to funnel and retention insights.
Break down activation by email type
Use email_category (company, free, disposable, educational) as a breakdown to compare how work-email users activate against webmail users.
Cohorts for B2B follow-up
Create a cohort of users with email_category = company and sync it to your CRM or sales tooling from PostHog.
Set it up
- 1
Install posthog-node in the service that handles signups and initialize it with your project token and host.
- 2
After creating the user, call pingutil /v1/lookup with skip_enrichment: true and a short timeout.
- 3
Capture an event for the user with $set properties email_category, email_is_spam and email_reason, as in the snippet.
- 4
Make sure the distinctId matches the ID your frontend passes to posthog.identify().
- 5
For existing users, run the same function in a one-off backfill, paced under 60 requests a minute.
import { PostHog } from 'posthog-node';
const posthog = new PostHog(process.env.POSTHOG_TOKEN!, { host: 'https://us.i.posthog.com' });
export async function tagSignup(userId: string, email: string): Promise<void> {
let props: Record<string, unknown> = { email_category: 'unchecked' };
try {
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: email, skip_enrichment: true }),
signal: AbortSignal.timeout(3000),
});
if (res.ok) {
const data = await res.json();
props = {
email_category: data.category,
email_is_spam: data.verdict.is_spam,
email_low_trust: data.verdict.low_trust,
email_reason: data.verdict.reason,
};
}
} catch {
// timeout or network error: keep 'unchecked', never block the signup
}
posthog.capture({
distinctId: userId,
event: 'email_classified',
properties: { $set: props },
});
}What to do with each result
| pingutil result | Action in PostHog |
|---|---|
| category | Person property email_category, used as a breakdown |
| verdict.is_spam = true | Person property email_is_spam; exclude it in funnels and experiments |
| verdict.low_trust = true | Person property email_low_trust for info@ and noreply@ style signups |
| Error or timeout | email_category = unchecked; re-run in the backfill job |
Limits to plan for
- PostHog transformations cannot make external HTTP calls, so classification happens in your backend before the event is sent.
- pingutil allows 60 requests a minute and 2,000 lookups a day (30,000 a month) per account; pace backfills accordingly. Those are Free plan limits; Enterprise has custom limits.
- In serverless functions, flush or shut down the PostHog client before returning, or the event may not be sent.
PostHog documentation
PostHog is a trademark of its owner. This integration uses PostHog's documented extension points; it is not an official PostHog app.
Common questions
- Why not do this in a PostHog transformation?
- PostHog's docs say transformations run during ingestion and cannot make external HTTP calls. Setting the properties from your backend avoids that limit.
- Should I store the full company profile in PostHog?
- Only if you use it. A full lookup adds company.name and company.industry, which are useful as group or person properties for B2B analysis.
Stop bad addresses in PostHog today
Sign in with your email, create an API key and paste it into the step above. Test on a few real addresses first: the live demo shows exactly what your PostHog setup will receive.