Person data in batch exports

[tiina303]

Why: Its currently only possible to have event data but person data is needed for full analysis downstream

Plan (TDB):

• [ ] Implement person and distinct ID table export
• [ ] Document how joins should be done for each batch export destination type

Q2 planning doc: https://docs.google.com/document/d/14vgMXToisseDFqAL-OaMXN1RfWSvh7w43Q8x6oheTaw/edit#heading=h.9sj0f6tabnjq

Open questions: Should events batch export to allow exporting person properties on events?

• Will be allowed by exposing a HogQL interface to define a schema.
• Notably, we don't allow exporting personIDs as internally it's not a simple fixed column unlike person properties.
• A more accurate personID to distinctID export will be provided to fill this gap.
• Progress:

  • 20075

  • 20060

  • 20095

  • 20177

  • 20181

[ConnorDoyle]

+1, this is needed. Does this feature include exporting cohorts?

[tiina303]

Does this feature include exporting cohorts?

This wasn't part of the plan ... yet ... could you elaborate on your use case?

[kotte34723]

This is an extremely basic expectation for any company using analytics. Please get this shipped.

[CamRounds]

It would be very helpful to have an export of all persons and their feature flag values!

[CamRounds]

My use case is to be able to run a drip campaign for persons in a specific feature flag group so having a list of all persons and their feature flag values would be helpful.

Using batch export today doesn't provide enough data for my use case because only events are exported, this leaves a gap with the persons that have not interacted with our website in some time, who will not have any event data.