Upload CSV contact lists to Ometria in the CSV Contact Upload screen.
You can queue a maximum of three uploads at any one time.
Each upload creates a unique contact listing.
See also: How to use a CSV upload as an automation trigger
Rules of priority
Ometria’s standard rules of priority for contact listings are:
- The Ometria preference centre
- API, CSV, Ometria overlays, and changes made directly in-app (i.e. to the single customer view)
- Ometria's JavaScript tracker
- Ometria form
- Importer (e.g. Magento or Shopify)
- Third party syncs
If there are two contact records with the same priority level, then Ometria uses the data from the most recent record.
For this reason, we recommend that you upload contacts via your importer (e.g. Shopify, Magento, or API).
Subscription statuses
Contacts uploaded via CSV retain their subscription status and timestamp unless:
- you select force subscribe or force unsubscribe from the Subscription mode panel,
- they are opted-in or opted-out via the Ometria preference centre, or;
- The contact has at least one listing with
@force_optin=TRUEand your account uses enhanced force opt-in.
If you select force subscribe or force unsubscribe while uploading your CSV, that status is prioritised over ecommerce importers e.g. Shopify or Magento.
Example:
If jane@fashion.com is uploaded via CSV with an ‘unsubscribed’ status, and Jane later re-subscribes through your website, her re-subscription is sent to Ometria through your importer. Jane’s subscription status will not change and will still be ‘unsubscribed’.
See also: Subscription timestamps
Upload requirements
File size: Maximum 100MB
Encoding: The following encoded CSV files are supported -
- Windows ISO-8859-1 (latin 1)
- UTF8
Headers
Your CSV file must contain headers in the first row.
The following headers are accepted by Ometria - they are case sensitive and must be written exactly as below.
Be aware that the email field is required for all CSV files.
| Header | Example | Description |
| jane@fashion.com | Required. | |
| id | 1234abc |
The contact listing ID (this is not the same as a customer ID). If you choose to use this header, you should supply a unique ID per contact. The ID can contain both numbers and letters. |
| prefix | Ms | |
| firstname | Jane | |
| middlename | Hortensia | |
| lastname | Smith-Jones | |
| gender | f |
This value can only be 'm' or 'f'. If this cell is left empty, gender will display as 'unknown'. |
| date_of_birth | 1990-01-01 | The date should be supplied in YYYY-MM-DD format. |
| country_id | GB | ISO 3166-1 alpha-2 code |
| preferred_lang | en-GB |
The contact's preferred language. This must be supplied in ISO 639-1 format. |
| timestamp_acquired |
The date that the contact was first acquired. This must be the exact date time in ISO 8601 format with timezone offset. |
|
| timestamp_subscribed |
The date that the contact subscribed to your marketing emails. This must be the exact date time in ISO 8601 format with timezone offset. You must include this field if you want uploaded contacts to enter welcome campaigns. See also: |
|
| timestamp_unsubscribed |
The date that the contact unsubscribed from your marketing emails. This must be the exact date time in ISO 8601 format with timezone offset. |
|
| phone_number |
UK: +447123456789 US: +1123456789 |
Use the international format. |
| properties.your_field_id |
You can use this to enter any custom field you have already configured in Ometria by replacing `custom_field` with the ID of the custom field. E.g. properties.contact_birthday
Note: If your custom field
@type is list of strings it can only be updated via via API, not via CSV or in the single customer view. See also: List of strings fields
Note: You can only segment on data that was sent after you've created your custom field.
|
|
| channel_sms_allow_marketing |
TRUE FALSE |
Whether or not a contact is opted into receiving SMS marketing. |
| channel_sms_dt_updated_marketing | YYYY-MM-DDThh:mm:ss |
Similar to the `timestamp_subscribed` field, but for SMS marketing opt-ins. This must be the exact date time in ISO 8601 format with timezone offset. If Ometria only receives the `channel_sms_allow_marketing` preference for a contact and not the timestamp, the timestamp is set to now (i.e. the time of upload). If the contact already has an SMS preference set and changes it (i.e. unsubscribes from SMS marketing) the timestamp and preference are overwritten. If the contact already has an SMS preference set and does not change it, the timestamp is only updated if it is an earlier date than the one currently stored. |
| channel_sms_marketing_optin_level |
double single |
If you have existing contacts who were double opted-in to SMS via another system, use this field to update their opt-in type to "double". |
Uploading a CSV file
Select your account name in the far right of the screen and select Contact upload from the dropdown:
Click Select CSV file to choose a CSV file from your desktop:
Add contacts to a static segment?
Choose from any of the following options:
Email subscription mode
Select a subscription method.
CSV uploads don't trigger double opt-in emails, so if you are using double opt-in for your subscriptions you should select 'Unchanged' as the Subscription mode and then use the changed segment membership trigger to enter those contacts in your double opt-in campaigns.
| Option | Description |
| Soft subscribed | Select to subscribe contacts unless they have unsubscribed already. |
| Force subscribed | Select to subscribe contacts even if they have already unsubscribed. |
| Force unsubscribe | Select to unsubscribe contacts. |
| Unchanged | Select to leave contacts' subscription statuses unchanged. |
Data protection
Before you can upload your CSV file, you must select both of the following checkboxes to confirm that:
- The list you are uploading was not purchased, rented, appended or provided by a third party, and;
- the contacts you are uploading are expecting to hear from you.
Once you have confirmed, you can click Upload to begin uploading your CSV file.
Ometria sends an email to the email address you used to log in to let you know that processing has begun.
Uploading and merging phone numbers
Be aware that if you upload a contact with a phone number which matches an existing phone number in your database, then the number will not be merged.
Example, if you upload the following two records, one in January and one in February, with the same phone number:
| Heading | Uploaded January 2021 | Uploaded February 2021 |
| id | 1234 | 5678 |
| customer1@gmail.com | customer2@hotmail.co.uk | |
| phone_number | +447567890987 | +447567890987 |
...then Ometria will only ingest the following information:
- id = 5678
- email = customer2@hotmail.co.uk
And not the phone number.
This is to avoid duplicating phone numbers.
There is currently no way to move phone numbers across or assign a phone number to the most recent profile.
ISO 8601 format
Always send timestamps in ISO 8601 format with the timezone offset.
You can use this formula to quickly re-format your dates in Google Sheets before exporting to CSV.
In this example +04:00 is the offset, so four hours ahead of UTC:
=TEXT(A1,"yyyy-mm-ddThh:MM:ss+04:00")
Processing errors
If there is an issue when processing your CSV Ometria provides a link to download a list of these errors.
In order to download the link you must have the permission Can export data enabled.
See: User permissions
Example CSV file
Click the attachment below to download an example CSV file with all headers and four rows of data:
Comments
0 comments
Article is closed for comments.