-
Notifications
You must be signed in to change notification settings - Fork 377
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Person data batch export FAQ #8489
Conversation
The latest updates on your projects. Learn more about Vercel for Git ↗︎
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
👍
Co-authored-by: Ian Vanagas <34755028+ivanagas@users.noreply.github.com>
- [person data export](https://github.com/PostHog/posthog/issues/20339). | ||
- Export person properties on events (`event.person_properties`) with [custom schemas](https://github.com/PostHog/posthog/issues/20367). | ||
|
||
Note: Our implementation of person ids on events (`event.person_id`) is eventually consistent, which for batch export destinations means joining event `distinct_id` with the person data export. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I would omit this note. It's not wrong it's just that we don't have a person data export (as stated above). Eventually, once we develop the person model export this will be the way to go. As it stands, this note seems confusing.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I need this section to answer why we're not exporting person_id
as that's the user question
https://posthog.com/questions/person-id-in-batch-export
Changes
Please describe.
Add screenshots or screen recordings for visual / UI-focused changes.
Checklist
vercel.json
Article checklist
Useful resources