Imports Live

The Landing Zone import pipeline — upload, sample preview, column mapping, opt-in consent capture, and screening — with dropped rows counted and reported.

Updated 2 min readMaintained by Landing Zone

Open this screen in Landing Zone →

Import is how your existing contact data gets into Landing Zone. It is a pipeline, not just an upload: every file passes through preview, mapping, consent capture, and screening before it becomes a working list.

How it works

An import moves through five stages:

  • Upload. Bring in a CSV or XLSX file.
  • Sample preview. Landing Zone shows you a sample of the parsed rows so you can confirm the file reads the way you expect before anything is created.
  • Column mapping. Match your file's columns to contact fields. Mappings can be saved as reusable mapping profiles, so a file format you import regularly only needs to be mapped once. See Map imported columns.
  • Opt-in consent capture. Imports include an opt-in acknowledgment step, including confirmation of A2P 10DLC compliance and that you have a lawful basis to contact the recipients. What you record here feeds consent records.
  • Screening. A scrub run screens the incoming contacts, and you see a cost estimate before anything is charged.

The pipeline is honest about what it drops: invalid rows are removed, counted, and reported, so you know exactly how many records made it in and why the rest did not. If your import loses more rows than expected, see Resolve import errors.

When to use it

Import when you already have data — a CRM export, a purchased file, a spreadsheet you have been maintaining. If you are starting from nothing, Intelligence can build the audience instead; see Intelligence or import? for how to choose. The import a list guide walks the pipeline end to end.

Limitations

  • The opt-in acknowledgment records your confirmation — it does not verify it. You remain responsible for the lawful basis you attest to.
  • Contacts imported without a recorded opt-in default to UNVERIFIED consent, and batch and campaign SMS require verified consent.
  • Invalid rows are dropped, not repaired. Fix the source file and import again if the dropped-row report shows losses you did not expect.
  • Import quality bounds everything downstream — verify and enrich after importing, before you send.