Luma field mapping

When you import a Luma event, TalkValue pulls in two layers: the event itself and every registered guest. Here’s how each field maps.

Event mapping

Each imported Luma event becomes an Event in Path. Badge events use the same model.

Luma field	TalkValue field	Notes
Event name	`event.name`	Visible in the Events list, attribution charts, and audience filters.
Start date and time	`event.startAt`	Stored with timezone for accurate time-zone-aware charts.
End date and time	`event.endAt`	Optional in Luma, optional in TalkValue.
Timezone	`event.timeZone`	Used to display the event’s date range in the event’s own time zone.
Location	`event.location`	Free-text venue or online indicator (Luma Zoom integrations show as the meeting URL).

Path also creates a channel for the Luma source on the first import. Every guest Path discovers through Luma is attributed to that channel, so the Attribution model works without extra setup.

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.

Luma field	TalkValue field	Notes
Email	`person.email`	The primary identity key. People are deduplicated by email.
First name	`person.firstName`	Parsed from the Luma name field when first/last aren’t separate.
Last name	`person.lastName`	Optional.
Company	`person.company` (also rolls up via email domain)	Path also auto-groups people by email domain into a Company record.
Job title	`person.jobTitle`	Optional.
Phone	`person.phone`	Optional.
LinkedIn / social URLs	`person.socials`	Optional. Stored on the person record when Luma collects them.
Custom questions	Stored on the registration record	Path keeps the original answer attached to the registration for the event.

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.

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.

Core concepts

Integrations

Event mapping

Guest mapping

Re-import behavior

What is not imported

​Event mapping

​Guest mapping

​Re-import behavior

​What is not imported

​Related

Event mapping

Guest mapping

Re-import behavior

What is not imported

Related