File Import Checklist
A clean file makes for a clean import. Run through this checklist before you upload — it saves time spent re-importing later if the file gets rejected or rows fail.
In this Article
Before an Import
Do you have consent?
Make sure you have consent for all Profiles in the file you import to Audience. After import, confirm the import is completed before executing any marketing activities against the imported Profiles.
File Import Checklist
✅ Create a Subscription
For your very first file import, make sure you have a Subscription to place the Profiles into. Read more about how to create a Subscription.
💡 Have you created your Subscriptions? Profiles must be imported into at least one Subscription. You can select multiple Subscriptions during the import. If your Profiles have consent for several Subscriptions, you can handle that in a single import.
✅ Cell format and simple text data
Use only simple text data. Remove any images, charts or decorative formatting (fonts, colours, etc.).
Review the format of the cells and make sure there are no combined or split cells. It must look like a clean table when viewed as columns.
Pay attention to cells containing dates — set their type to Text in your spreadsheet before saving.
✅ One sheet
Make sure your file contains only one sheet, or that the data you need is in the first sheet of the file.
✅ No formulas
The File Import Wizard does not support formulas. Remove any existing formulas, or replace them with the resulting values.
✅ Phone numbers
Make sure phone numbers contain the country code and number in the same column, with no spaces and no leading zeros. The country code is mandatory. Follow the MSISDN format, for example: 46793699558
✅ Dates
For Date-type Attributes, we accept the date formats listed in the Dates table below (including Unix timestamps). Time zones are disregarded.
For example, the Default Attribute Date of Birth with a value like Tue, 07 Mar 1993 04:22:23 +0300 will be converted to 1993-03-07.
✅ Timestamps
For Timestamp-type Attributes, we support importing and storing Unix timestamps. Any other format will be converted to a Unix timestamp. See Timestamps below for details.
✅ Remove duplicates
Make sure there are no duplicate Profiles in your file (duplicates in the column you'll use as the Unique Identifier). Duplicates cause errors at import. Before importing, find and remove duplicates from the Unique Identifier column.
Supported file formats and encodings
We support CSV and XLSX files up to 50 MB.
For CSV files, convert to UTF-8 before import to ensure characters are correctly recognised.
For CSV files we support these delimiters: , \t | ;
Both Chinese and Cyrillic characters are supported.
When saving your Microsoft Excel file, or exporting data from another system, make sure the file is encoded as one of the following supported formats:
| Unicode | UTF-8 | Big5 |
UTF-16BE | EUC-JP | ISO-8859-1 | windows-1250 |
UTF-16LE | EUC-KR | ISO-8859-2 | windows-1251 |
UTF-32BE | KOI8-R | ISO-8859-5 | windows-1252 |
UTF-32LE | IBM420 | ISO-8859-6 | windows-1253 |
ISO-2022-JP | IBM424 | ISO-8859-7 | windows-1254 |
ISO-2022-CN | GB18030 | ISO-8859-8 | windows-1255 |
ISO-2022-KR | Shift_JIS | ISO-8859-9 | windows-1256 |
Email addresses
The Email Attribute must be formatted as a correct email address, containing a valid domain (for example gmail) and a valid domain extension (.com):
Only public email addresses can be reached via email sendings.
Phone numbers
The Mobile Attribute must have values in the MSISDN format, for example: 46793699558
[SCREENSHOT: Example phone number column in MSISDN format]
Attribute data types
Data type | What's accepted |
Text | UTF-8 encoded text (string) with a 1000-character limit. Chinese and Cyrillic characters are supported. |
Number | Number values only. For decimals, choose Number with decimals as the Attribute type. |
Number with decimals | Number values with decimal precision. |
Boolean | Only |
Location | ISO 3166-1 alpha-2 format (for example |
Date | See the Dates table below. Time zones are disregarded. |
Timestamp | Unix timestamps. Other formats are converted. See Timestamps. |
Dates
For Date-type Attributes, we accept the formats listed below. Time zones are disregarded.
Format | Result in Apsis One |
2013-02-08 | 08/02/2013 |
2013-02 | 01/02/2013 |
2013-W06-5 | 08/02/2013 |
2013-039 | 08/02/2013 |
20130208 | 21/08/1970 |
201303 | 03/01/1970 |
2013 | 01/01/1970 |
2013W065 | 08/02/2013 |
2013W06 | 04/02/2013 |
2013050 | 24/01/1970 |
2013-02-08T09 | 08/02/2013 |
2013-02-08 09 | 08/02/2013 |
2013-02-08 09:30 | 08/02/2013 |
2013-02-08 09:30:26 | 08/02/2013 |
2013-02-08 09:30:26.123 | 08/02/2013 |
2013-02-08 24:00:00.000 | 09/02/2013 |
20130208T080910,123 | 08/02/2013 |
20130208T080910.123 | 08/02/2013 |
20130208T080910 | 08/02/2013 |
20130208T0809 | 08/02/2013 |
20130208T08 | 08/02/2013 |
2013-02-08 09 | 08/02/2013 |
2013-W06-5 09 | 08/02/2013 |
2013-039 09 | 08/02/2013 |
2013-02-08 09+07:00 | 08/02/2013 |
2013-02-08 09-0100 | 08/02/2013 |
2013-02-08 09Z | 08/02/2013 |
2013-02-08 09:30:26.123+07:00 | 08/02/2013 |
2013-02-08 09:30:26.123+07 | 08/02/2013 |
6 Mar 17 21:22 UT | 06/03/2017 |
6 Mar 17 21:22:23 UT | 06/03/2017 |
6 Mar 2017 21:22:23 GMT | 06/03/2017 |
06 Mar 2017 21:22:23 Z | 06/03/2017 |
Mon 06 Mar 2017 21:22:23 z | 06/03/2017 |
Mon, 06 Mar 2017 21:22:23 +0000 | 06/03/2017 |
6 Mar 17 00:00 UT | 06/03/2017 |
6 Mar 17 00:00:00 EST | 06/03/2017 |
6 Mar 2017 00:00:00 CST | 06/03/2017 |
06 Mar 2017 00:00:00 PST | 06/03/2017 |
Mon 06 Mar 2017 00:00:00 z | 06/03/2017 |
Mon, 06 Mar 2017 00:00:00 +9999 | 06/03/2017 |
For example, the Default Attribute Date of Birth with a value like Tue, 07 Mar 1993 04:22:23 +0300 will be converted to 1993-03-07.
Timestamps
We support importing and storing Unix timestamps for Timestamp-type Attributes. Any other format will be converted.
For example, a Custom Attribute "Member since" with a value like Tue, 07 Mar 2017 04:22:23 +0300 will be converted to 1488844800 (07 Mar 2017 00:00:00 +0000).
Other details:
Timestamps (for example
1599116184) are imported without milliseconds.Negative values are supported for dates before 1970 (
01-01-1970is0).
⚠️ Note: We currently ignore the given time zone to avoid date shift. If the time zone is crucial, provide all timestamps in UTC only.
Troubleshooting
❓ My dates are showing up as 1970-something in Apsis One.
Compact numeric date formats like 20130208 (without separators) are interpreted as day-of-year values, which fall in 1970. Use a separated format such as 2013-02-08 to get the date you expect.
❓ My CSV has accented or non-Latin characters that come in garbled.
CSV files must be saved as UTF-8. Re-export from Excel as "CSV UTF-8" or convert with a text editor before uploading.
❓ My phone numbers are not being recognised.
Phone numbers must be in MSISDN format — country code + number, no spaces, no leading zeros (for example 46793699558). Leading zeros from spreadsheet auto-formatting are a common cause; format the column as Text in your spreadsheet before saving.
❓ My import shows lots of duplicate errors.
Duplicates in the Unique Identifier column will cause rows to fail. De-duplicate that column before importing — see the Excel duplicate guide linked above.
❓ Excel converted my long numeric ID to scientific notation.
Excel will silently convert numeric IDs longer than 15 digits to scientific notation, which corrupts the value. Format the column as Text in your spreadsheet before pasting or entering IDs, or save and import as CSV with the column quoted.
❓ My file is over 50 MB.
Split the file into smaller chunks, or use Scheduled Import over SFTP for very large recurring jobs.