> For the complete documentation index, see [llms.txt](https://help.peoplevine.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.peoplevine.com/products/control-panel-overview/reports-overview/data-dictionary-preview.md). # Peoplevine Data Dictionary This reference lists available fields per data table, their technical field names (as they appear in CSV exports), and plain-language descriptions. Fields are grouped by report type as they appear in **Build a Custom Report**. > Not all fields are available in a single report. For some analyses you may need to export two or more report types and combine the data. > **Import vs export:** field availability and naming can differ between importing and exporting. A field in the import spec may not appear in the export, or may use a different column name — when in doubt, export a sample file to confirm the actual export columns. ### Using the report builder 1. Navigate to [**REPORTS > Export Data to File**](https://control.peoplevine.com/export). > **Note (Pro Dash):** Navigate to your **Company dropdown > Export Data to File**. 2. The page has two sections: **Load an Existing Report** (to re-run a saved report) and **Build a Custom Report** (to start from scratch). 3. Under **Build a Custom Report**, select a **Data to Export** type from the dropdown and click **LOAD FIELDS**. 4. Toggle **Filter for Active Members Only** to limit results to active members. 5. Use **SHOW ALL FIELDS** to see every available field, or **Search** to find specific fields. No fields are toggled on by default — you select each field you want to include. 6. Underneath each field title, the source table is displayed — this helps identify which table a field comes from when the same field name appears across multiple tables. 7. For each field, set a **Match** condition and enter a **Filter** value to narrow results. The most common filter is a date filter for pulling a specific date range. 8. Select your file type options before generating the report: **File type options:** * **CSV - Comma Separated Value** — standard export with headers * **CSV - No Header Values** — export without column headers * **Return date/time in Universal format** — outputs dates as `2022-12-31 22:59Z` (UTC) 9. Click **GENERATE REPORT**. The report is sent to a queue — when it is ready for download, you will receive an email notification. ### Date filter variables Use these variables in the Filter field to create dynamic date ranges that update automatically each time you run the report: | Variable | Returns | | -------------------- | --------------------------------------- | | `{@thisMonthStart@}` | First day of this month | | `{@thisMonthEnd@}` | Current day (when the report is pulled) | | `{@lastMonthStart@}` | First day of last month | | `{@lastMonthEnd@}` | Last day of last month | Additional variables: `{@thisWeekStart@}`, `{@thisWeekEnd@}`, `{@nextWeekStart/End@}`, `{@thisMonthStart/End@}`, `{@lastMonthStart/End@}`, `{@lastYearStart/End@}`, `{@thisYearStart/End@}`, `{@todayStart/End@}`, `{@tomorrowStart/End@}`, `{@yesterdayStart/End@}`. **Match options:** No Filter, Match, Like, >=, >, <=, <, Not, Between (separate with -), Include/Match a few items (separate with a comma). ![Match dropdown options](/files/xHiQujlAUCsjVYUHPdjR) **Example — members with birthdays last month:** 1. Toggle on the **birthdate** field (Table: customer). 2. Set the **Match** dropdown to **Between (separate with -)**. 3. In the **Filter** field, enter: `{@lastMonthStart@}-{@lastMonthEnd@}` ![Birthdate filter with date variables](/files/HsyqKfY7gRb5KYK6j1z7) *** ## Customer CRM Data Fields available when importing or exporting CRM profile data. | Field Name | Technical Name | Description | Accepted Values / Format | | ------------------ | -------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -------------------------------------------------------------------------------- | | Email | `email` | Primary email address. Unique identifier. | Valid email | | CC Email | `cc_email` | CC email address used by email marketing campaigns when the CC email option is included. | Valid email | | First Name | `first_name` | Profile's first name. The CRM record may belong to a member, guest, or prospect. | Text | | Middle Name | `middle_name` | Profile's middle name. | Text | | Last Name | `last_name` | Profile's last name. | Text | | Gender | `gender` | Profile's gender. | `Prefer not to say`, `Male`, `Female`, `Non-binary`, `Other` | | Birthdate | `birthdate` | Date of birth. | Date | | Anniversary Date | `anniversary_date` | Wedding anniversary date. (For the membership anniversary, use `member_since` instead — date of initial enrollment in any membership program.) | Date | | Mobile Number | `mobile_number` | Primary mobile number. Unique identifier. | Phone number | | Phone Number | `phone_number` | Secondary phone number (landline, office, etc.). | Phone number | | Company Name | `company_name` | Profile's company or employer. | Text | | Company Title | `company_title` | Profile's job title or role. | Text | | Customer Type | `customer_type` | Category of the CRM record. | `customer`, `staff`, `company` | | Customer Reference | `customer_reference` | External reference ID from a previous system. | Text | | Address | `address` | Primary street address line 1. | Text | | Address 2 | `address2` | Primary street address line 2. | Text | | Address 3 | `address3` | Primary street address line 3. | Text | | City | `city` | Primary address city. | Text | | State | `state` | Primary address state/province. | Text | | Zip Code | `zip_code` | Primary address postal code. | Text | | Country | `country` | Primary address country. | Text | | Secondary Title | `address_type` | Label for the secondary address (e.g., "Summer Home", "Office"). Available on **import only** — secondary-address fields are not included in the data export (confirmed by Jordan). The `*1`-suffixed columns in the export (e.g. `email1`, `created_on1`) are the joined `user`-table duplicates of same-named `customer` fields, not secondary-address data. | Text | | Secondary Address | `secondary_address` | Secondary street address line 1. Available on **import only** — secondary-address fields are not included in the data export (confirmed by Jordan). The `*1`-suffixed columns in the export (e.g. `email1`, `created_on1`) are the joined `user`-table duplicates of same-named `customer` fields, not secondary-address data. | Text | | Secondary City | `secondary_city` | Secondary address city. Available on **import only** — secondary-address fields are not included in the data export (confirmed by Jordan). The `*1`-suffixed columns in the export (e.g. `email1`, `created_on1`) are the joined `user`-table duplicates of same-named `customer` fields, not secondary-address data. | Text | | Secondary State | `secondary_state` | Secondary address state/province. Available on **import only** — secondary-address fields are not included in the data export (confirmed by Jordan). The `*1`-suffixed columns in the export (e.g. `email1`, `created_on1`) are the joined `user`-table duplicates of same-named `customer` fields, not secondary-address data. | Text | | Secondary Zip Code | `secondary_zip_code` | Secondary address postal code. Available on **import only** — secondary-address fields are not included in the data export (confirmed by Jordan). The `*1`-suffixed columns in the export (e.g. `email1`, `created_on1`) are the joined `user`-table duplicates of same-named `customer` fields, not secondary-address data. | Text | | Secondary Country | `secondary_country` | Secondary address country. Available on **import only** — secondary-address fields are not included in the data export (confirmed by Jordan). The `*1`-suffixed columns in the export (e.g. `email1`, `created_on1`) are the joined `user`-table duplicates of same-named `customer` fields, not secondary-address data. | Text | | Opt In Email | `opt_in_email` | Whether the member has opted in to email marketing. | `Y` or `N` | | Opt In SMS | `opt_in_sms` | Whether the member has opted in to SMS marketing. | `Y` or `N` | | Opt In Updates | `opt_in_updates` | Whether the member has opted in to general updates. | `Y` or `N` | | Profile Photo | `profile_photo` | URL to the member's profile photo. | URL | | Facebook Handle | `facebook_handle` | Facebook profile handle. | Text | | Instagram Handle | `instagram_handle` | Instagram profile handle. | Text | | LinkedIn Handle | `linkedin_handle` | LinkedIn profile handle. | Text | | Twitter Handle | `twitter_handle` | Twitter/X profile handle. | Text | | Website | `website` | Personal or business website. | URL | | Username | `username` | Legacy portal login username. Usernames are no longer supported — the Member Portal uses the member's **email** as the login identifier, and the username field is being removed. Only present for legacy records. | Text | | Timezone | `timezone` | Member's timezone. | Windows timezone ID (141 options with UTC offsets available in company settings) | | Created On | `created_on` | Date the CRM record was created. | Date | | Modified On | `modified_on` | Date the CRM record was last modified. | Date | > **Opt-in fields are current-status flags only.** `opt_in_email`, `opt_in_sms`, and `opt_in_updates` report the member's **present** preference (`Y`/`N`) — they do **not** record *when* the member opted in or out. There is no opt-out timestamp in the export. To list members who are currently opted out, use the **My People** export and filter `opt_in_email = N` (and/or `opt_in_sms = N`); the row's `created_on` is the record-creation date, not the date of the opt-out. (`opt_in_email`/`opt_in_sms` come from the `customer assign` table; `opt_in_updates` from the `customer` table.) *** ## Membership Data Fields available when importing or exporting membership card data. | Field Name | Technical Name | Description | Accepted Values / Format | | ------------------------------ | ------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ------------------------------------------------- | | Email | `email` | Member's email — used to match to the CRM profile. Same field as the CRM profile email — editing here updates the CRM profile. | Valid email | | Customer No | `customer_no` | Peoplevine internal customer ID — alternative match field. Available across all data tables (CRM, Membership, Transactions). | Number | | Customer Reference | `customer_reference` | External reference ID — alternative match field from a previous system. | Text | | Mobile Number | `mobile_number` | Member's mobile — alternative match field. Same field as the CRM profile mobile number — editing here updates the CRM profile. | Phone number | | Membership ID | `membership_id` | The member's membership number displayed on their card. | Text | | Membership SKU | `membership_sku` | SKU of the membership program to enroll the member into. Set on the membership program's settings page; must match an existing program SKU. | Text | | Membership Status | `card_status` | Status of the membership card. | `active`, `inactive`, `pending` | | Expiration Date | `expiration_date` | When the membership card expires. Used for Membership ID (non-paid) programs. | Date | | Joined On | `created_on` | Date the member was enrolled in this specific membership program. May be referenced as `subscribed_on` in some contexts. If a member is enrolled in multiple programs, this date is per-program. The `member_since` data point reflects the date of initial enrollment into any membership. | Date | | Parent Membership Card | `parent_membership_card_no` | Card number of the primary member — links this member as a sub-member. Returns 0 if the customer record is the primary. | Number | | Membership Card Graphic | `membership_card_graphic` | URL to a custom card graphic. | URL | | Subscription Frequency | `subscription_frequency` | Billing frequency for paid memberships. | `monthly`, `quarterly`, `semi-annual`, `annually` | | Subscription Rate | `subscription_rate` | Recurring charge amount. | Decimal | | Subscription Details | `subscription_details` | Additional subscription notes. | Text | | Subscription Next Billing Date | `next_date` | When the next charge should process. | Date | | Subscription Last Billing Date | `last_date` | When the last charge was processed. | Date | | Field 1–6 | `field1_value` – `field6_value` | Custom fields displayed on the membership card (mapped to card field slots 1–6). | Text | *** ## Transaction Export Fields available in the CSV export from **SELL > View Transactions > EXPORT DATA**. | Field Name | Technical Name | Description | Example Values | | --------------------- | ----------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -------------------------------------------------------------------------------------- | | Transaction No | `transaction_no` | Unique transaction ID. | `18731123` | | Customer No | `customer_no` | Member/customer ID. | `2697771` | | Card No | `card_no` | Payment method ID in Peoplevine. Every payment method has a unique ID — a member with two Visa credit cards has two separate IDs. `0` = no payment method on file. | `717665` | | Linked Transaction No | `linked_transaction_no` | Related transaction — links a refund to its original charge, or an invoice payment to its invoice. | — | | Reference Type | `reference_type` | Type of entity charged. | `order`, `membership`, `invoices`, `application`, `service`, `transaction`, `giftcard` | | Reference No | `reference_no` | ID of the referenced entity (order\_no, card\_no, etc.). | — | | Reference Title | `reference_title` | Human-readable charge description — useful for identifying which membership program dues were charged or which specific event ticket was purchased. | "Gold Membership", "Order - pos", "invoices" | | Transaction Amount | `transaction_amount` | Total amount charged. **Use this field for Sales Reporting** — it is the sale amount. | `250.00` | | Refunded Amount | `refunded_amount` | Amount refunded (0 if none). | `0.00` | | Processed Amount | `processed_amount` | Net processed amount. If a partial refund was initiated on the original transaction, this updates to the remaining processed amount minus the refund. For Sales Reporting, use `transaction_amount` instead. | `250.00` | | Tax Amount | `tax_amount` | Tax portion of the charge. | `12.50` | | Discount Total | `discount_total` | Discount applied. | `0.00` | | Charged On | `charged_on` | Date and time the transaction was charged. **Use this field for Sales Reporting** — `charged_on` is the invoice date. The value is set once and does not change afterward; it can be back-dated at the moment a transaction is manually processed (an admin entering a charge for an earlier date), but it is not updated later. Distinct from the record creation date (`created_on`), which always reflects the day the record was generated in Peoplevine. | `2026-03-01 08:00` | | Paid On | `paid_on` | Date payment was collected. For invoices, this is the date the invoice was finally processed and paid. `1/1/1900` = unpaid. | `2026-03-01 08:01` | | Matched On | `matched_on` | Date matched to processor payout batch. `1/1/1900` = not matched. | `2026-03-03` | | Payment Type | `payment_type` | Payment method used. | `creditcard`, `invoice`, `cash`, `ach`, `giftcard` | | Card Type | `t_card_type` | Card brand or tender type. | `visa`, `mastercard`, `amex`, `ach`, `Invoice` | | Last 4 Digits | `t_card_four` | Last 4 digits of the card used. | `4242` | | Payment Processor No | `payment_processor_no` | Internal ID of the payment processor that handled the charge. | Number | | Transaction ID | `transaction_id` | Processor's unique ID for reconciliation. Received directly from Stripe (credit cards) and GoCardless (ACH) — not generated by Peoplevine. Only populated after the processor syncs the response back. | `pi_3T9ryF...` (Stripe), `PM_...` (GoCardless) | | Batch ID | `batch_id` | Payout batch ID. All transactions in the same bank deposit share this ID. Values start with `PO`. | `PO_...` | | Matched | `matched` | Whether transaction has been matched to a processor payout. | `Y` / `N` | | Transaction Status | `transaction_status` | Internal status code. | `processed`, `invoiced`, `refunded`, `declined`, `payment` | | First Name | `first_name` | Member's first name. | — | | Last Name | `last_name` | Member's last name. | — | | Was Invoice | `wasInvoice` | Whether this was originally invoiced before payment was collected. | `True` / `False` | *** ## My People Fields available in the **My People** export from Build a Custom Report. > Common CRM fields (name, address, contact details, opt-ins) are shared across all report types — see Customer CRM Data above. My People is a CRM-focused report. The majority of its fields are standard CRM person fields. The fields below are the non-standard engagement and classification fields included in this report. | Field Name | Technical Name | Description | Example Values | | ---------------------------- | -------------------- | -------------------------------------------------------------------------------------------------------------------------------------- | ------------------------ | | Customer No | `customer_no` | Internal Peoplevine customer ID | `2694343`, `2735038` | | Customer Reference | `customer_reference` | External reference ID from a previous system | `17896691`, `26403036` | | Customer Source | `customer_source` | System the customer record was originally sourced from | `book4time` | | Customer Status | `customer_status` | Whether the CRM record is active or removed | `active`, `deleted` | | Customer Type | `customer_type` | Category of the CRM record | `customer`, `admin` | | Is Member | `isMember` | Whether the person is a current member | `N` | | Was Member | `wasMember` | Whether the person was previously a member | `Y`, `N` | | Has Applied | `hasApplied` | Whether the person has submitted an application | `Y`, `N` | | When Applied | `when_applied` | Date and time the person submitted an application | `11/19/2024 6:22:54 PM` | | Member Since | `member_since` | Date of the person's first membership enrollment | `4/4/2022 5:19:53 PM` | | VIP Flag | `vip_flag` | Whether the person is flagged as a VIP | `Y`, `N` | | Keep Private | `keep_private` | Whether the profile is hidden from directory listings | `Y`, `N` | | Lifecycle Stage No | `lifecycle_stage_no` | ID of the CRM lifecycle stage the person is in | `0`, `1`, `2`, `4`, `5` | | Enable House Account | `enableHouseAccount` | Whether a house account is enabled for this person | `Y`, `N` | | App Installed | `app_installed` | Whether the person has installed the mobile app | `Y`, `N` | | App Installed On | `app_installed_on` | Date the mobile app was installed (`1/1/1900` = never) | `10/30/2022 10:12:40 PM` | | Last Login | `last_login` | Date of the person's last portal login | `6/5/2024 10:20:50 PM` | | Last Accessed | `last_accessed` | Date the person's record was last accessed by any user | `6/1/2026 9:04:58 PM` | | Last Communication | `last_contacted` | Date of the person's last communication. `last_contacted` is the underlying table field; it surfaces to users as "Last Communication". | `9/21/2021 1:39:03 AM` | | Last Communication (display) | `lastCommunication` | User-facing copy of the same last-communication date as `last_contacted`. | `3/16/2021 8:29:44 AM` | | Last Email Opened | `lastEmailOpened` | Date the person last opened an email | `11/23/2025 8:26:50 PM` | | Last Newsletter | `lastNewsletter` | Date the last newsletter was sent to this person | `10/29/2025 2:46:02 PM` | | Last Page View | `lastPageView` | Date the person last viewed a page on the portal | `8/27/2025 5:43:35 PM` | | Last Touchpoint | `lastTouchpoint` | Date of the most recent touchpoint recorded for this person | `10/29/2025 2:47:17 PM` | | Last Visit | `lastVisit` | Date of the person's most recent check-in (via the Check-In App or manually checking in via the Control Panel) | `2/8/2023 5:07:20 PM` | | Total Spent | `totalSpent` | Total amount the person has spent across all transactions | `0`, `209.88` | | Total Touchpoints | `totalTouchpoints` | Total number of engagement touchpoints recorded | `0`, `15` | | Total Visits | `totalVisits` | Total number of check-ins recorded | `0`, `12` | | Account Access | `account_access` | Whether the person has portal account access | `Yes`, `No` | *** ## Membership Activity Fields available in the **Membership Activity** export from Build a Custom Report. > Common CRM fields (name, address, contact details, opt-ins) are shared across all report types — see Customer CRM Data above. Membership Activity is the member **check-in / scan** report — each row is a scan (check-in) event, not a card-status-change log. | Field Name | Technical Name | Description | Example Values | | ------------------ | -------------------- | -------------------------------------------------------------------------------------------------- | -------------------------------- | | Customer No | `customer_no` | Internal Peoplevine customer ID | `2675210`, `2675212` | | Membership ID | `membership_id` | Member-facing membership card number | `17445583`, `66746486` | | Membership No | `membership_no` | Internal ID of the membership program | `2101`, `3024` | | Membership Title | `membership_title` | Name of the membership program | `"Gold Membership"` | | Membership Details | `membership_details` | Membership details captured with the scan | Text | | Card Status | `card_status` | Status of the membership card | `active`, `pending`, `cancelled` | | Check-In No | `checkin_survey_no` | Internal ID of the check-in survey configured on the membership program (not the per-scan record). | Number | | Scan Date | `scan_date` | Date and time of the scan | `9/29/2023 1:05:02 PM` | | Scan Location | `scan_location` | Where the scan was recorded | Text | | Scan Notes | `scan_notes` | Notes recorded with the scan | Text | | Scanned By | `scanned_by` | Who or what recorded the scan | Text | | Scanned Type | `scanned_type` | Type of scan recorded | `user` | | Scan Status | `scan_status` | Status of the scan | Text | | Device Type | `device_type` | Device type recorded on the member's CRM record (a customer-level field, not the scanning device). | Text | *** ## Event Data Fields available in the **Event Data** export from Build a Custom Report. This is event-level data only — for per-attendee ticket data, use Event Guest List. > Common CRM fields (name, address, contact details, opt-ins) are shared across all report types — see Customer CRM Data above. | Field Name | Technical Name | Description | Example Values | | -------------------- | ---------------------- | -------------------------------------------------------------------- | ------------------------------------------------------ | | Event No | `event_no` | Internal numeric ID for the event record | `58862`, `89836` | | Event ID | `event_id` | UUID for the event record | UUID | | Event Title | `event_title` | Title of the event | `"Summer Gala"` | | Event Summary | `event_summary` | Short summary or subtitle for the event | Free text | | Event Description | `event_description` | Full event description | Free text | | Event Status | `event_status` | Approval/publication status of the event | `approved`, `pending`, `denied`, `cancelled` | | Event Type | `event_type` | How the event handles attendance | `public`, `ticket`, `register`, `external`, `standard` | | Event Display | `event_display` | Audience the event is displayed to | `public`, `members`, `private`, `customers` | | Visibility | `visibility` | Access level for the event | `public`, `members`, `admin` | | Visibility Scope | `visibility_scope` | JSON list of membership programs the event is restricted to | JSON | | Event Date | `event_date` | Start date and time of the event | `12/3/2021 5:00:00 PM` | | Event Date End | `event_date_end` | End date and time of the event | `12/3/2021 6:00:00 PM` | | Event Duration | `event_duration` | Duration value (internal numeric representation) | `-1062902160` | | Event Timezone | `event_timezone` | UTC offset for the event timezone | `0`, `-8` | | Event Timezone ID | `event_timezone_id` | Windows timezone name for the event | `Eastern Standard Time` | | Event Venue | `event_venue` | Name of the venue | `"The Grand Ballroom"` | | Event Location | `event_location` | Full address of the event venue | Free text | | Event Latitude | `event_latitude` | Latitude coordinate of the event location | `41.6773775` | | Event Longitude | `event_longitude` | Longitude coordinate of the event location | `-87.6538017` | | Category No | `category_no` | ID of the event category | `4702`, `4703` | | Category Name | `category_name` | Name of the event category | `"General"`, `"Late Night"`, `"Music"` | | Event Flag | `event_flag` | Promotional flag applied to the event | `featured` | | Event Repeat | `event_repeat` | Repeat interval setting for recurring events (0 = no repeat) | `0`, `1`, `7` | | Event Graphic | `event_graphic` | URL to the main event image | URL | | External Link | `external_link` | External URL linked from the event | URL | | Event Settings | `event_settings` | JSON blob of display configuration | JSON | | Hide Tickets | `hideTickets` | Whether ticket options are hidden from the event page | `Y`, `N` | | Enable Reserved | `enableReserved` | Whether reserved seating is enabled for the event | `Y`, `N` | | Allow Cancel | `allow_cancel` | Whether attendees can cancel their registration | `Y`, `N` | | Allow Transfer | `allow_transfer` | Whether attendees can transfer their ticket/registration | `Y`, `N` | | Cancel Cutoff | `cancel_cutoff` | Minutes before event start after which cancellations are blocked | `0`, `90`, `4320` | | Send Calendar Invite | `sendCal` | Whether a calendar invite is sent to registrants | `Y`, `N` | | Survey No | `survey_no` | ID of a survey or form linked to the event (0 = none) | `0`, `6131` | | Waitlist Form | `waitlist_form` | ID of the waitlist form linked to the event (0 = none) | `0`, `4850` | | Payment Processor No | `payment_processor_no` | ID of the payment processor configured for the event | `339`, `865` | | Business Location No | `business_location_no` | ID of the location associated with the event | `0`, `160039` | | Template No | `template_no` | ID of the email template used for event communications (0 = default) | `0` | | Created On | `created_on` | Date and time the event record was created | `12/3/2021 6:46:57 PM` | *** ## Event Guest List Fields available in the **Event Guest List** export from Build a Custom Report. One row per attendee/ticket. > This report is best pulled from the specific event detail page — you will receive the guest list for just that event. If you run it from Build a Custom Report without applying filters, you will get all events combined. > Common CRM fields (name, address, contact details, opt-ins) are shared across all report types — see Customer CRM Data above. | Field Name | Technical Name | Description | Example Values | | ------------------ | --------------------- | ------------------------------------------------------------------------------------------------------------------------------------------- | ----------------------------------------------- | | Event No | `event_no` | Internal numeric ID for the event | `88097`, `151149` | | Event Title | `event_title` | Title of the event | `"Summer Gala 2026"` | | Event Type | `event_type` | How the event handles attendance | `ticket`, `public`, `register` | | Event Status | `event_status` | Approval/publication status of the event | `approved`, `pending`, `denied` | | Event Date | `event_date` | Start date and time of the event | `1/30/2024 6:00:00 PM` | | Event Date End | `event_date_end` | End date and time of the event | `2/29/2024 7:00:00 PM` | | Event Venue | `event_venue` | Name of the event venue | `"The Grand Ballroom"` | | Category Name | `category_name` | Name of the event category | `"Eat & Drink"`, `"Jazz"` | | Ticket Log No | `event_ticket_log_no` | Unique ID for this specific ticket/registration log entry | `731641`, `1244404` | | Ticket No | `event_ticket_no` | ID of the ticket type (0 = free/register event) | `254950`, `0` | | Ticket Title | `ticket_title` | Name of the ticket tier | `"RSVP"`, `"GA"` | | Ticket Description | `ticket_description` | Description of the ticket tier | Free text | | Ticket Price | `ticket_price` | Price paid for the ticket | `0`, `10`, `100` | | Ticket Tax | `ticket_tax` | Tax applied to the ticket | `0`, `0.3` | | Ticket Serial | `ticket_serial` | Unique serial number for the individual ticket | UUID or numeric string | | Ticket Status | `ticket_status` | Current status of the ticket | `register`, `purchased`, `scanned`, `cancelled` | | Ticket Notes | `ticket_notes` | Notes on how the ticket was acquired or transferred | `"Purchased via Control Panel"` | | Ticket Scan Date | `scan_date` | Date and time the ticket was scanned for entry (`1/1/1900` = not scanned) | `5/7/2026 8:15:55 AM` | | Ticket Scan Out | `scan_out` | Date and time of a second scan of the same ticket (`1/1/1900` = none). Guests aren't typically scanned out, but a repeat scan records this. | `11/18/2022 4:29:45 PM` | | Purchase Date | `purchase_date` | Date and time the ticket was purchased | `3/6/2024 10:10:56 PM` | | When Applied | `when_applied` | Date and time the guest registered or applied | `8/1/2023 10:42:55 PM` | | On Sale | `on_sale` | Date ticket sales opened | `3/6/2024 6:00:00 AM` | | Off Sale | `off_sale` | Date ticket sales closed | `12/31/9999 11:59:59 PM` | | Original Quantity | `original_quantity` | Total capacity of this ticket tier | `20`, `244` | | Available Quantity | `available_quantity` | Remaining tickets available at time of export | `14`, `0` | | Order Minimum | `order_minimum` | Minimum number of tickets per order | `1`, `2` | | Order Maximum | `order_maximum` | Maximum number of tickets per order | `1`, `20` | | Order Item No | `order_item_no` | Order line item ID linked to this ticket purchase | `21648818` | | Transaction No | `transaction_no` | Payment transaction ID linked to this ticket (0 = free) | `0`, `10562663` | | Allow Cancel | `allow_cancel` | Whether the attendee can cancel | `Y`, `N` | | Allow Transfer | `allow_transfer` | Whether the attendee can transfer the ticket | `Y`, `N` | | Is Member | `isMember` | Whether the attendee is a current member | `Y` | | Was Member | `wasMember` | Whether the attendee was previously a member | `Y`, `N` | | Membership ID | `membership_id` | Membership card number for the attendee | `66746486` | | Membership Name | `membership_name` | Name of the membership program | `"Gold Membership"` | *** ## Gift Certificates Fields available in the **Gift Certificates** export from Build a Custom Report. > Common CRM fields (name, address, contact details, opt-ins) are shared across all report types — see Customer CRM Data above. | Field Name | Technical Name | Description | Example Values | | --------------------------- | ----------------------------- | --------------------------------------------------------------------------------------------- | ---------------------------------------------- | | Gift Card No | `gift_card_no` | Internal ID for the gift certificate / house credit record | `169810`, `170091` | | Gift Card PIN | `gift_card_pin` | PIN associated with the gift certificate | `1031`, `6346` | | Gift Card Type | `gift_card_type` | Type of credit instrument | `giftcard`, `stipend`, `deposit`, `rewardcert` | | Reference Type | `reference_type` | What the credit can be used for — the gift-card/stipend **subtype** (e.g. F\&B, spa, events). | Usage subtype | | Reference No | `reference_no` | ID of the specific item the credit is restricted to. Usually `0` (no specific item). | `0` | | Business Location No | `business_location_no` | Location where the credit can be used. | `0`, `160039` | | Serial Number | `serial_number` | Customer-facing serial number for the gift certificate | `14278574`, `12956607` | | Status | `status` | Whether the gift certificate is currently usable | `active`, `inactive` | | Initial Value | `initial_value` | Value at the time the gift certificate was issued | `50`, `100`, `500` | | Current Value | `current_value` | Remaining balance on the gift certificate | `0`, `50`, `9235.57` | | Starting Balance This Month | `starting_balance_this_month` | Balance at the start of the current billing month | `0`, `50`, `9235.57` | | Charged Last Month | `charged_last_month` | Amount charged against the certificate in the previous month | `0`, `9.9`, `14.63` | | Charged This Month | `charged_this_month` | Amount charged against the certificate in the current month | `0` | | Expires On | `expires_on` | Expiration date (`12/31/9999` = no expiry) | `12/31/9999`, `8/31/2025` | | Transaction No | `transaction_no` | Payment transaction ID for the purchase of this gift certificate | `0`, `2502688` | | Purchased Customer No | `purchased_customer_no` | Customer ID of the person who purchased the gift certificate | `2697771`, `2694203` | | Customer No | `customer_no` | Customer ID of the person the gift certificate is assigned to | `2697771`, `2707634` | | Created On | `created_on` | Date the gift certificate record was created | `2/8/2021 6:20:46 PM` | *** ## Newsletter Log Fields available in the **Newsletter Log** export from Build a Custom Report. One row per recipient per send. > Common CRM fields (name, address, contact details, opt-ins) are shared across all report types — see Customer CRM Data above. | Field Name | Technical Name | Description | Example Values | | --------------------- | ----------------------- | -------------------------------------------------------------- | --------------------------------------- | | Newsletter Log No | `newsletter_log_no` | Unique ID for this send log entry | `108288604`, `108538931` | | Newsletter No | `newsletter_no` | Internal ID of the newsletter | `94779`, `97116` | | Newsletter Subject | `newsletter_subject` | Subject line of the newsletter | Free text | | Newsletter Campaign | `newsletter_campaign` | Campaign label associated with the newsletter | Free text | | Newsletter Type | `newsletter_type` | Type of send | `notification`, `marketing`, `campaign` | | Newsletter Status | `newsletter_status` | Approval status of the newsletter | `approved`, `pending`, `denied` | | Newsletter Importance | `newsletter_importance` | Priority level of the newsletter send | `Normal`, `High` | | Message Type | `message_type` | Channel the message was sent via | `email`, `sms` | | Created On | `created_on` | Date and time the message was sent | `5/14/2026 7:01:27 AM` | | Message Opened | `message_opened` | Whether the recipient opened the message | `Y`, `N` | | Message Opened On | `message_opened_on` | Date and time the message was opened (`1/1/1900` = not opened) | `5/2/2026 7:32:22 AM` | | Message Clicked | `message_clicked` | Whether the recipient clicked a link in the message | `Y`, `N` | | Message Clicked On | `message_clicked_on` | Date and time a link was clicked (`1/1/1900` = not clicked) | `5/27/2026 6:47:35 PM` | | Message Failed | `message_failed` | Whether delivery of the message failed | `Y`, `N` | | Reported Spam | `reported_spam` | Whether the recipient reported the message as spam | `Y`, `N` | | Caused Opt Out | `caused_opt_out` | Whether this send caused the recipient to opt out | `Y`, `N` | | Open Count | `open_count` | Number of times this message was opened by this recipient | `0`, `1`, `3` | | Click Count | `click_count` | Number of times links were clicked by this recipient | `0`, `1`, `15` | | Total Sent | `totalSent` | Total number of recipients for this newsletter send | `28`, `4` | | Total Opened | `totalOpened` | Total opens across all recipients for this send | `3`, `8` | | Total Clicks | `totalClicks` | Total link clicks across all recipients for this send | `0`, `3` | | Total Failed | `totalFailed` | Total failed deliveries for this send | `0`, `1` | | Total Opted Out | `totalOptedOut` | Total recipients who opted out following this send | `0`, `1` | | Send From | `send_from` | Sender name displayed to the recipient | `"The Club"` | | Send From Email | `send_from_email` | Sender email or phone number | `info@peoplevine.com` | | Reply To | `reply_to` | Reply-to address for the newsletter | `info@peoplevine.com` | | Preview Text | `preview_text` | Preview/preheader text displayed in the inbox | Free text | *** ## Products (with Attributes) Fields available in the **Products (with Attributes)** export from Build a Custom Report. One row per product. > Common CRM fields in this report belong to the staff user who created the product, not a customer. | Field Name | Technical Name | Description | Example Values | | ------------------- | --------------------- | --------------------------------------------------- | --------------------------------------------------- | | Product No | `product_no` | Internal ID of the product | `76692`, `76695` | | Product Short | `product_short` | Short/display name of the product | `"Grilled Salmon"`, `"Caesar Salad"` | | Product Long | `product_long` | Long name of the product | `"Club Burger"` | | Product SKU | `product_sku` | Stock-keeping unit identifier | `16351485`, `12737549` | | Product Brief | `product_brief` | Brief description of the product | Free text | | Product Description | `product_description` | Full description of the product | Free text | | Product Type | `product_type` | Category of the product (`fandb` = Food & Beverage) | `physical`, `fandb`, `digital`, `bundle`, `service` | | Product Status | `product_status` | Availability status | `active`, `pos`, `inactive`, `archived` | | Product Flag | `product_flag` | Promotional flag | `None Selected`, `Featured`, `Frontpage` | | Visibility | `visibility` | Who can see the product | `public`, `hidden`, `admin`, `members`, `archive` | | Category Name | `category_name` | Product category name | `"Mains"`, `"Starters"`, `"Dining"` | | MSRP Price | `msrp_price` | Listed selling price | `8.5`, `26`, `17.95` | | Tax Rate | `tax_rate` | Tax rate applied to the product | `0`, `0.02`, `0.015` | | Shipping Fee | `shipping_fee` | Shipping fee | `0`, `4`, `10` | | Handling Fee | `handling_fee` | Handling fee | `0`, `2` | | Product Weight | `product_weight` | Weight (for shipping calculations) | `1`, `1.5`, `3` | | Unit Type | `unit_type` | Unit of measure | `"Slice"`, `"Pair"`, `"day"` | | Min Qty | `min_qty` | Minimum order quantity | `1`, `0` | | Max Qty | `max_qty` | Maximum order quantity (0 = unlimited) | `0`, `10` | | Flag Limited | `flag_limited` | Whether the product has limited stock | `Y`, `N` | | Flag Backorders | `flag_backorders` | Whether backorders are allowed | `Y`, `N` | | On Demand | `on_demand` | Whether the product is made to order | `Y`, `N` | | External ID | `external_id` | External system ID for the product | `102000007`, `CMSS` | | Reference No | `reference_no` | ID of linked entity (e.g. membership program) | `0`, `4894` | | Reference Type | `reference_type` | Type of linked entity | `membership`, `voucher`, `giftcard` | | Created On | `created_on` | Date the product record was created | `1/28/2021 3:11:36 AM` | | Modified On | `modified_on` | Date the product record was last modified | `6/14/2025 1:00:13 AM` | *** ## Product Sales Activity Fields available in the **Product Sales Activity** export from Build a Custom Report. One row per order line item. The report covers both native Peoplevine products and products synced from connected third-party commerce integrations. > Common CRM fields (name, address, contact details, opt-ins) are shared across all report types — see Customer CRM Data above. | Field Name | Technical Name | Description | Example Values | | ----------------- | ------------------- | -------------------------------------------------------- | --------------------------------------------------- | | Order No | `order_no` | Internal ID of the sales order | `2398172`, `2398267` | | Order Item No | `order_item_no` | Internal ID of the line item within the order | `8623633`, `8623949` | | Order Date | `order_date` | Date and time the order was placed | `4/8/2022 6:38:22 PM` | | Order Status | `order_status` | Current status of the order | `completed`, `cancelled`, `processing` | | Order Type | `order_type` | Whether this was a purchase or saved order | `purchase`, `save` | | Order Via | `order_via` | Channel through which the order was placed | `ecommerce`, `pos`, `pms`, `spa`, `connectedpos` | | Order Source | `order_source` | Integration or system that originated the order | `book4time`, `Simphony`, `opera`, `dash` | | Order Price | `order_price` | Unit price of the item at the time of purchase | `20`, `15`, `40` | | Order Quantity | `order_quantity` | Number of units ordered | `1`, `2`, `6` | | Pull Quantity | `pull_quantity` | Number of units fulfilled | `1`, `2`, `0` | | Returned Quantity | `returned_quantity` | Number of units returned | `0`, `1` | | Discount Rate | `discount_rate` | Discount percentage applied to the item | `0`, `0.01`, `0.1` | | Discount Total | `discount_total` | Total discount amount | `0`, `2`, `4` | | Tax Rate | `tax_rate` | Tax rate applied to the item | `0`, `0.1025`, `0.0875` | | Tax Total | `tax_total` | Tax amount | `0`, `1.38`, `2.77` | | Item Status | `item_status` | Current status of the line item | `active`, `cancelled` | | Is Subscription | `isSubscription` | Whether this item is part of a subscription | `Y`, `N` | | Product No | `product_no` | Internal ID of the product | `231791`, `1547030` | | Product Short | `product_short` | Short/display name of the product | `"House Wine"`, `"Grilled Salmon"` | | Product SKU | `product_sku` | SKU of the product | UUID or string | | Product Type | `product_type` | Category of the product (`fandb` = Food & Beverage) | `physical`, `fandb`, `bundle`, `service`, `digital` | | MSRP Price | `msrp_price` | Listed price of the product | `1`, `21`, `8` | | Schedule Book No | `schedule_book_no` | ID of the schedule booking linked to this item (0 = N/A) | `0`, `533009` | | Event Ticket No | `event_ticket_no` | ID of the event ticket linked to this item (0 = N/A) | `231791`, `0` | | External ID | `external_id` | External system ID for the product | `4500345`, `CMSS` | | Customer No | `customer_no` | Internal Peoplevine customer ID | `2675212`, `2697771` | | Created On | `created_on` | Date the order was created | `4/8/2022 6:38:22 PM` | *** ## Sales Orders Fields available in the **Sales Orders** export from Build a Custom Report. One row per order. > Common CRM fields (name, address, contact details, opt-ins) are shared across all report types — see Customer CRM Data above. | Field Name | Technical Name | Description | Example Values | | ------------------- | --------------------- | ------------------------------------------------------------- | -------------------------------------------------- | | Order No | `order_no` | Internal ID of the sales order | `14086385`, `14099849` | | External Order No | `external_order_no` | Order ID from an external/integrated system | UUID or string | | Order Date | `order_date` | Date and time the order was placed | `4/21/2026 3:13:58 PM` | | Order Status | `order_status` | Current status of the order | `completed`, `processing`, `cancelled` | | Order Type | `order_type` | Whether this was a purchase or saved order | `purchase`, `save` | | Order Via | `order_via` | Channel through which the order was placed | `ecommerce`, `pos`, `fandb`, `connectedpos`, `spa` | | Order Source | `order_source` | Integration or system that originated the order | `dash`, `Simphony`, `book4time`, `connectedpos` | | Order Currency | `order_currency` | Currency the order was placed in | `USD`, `CAD`, `EUR`, `GBP`, `THB` | | Sub Total | `sub_total` | Order subtotal before tax, tip, and shipping | `110`, `11.79`, `100` | | Tax Total | `tax_total` | Total tax applied to the order | `18.9`, `4.45`, `0` | | Tip Total | `tip_total` | Tip amount added to the order | `0`, `10`, `29.56` | | Shipping Total | `shipping_total` | Shipping amount | `0`, `22.02`, `10` | | Discount Total | `discount_total` | Total discount applied to the order | `11`, `2`, `0` | | Service Fee | `service_fee` | Service fee applied to the order | `0` | | Order Total | `order_total` | Total order amount | `117.9`, `15.06`, `0` | | Balance Due | `Balance Due` | Outstanding balance remaining on the order | `0`, `306.61`, `37.5` | | Check No | `Check #` | POS check number associated with the order | `526`, `17077002` | | Order Note | `order_note` | Staff or system note on the order | `"placed via POS"` | | Flag Paid | `flag_paid` | Order paid flag (`-1` = paid, `0` = unpaid, other = user ID) | `-1`, `0`, `4222` | | Flag Paid Date | `flag_paid_date` | Date the order was marked as paid | Date | | Flag Completed | `flag_completed` | Order completion flag (`-1` = completed, `0` = not completed) | `-1`, `0` | | Flag Completed Date | `flag_completed_date` | Date the order was marked as completed | Date | | Flag Shipped | `flag_shipped` | Order shipped flag (`-1` = shipped, `0` = not shipped) | `-1`, `0` | | Flag Shipped Date | `flag_shipped_date` | Date the order was marked as shipped | Date | | Flag Returned | `flag_returned` | Whether the order has been returned (`0` = not returned) | `0` | | Flag Returned Date | `flag_returned_date` | Date the order was returned | Date | | Gift Flag | `gift_flag` | Whether the order is a gift | `Y`, `N` | | Fiscal ID | `fiscal_id` | Fiscal/tax authority invoice ID | Numeric string | | Location Name | `location_name` | Name of the business location | `"Main Club"`, `"Dining Room"` | | Customer No | `customer_no` | Internal Peoplevine customer ID | `2675212`, `2697771` | | Created On | `created_on` | Date the order record was created | `4/21/2026 3:13:58 PM` | *** ## Subscriptions Fields available in the **Subscriptions** export from Build a Custom Report. One row per subscription. > Common CRM fields (name, address, contact details, opt-ins) are shared across all report types — see Customer CRM Data above. | Field Name | Technical Name | Description | Example Values | | ---------------------- | ------------------------ | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ------------------------------------------------------ | | Subscription No | `subscription_no` | Unique subscription number per CRM profile. Each person with an assigned subscription gets a unique subscription number. | `150091`, `176777` | | Service No | `service_no` | Subscription group number. When a service is created, it gets one service number, and unique subscription numbers are generated underneath it per person. | `11488`, `11542` | | Service Title | `service_title` | Name of the subscription service or membership program | `"Gold Membership"` | | Service SKU | `service_sku` | SKU of the subscription service | `"PLATINUM"` | | Subscription Status | `subscription_status` | Current status of the subscription | `active`, `pending`, `failed`, `cancelled`, `archived` | | Subscription Frequency | `subscription_frequency` | Billing cycle | `monthly`, `annually`, `quarterly`, `daily`, `semi` | | Subscription Rate | `subscription_rate` | Amount charged per billing cycle | `200`, `50`, `10` | | Subscription Currency | `subscription_currency` | Currency for the subscription charge | `USD`, `GBP`, `EUR` | | Subscription Details | `subscription_details` | Staff notes on the subscription | Free text | | Subscribed On | `subscribed_on` | Date the subscription started (typically correlates with the member's enrollment date) | `2/16/2021 12:00:00 AM` | | Renewal Date | `renewal_date` | Annual renewal date. This does not follow the same cadence as the subscription frequency. Not automatically populated when a subscription is created — needs to be manually added. | Date | | Last Date | `last_date` | Date of the most recent billing attempt | Date | | Next Date | `next_date` | Date of the next scheduled billing | Date | | Next Status | `next_status` | Scheduled status change on next billing date | `cancelled`, `upgraded`, `downgraded`, `age` | | Reactivate On | `reactivate_on` | Date a suspended subscription is scheduled to reactivate. Only applies to suspended statuses — a cancelled subscription will never reactivate. | Date | | Requested Cancel Date | `requested_cancel_date` | Date the subscription will automatically cancel (`1/1/1900` = not set) | Date | | Price Monthly | `price_monthly` | Monthly price option | `220`, `49`, `1` | | Price Quarterly | `price_quarterly` | Quarterly price option | `400`, `100`, `0` | | Price Semi | `price_semi` | Semi-annual price option | `0`, `200` | | Price Annually | `price_annually` | Annual price option | `2400`, `549`, `0` | | Price Weekly | `price_weekly` | Weekly price option | `60`, `0`, `10` | | Price Daily | `price_daily` | Daily price option | `0`, `10`, `20` | | Initiation Fee | `initiation_fee` | One-time setup/initiation fee | `10000`, `99`, `0` | | Payment Type | `payment_type` | Payment method used | `ach`, `creditcard` | | Card No | `card_no` | ID of the payment card on file (0 = none) | `0`, `593462` | | Card Type | `card_type` | Type of payment card | `checking`, `amex`, `visa`, `mastercard` | | Last Four | `last_four` | Last 4 digits of the payment card | `9911`, `8431` | | Card Year | `card_year` | Expiry year of the payment card | `0`, `2026`, `2033` | | Auto Charge | `auto_charge` | Whether the subscription auto-charges the card on file | `Y`, `N` | | Auto Renew | `auto_renew` | Whether the subscription automatically renews | `Y` | | Allow Cancel | `allow_cancel` | Whether the member can cancel their subscription | `Y`, `N` | | Allow Change | `allow_change` | Whether the member can change their subscription plan | `Y`, `N` | | Prorate Billing | `prorate_billing` | Whether billing is prorated when starting mid-cycle | `Y`, `N` | | Remaining Payments | `remainingPayments` | Payments remaining in a fixed-term subscription | `0` | | Total Payments | `totalPayments` | Total payments made on this subscription | `0` | | Was Upgraded | `wasUpgraded` | Whether this subscription was the result of an upgrade | `Y`, `N` | | Membership ID | `membership_id` | Member-facing membership card number | `61695724` | | Membership Name | `membership_name` | Name of the membership program | `"Gold Membership"` | | Customer No | `customer_no` | Internal Peoplevine customer ID | `2697771`, `2694203` | | Created On | `created_on` | Date the subscription record was created | `2/16/2021 6:44:37 PM` | | Modified On | `modified_on` | Date the subscription was last modified | `6/1/2026 3:02:15 PM` | *** ## Survey Applications Fields available in the **Survey Applications** export from Build a Custom Report. > Common CRM fields (name, address, contact details, opt-ins) are shared across all report types — see Customer CRM Data above. | Field Name | Technical Name | Description | Example Values | | --------------------- | ----------------------- | ----------------------------------------------------------------- | ----------------------------------------------------- | | Survey Application No | `survey_application_no` | Internal ID of the application record | `37377`, `298602` | | Survey Group No | `survey_group_no` | Internal ID of the survey/application form | `341`, `709` | | Survey Group Name | `survey_group_name` | Name of the survey or application form | `"Contact Us"`, `"Member Application"` | | Application Number | `application_number` | Human-readable application reference number | `324324`, `3154164` | | Application Status | `application_status` | Current review status of the application | `new`, `pending`, `reviewing`, `approved`, `rejected` | | Application Notes | `application_notes` | Staff notes on the application | Free text | | Application Fee | `application_fee` | Fee charged at the time of submission | `0`, `89`, `15` | | Transaction No | `transaction_no` | Payment transaction ID for the application fee (0 = free) | `0`, `6297630` | | When Applied | `when_applied` | Date and time the application was submitted | `3/3/2022 7:48:32 PM` | | Reference No | `reference_no` | ID of the entity the application is for (e.g. membership program) | `0`, `2392`, `4894` | | Reference Type | `reference_type` | Type of entity the application is linked to | `membership` | | Allow Edit | `allow_edit` | Whether the applicant can edit responses after submission | `Y`, `N` | | Require Confirm | `require_confirm` | Whether a confirmation step is required before submission | `Y`, `N` | | Customer No | `customer_no` | Internal Peoplevine customer ID (0 = no CRM profile linked) | `0`, `2697771` | | Created On | `created_on` | Date the application record was created | `9/21/2021 4:44:14 PM` | *** *Last updated: 2026-06-12* --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://help.peoplevine.com/products/control-panel-overview/reports-overview/data-dictionary-preview.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.