PostHog identify email capture
Last updated 2026-06-14
Definition
PostHog identify email capture grabs the email a user passes when PostHog identifies them, then hands it to Quri’s identity spine. That email is the key that binds their earlier anonymous PostHog events to a known person, so a stream of anonymous activity finally becomes one named customer in Atlas.
How to do this in Quri
- Pass an email property in your PostHog identify call when a user signs in or signs up.
- Connect PostHog to Quri in your Atlas source settings.
- Quri reads the identify email and binds it to the identity spine.
- Open /app/atlas/users to confirm anonymous PostHog events now sit under a named person.
Frequently asked
- Why does Quri need the email from identify?
- The email is the shared key that ties PostHog activity to the same person seen in other tools. Without it, anonymous PostHog events stay a separate, nameless stream that cannot join the journey.
- What if my identify call has no email?
- Then those events bind only by PostHog’s own ID and may not link across sources. Passing an email on identify is what unlocks cross-source stitching for that person.