Skip to main content
At the end of this page, your existing end user records are in Tars and you can export them again.

​
Before you start

Before you start, sign in to the dashboard and select the organization you want to work in.
  • Add user requires permission to manage end users.
  • Import is visible only to organization admins.
  • Export requires permission to export data.
  • To create profiles from your own systems, see the end user API.

​
Where these actions live

Open Users in the sidebar. The All users tab shows the directory, and its toolbar holds all three actions.

​
Add one profile

1

Select Add user in the toolbar

The Add user modal opens.
2

Fill in the details

The fields are First name, Last name, Email, Phone, Labels, and Tags. The phone field is an international input. Type a tag and press Enter to add it.At least one of email or phone is required. Saving with neither shows Email or phone is required.
3

Select Save

A User added message confirms the new profile.
If the email or phone matches an existing profile, Tars shows Existing user matched instead of creating a duplicate.

​
Import a CSV file

The Import users modal walks three steps: Upload, Map columns, and Check. To import into a segment instead, see Import into a segment.

​
Step 1: Upload

1

Select Import in the toolbar

The Import users modal opens on the Upload step.
2

Drop your CSV on the dropzone

Only .csv files up to 20 MB are accepted. The file must be UTF-8 with a header row. Select Download sample.csv for a working example with the columns name,email,phone,company,country,tags_list.The modal moves to Map columns as soon as the file parses.
If the file cannot be read, the step shows one of these errors:

​
Step 2: Map columns

The mapping grid has three columns: CSV column, TARS field, and Preview (first row). Tars auto-maps columns from common header names, such as full_name to Name and mobile to Phone. A header that matches the key of an end user custom attribute maps to that attribute. Adjust any mapping from the TARS field dropdown. The field options are: At least one of Email, Phone, or Identifier (anonymousId) must be mapped. Until then the step blocks with Required: at least one identity column (email / phone / identifier). Once an identity column is mapped, the same line turns muted grey and confirms the file is ready to preview. The step also blocks Next and lists the reason when:
  • two columns in the file have the same header
  • a column that is not skipped has a header that starts with $ or uses characters other than English letters, digits, spaces, and punctuation
  • the file has more than 500,000 rows
Select Next to check the file.

​
Step 3: Check and start

Tars reads the whole file in your browser and matches every row against existing profiles. The check does not write anything. When it finishes, three cards show exact counts for the file: If rows are skipped, the Skipped rows list shows a count for each reason, such as Invalid email or Duplicate in file. Sample rows follow, each with its row number and reason. The import report holds the full list. The counts are as of the check, and the import report is the final record. If no row can be imported, the start button stays disabled. If the check cannot finish, select Retry check, or start the import anyway, because the import checks every row again.
1

Optionally add tags for every imported profile

The Tags to apply to all imported users (optional) field tags every row. Tags from a mapped CSV column are merged per row on top.
2

Tick the consent acknowledgement

The checkbox confirms these end users opted in to receive outbound messages. It is required before the import can start.
3

If the check found existing profiles or could not finish, tick the update acknowledgement

This checkbox confirms that matched profiles are updated. The directory import matches by email first, then phone.
4

Select Start import

The button reads Starting… while pending, then an Import started message confirms.
The import runs in the background. The tasks tracker in the sidebar shows its progress, the final counts, and a Report download.

​
Import into a segment

Organization admins can import a CSV into a static segment from two places. The modal is titled Import CSV into segment, and every imported end user joins the segment. The steps match the directory import, with these differences:
  • The TARS field dropdown adds Segment data (this segment only). A segment data value is stored on the end user’s membership in this segment, not on the profile.
  • Columns that match no field or attribute default to segment data. Download sample.csv adds a your_own_column column as an example.
  • The check cards read New contacts, Existing contacts, and Skipped.
  • A segment import matches existing profiles by phone first, then email.
A segment holds at most 50 segment data columns. A segment data column name is at most 64 characters and cannot start with $ or _. When you import into a segment again, the Existing contacts card also says how many end users are already in the segment. The file replaces their values in the mapped segment data columns, and a blank cell clears the stored value. To send segment data in a campaign, see Reuse segments in campaigns.

​
Export profiles

1

Select Export in the toolbar

The button is visible only when your role allows data export.
2

Wait for the background job

An Export started message confirms the job is running, and a download arrives when it is ready. If the job cannot start, Tars shows Could not start the export.
Export covers all end users, up to 10,000 rows. To export a subset, save the group as a segment and use Export on the segment’s Members tab.

​
Verify

The directory count chip reflects the loaded rows after the import finishes. Open an imported profile and check the Metadata section. Its Source reads CSV import. You can also filter the directory by Source equals CSV import.