> ## Documentation Index
> Fetch the complete documentation index at: https://docs.trytalkvalue.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Eventbrite field mapping

> How Eventbrite event and attendee fields map into TalkValue entities when you import.

When you import an Eventbrite event, TalkValue pulls in two layers: the event itself and every registered attendee. Here's how each field maps.

## Event mapping

Each imported Eventbrite event becomes an [Event](/platform/concepts/data-model) in Path. Badge events use the same model.

| Eventbrite 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 Eventbrite, 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.                                  |

Path also creates a **channel** for the Eventbrite source on the first import. Every attendee Path discovers through Eventbrite is attributed to that channel, so the [Attribution model](/path/concepts/attribution-model) works without extra setup.

## Attendee mapping

Every Eventbrite attendee becomes a [Person](/platform/concepts/data-model). If a person already exists with the same email, TalkValue updates that record instead of creating a duplicate.

| Eventbrite field       | TalkValue field                                     | Notes                                                                                                |
| ---------------------- | --------------------------------------------------- | ---------------------------------------------------------------------------------------------------- |
| Email                  | `person.email`                                      | The primary identity key. People are deduplicated by email.                                          |
| First name             | `person.firstName`                                  | Optional.                                                                                            |
| Last name              | `person.lastName`                                   | Optional.                                                                                            |
| Company / Organization | `person.company` *(also rolls up via email domain)* | Path also auto-groups people by email domain into a [Company](/platform/concepts/data-model) record. |
| Job title              | `person.jobTitle`                                   | Optional.                                                                                            |
| Phone                  | `person.phone`                                      | Optional.                                                                                            |
| Cell phone             | `person.phone`                                      | Falls back to phone when set.                                                                        |
| Address                | `person.address`                                    | Optional. Imported as a single string.                                                               |
| Custom questions       | Stored on the registration record                   | Path keeps the original answer attached to the registration for the event.                           |

The required Eventbrite 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 Eventbrite event. Path updates existing people in place by email, adds new registrants, and refreshes event metadata. TalkValue never deletes people; it merges and updates them.

## What is not imported

* **Refunded or canceled registrations.** Only currently valid attendees are pulled in.
* **Eventbrite order or payment information.** TalkValue does not store Eventbrite order IDs, ticket types, prices, or transaction history.
* **Marketing settings** from Eventbrite (opt-in flags, email subscription state). Manage those separately in your email tool.

## Related

* [Eventbrite integration](/platform/integrations/eventbrite). Connection model, status states, reconnect, disconnect.
* [Import a CSV](/path/import/csv-quickstart). Manual import path with explicit column mapping.
* [Column mapping](/path/import/column-mapping). The CSV-side counterpart for picking which columns map to which fields.
* [People, companies, channels, events](/platform/concepts/data-model). The Path entity model the import lands in.