Can I validate a Klaviyo profile CSV before importing it?+
Yes. This local preflight checks CSV shape, identifiers, duplicates, explicit property types, consent states and timestamps, phone-country evidence, and safe test output. It cannot query a Klaviyo account or guarantee acceptance.
Does the validator upload or save profile data?+
No. Parsing, mapping, findings, masked evidence, acknowledgments, normalization, and downloads remain in the current browser tab. Profile values are not sent to Klaviyo or csvtodashboard.
Can I upload Excel directly to a Klaviyo list?+
No. Klaviyo's list uploader requires CSV. This workspace can read one selected XLS or XLSX worksheet locally, but its handoff is a normalized CSV.
What identifier does every Klaviyo profile need?+
Every row needs an email address or phone number. The first column should be Email, Email Address, or Phone Number, and duplicate nonblank email or phone identifiers should be resolved before import.
What consent values does Klaviyo accept in a CSV?+
Consent columns use Subscribe, Never Subscribed, or Unsubscribed. A blank consent cell defaults to Never subscribed. A local format check cannot prove permission or resubscribe eligibility.
How should Klaviyo list, Boolean, and date properties be formatted?+
List values use JSON arrays with quoted items, Boolean CSV values use True or False, Numeric values omit symbols, and dates use a Klaviyo-supported date or timestamp format.
What is the Klaviyo CSV file-size limit?+
Klaviyo's current list-import guidance requires a CSV file of 50 MB or less. Split larger sources into controlled files before import.
Does a clean preflight prove consent or SMS readiness?+
No. Permission, suppressions, account role, list flows, SMS setup, sending numbers, supported countries, property mappings, and existing profiles are account state that must be reviewed in Klaviyo.