All tutorials

Azimea Academy · Full walkthrough

Contacts: import, map and verify a small file

Import a real demonstration CSV, map its columns and review the result in the contact record. Keep stored contact details separate from permission and eligibility to receive a message.

2:44Audio: EnglishCaptions: English
Free to watch. No account needed.

What you will see

  • Import a real demonstration CSV, map its columns and review the result in the contact record.
  • Keep stored contact details separate from permission and eligibility to receive a message.

Transcript

A useful contact import preserves the meaning of the source data and the permission attached to it.

We will upload a small fictional contact file, review how its columns map to the account, choose the appropriate permission treatment,

and inspect the resulting records. No messages will be sent.

The file import starts with a CSV or spreadsheet. We will use a small demonstration file containing an email address, a first name, a

last name, and a city. The preview lets us review the structure before creating records, so we can catch a mismatched column early.

Column mapping tells the application what each value represents. We will explicitly match the address, name, and city fields to their

corresponding contact properties. Review samples as well as headings.

A familiar column name does not guarantee that every value underneath it has the expected format.

Importing an address does not establish permission to send marketing.

Our fictional file has no permission evidence, so we will import it without adding subscription permission.

For your own data, choose the option that accurately reflects the permission you hold and can support with the appropriate evidence.

Starting the import creates a background task. The progress view reports its actual status, rather than assuming that the upload

completed every record. We will wait for this demonstration import to finish, then review the counts before relying on the contacts in

another workflow.

The result distinguishes records that were imported, updated, or rejected.

That makes it possible to review a repeat import without assuming that every row created a new contact.

Investigate reported errors before retrying a file and keep the source data accurate rather than silently dropping problematic rows.

Back in the contact list, search helps us verify a specific imported record.

We will find Alex from the demonstration file. Checking a recognizable example is a useful follow-up to the aggregate import counts,

particularly when the source includes several names or locations.

The contact record brings the stored details and sending permission together.

Review the imported values here before building an audience around them.

A contact can exist in the account without being eligible for a marketing email.

Storing the record and deciding who may receive a message are separate concerns.

The file has become real contact records with its columns mapped and its permission treatment kept explicit.

Before importing a larger audience, use a small representative sample and inspect the result.

That approach makes it easier to resolve data issues before they affect a campaign.