Event mapping
Each imported Luma event becomes an Event in Path. Badge events use the same model.
Every guest Path discovers through this Luma event is linked to that event. Add those people to a channel to see the event in the Attribution model.
Guest mapping
Every Luma guest becomes a Person. If a person already exists with the same email, TalkValue updates that record instead of creating a duplicate.
The required Luma fields (name + email) always land in the matching TalkValue fields; optional fields are imported when present.
Re-import behavior
You can re-import the same Luma event. Path updates existing people in place by email, adds new guests, and refreshes event metadata. TalkValue never deletes people; it merges and updates them.What is not imported
- Waitlist entries that never got approved. Only confirmed guests are pulled in.
- Luma payment information. TalkValue does not store Luma order IDs, ticket types, prices, or transaction history.
- Marketing settings from Luma (opt-in flags, email subscription state). Manage those separately in your email tool.
Related
- Luma integration. Connection model, status states, reconnect, disconnect.
- Import a CSV. Manual import path with explicit column mapping.
- Column mapping. The CSV-side counterpart for picking which columns map to which fields.
- People, companies, channels, events. The Path entity model the import lands in.