Data & Import

CSV field mapping guide

Reference guide for mapping CSV column headers to LiftSignals fields during import.

How column mapping works

When you upload a CSV, LiftSignals reads the column headers and automatically maps them to the closest LiftSignals field. Common synonyms are recognised (e.g., "lifetime_revenue", "total_orders", "last_purchase" are all auto-mapped correctly).

After auto-mapping, you review a mapping table and can adjust any field. Unrecognised columns default to "Skip".

Field reference

LiftSignals fieldRecognised CSV namesFormatRequired?
Emailemail, email_address, customer_emailValid email addressYes (or customer_id)
Customer IDcustomer_id, id, external_idAny unique stringYes (or email)
First namefirst_name, firstname, given_nameTextNo
Last namelast_name, lastname, surnameTextNo
Phonephone, phone_number, mobileAny phone formatNo
Total spenttotal_spent, lifetime_revenue, ltv, total_orders_valueNumber without currency symbol (149.99)No
Order countorder_count, num_orders, total_orders, ordersIntegerNo
Last order datelast_order_date, last_purchase, last_orderYYYY-MM-DD, MM/DD/YYYY, or DD/MM/YYYYNo
First order datefirst_order_date, first_purchase, signup_dateYYYY-MM-DDNo
Tagstags, customer_tagsComma-separated textNo

Common mapping issues

  • Date format not recognised — Use YYYY-MM-DD (ISO 8601) for most reliable auto-detection
  • Currency symbols in total_spent — Remove $ or £ symbols. Use plain numbers: 149.99 not $149.99
  • Comma in phone numbers — If your CSV uses comma as a separator and your phone numbers contain commas, use a TSV (tab-separated) file instead
Was this article helpful?