After importing profiles to Synerise, you can direct various actions towards them, such as:
- Sending messages (email, SMS, mobile push, web push, in-app messages).
- Creating predictions.
- Creating query rules in AI search engine.
Requirements
- You need user permissions that grant you access to Simple Imports or/and Automation
- Prepare a file that contains one of the profile identifiers. This is the only required column, the rest is optional.
- Spaces and special characters in the column headers are not allowed.
.csvfiles must be UTF-8 encoded- Maximum file size: 200 MB.
Profile identifiers
The file must contain at least one of the following identifiers. The list contains recommended column names. If you use different names, you can map or transform the data during the import.
| Identifier | Unique emails | Non-unique emails | Comments |
|---|---|---|---|
email |
+ | - | Pay attention to the correct format of emails. Otherwise, your import will fail. |
uuid |
+ | + | |
customId |
+ | + | |
clientId |
+ | + | Can be used only when updating an existing profile. |
If your workspace uses non-unique emails:
emailandphonearen't profile identifiers. UsecustomId,uuid, orclientId.- To create a new profile, use
customIdoruuid. emailisn't listed among the required columns in data transformation goals and in the Import Profiles node.- Emails are sent to the address stored in the attribute selected in Settings > Identifiers in the Email address field. The predefined
emailattribute isn't used. If your file contains anemailcolumn, save its values to the attribute selected in Settings > Identifiers: map the column to this attribute during the import, or rename the column in a data transformation with the Rename columns node. In both cases, use the source name of the attribute, not its display name. If you use the display name, a new attribute is created.
Tips for preparing a CSV file
- Recommended file metacharacters:
- A character that splits columns (delimiter):
, - A character that is used to contain the text (quotation mark):
" - A character (escape character) that changes the default interpretation of a sign or string followed by the escape character:
\
- A character that splits columns (delimiter):
- Attributes (column names) and values are case-sensitive (firstname and Firstname are not the same)
- If you will use Automation Hub as a method of import, below you can find the instructions how to transform the optional default profile properties:
| Profile's property | Required name | Accepted values | Other comments |
|---|---|---|---|
| Profile's first name | firstName |
A string | n/a |
| Profile's last name | lastName |
A string | n/a |
| Date of birth in the profile | birthDate |
the yyyy-mm-dd format, months must be zero-padded (for example, May is 05) |
For example, 1999-09-09 |
| Profile's company | company |
A string | n/a |
| Profile's city of residence | city |
A string | n/a |
| Profile's street address | address |
A string | n/a |
| Profile's zip code | zipCode |
A string | n/a |
| Profile's province of residence | province |
A string | n/a |
| Code of profile's country of residence in accordance with the ISO 3166 format | countryCode |
A string | n/a |
| Profile's gender | sex |
FEMALE, MALE, OTHER, NOT_SPECIFIED |
These values are transformed during import as follows: - NOT SPECIFIED and OTHER to 0 - FEMALE to 1 - MALE to 2 These values will be presented as such in a profile's card |
| Marketing agreements of the profile | - for email: agreements.email - for web push: agreements.webPush - for mobile push: agreements.push - for SMS: agreements.sms - for WhatsApp texts: agreements.whatsapp |
- for email: true, false, True, False, 1 (true), O (false) - for web push: true, false - for mobile push: true, false - for SMS: true, false; - for WhatsApp texts: true, false |
If you use non-unique emails, email marketing agreement is saved as a custom attribute which takes the following values: enabled, disabled |
| Tags assigned to a profile | tags |
An array of strings | n/a |
| A profile's phone number | phone |
The phone number can contain digits, spaces, and an optional + at the beginning. |
For example: +48111222333; +48 111 222 333 |
Example
For more details about parameters and their accepted formats, click here.
Import modes
When updating profiles, you can select one of these modes:
- Bulk imports:
This is the default mode, recommended for most situations. Use Bulk imports for importing large data loads, backfills, migrations, and recurring imports that do not require priority over current profile activity. - Ongoing updates:
Use Ongoing updates for small, time-sensitive updates that should be processed ahead of bulk imports. Platform imports and API requests submitted as Ongoing updates share processing capacity. Sending a large import through this mode can delay profile updates submitted through those API endpoints that work as ongoing updates.
Imports created before Sep 23, 2026 are treated as ongoing updates. You can change the setting manually.
WARNING: Update order is preserved within one processing mode, but not across modes. Keep order-dependent updates in the same mode.
Procedure
Selecting the file for import
In this part of the process, you will upload a file from your device.
- Go to
Data Modeling Hub > Imports > New import.
- As the data type for import, select Profiles.
- As the import method, select one of the following options:
- Import a local file - To import a single
.csvor.jsonfile to Synerise. - Import in Automation - To import a .
csv,.json,.jsonl, and.xmlfiles and execute periodical imports.
- Import a local file - To import a single
- Upload a
.csvor.jsonfile by using the + Upload file or drop one here field. - If you uploaded a CSV file, optionally, you can customize the file metacharacters by clicking the arrow down icon.
- From the Delimiter dropdown, select the character that marks the end of a column.
- From the Quotation mark dropdown list, select the characters that contain the text or data type.
- From the Escape character dropdown lists, select the character which changes the default interpretation of a character or a string followed by the escape character.
- If you uploaded a JSON file, optionally, in the JSON path field, enter a JSONPath expression that points to the data you want to import (for example,
$.data.items[*]).- The expression must start with the
$character. - Each element that the expression returns is imported as a separate row. The rest of the file is discarded.
- If you leave the field empty, the entire file is imported.
- The expression must start with the
- Optionally, to check the data, click Preview data. If you entered a JSON path, the preview shows only the data at this path. If the path is invalid, the Can't process a file error is displayed. If the path doesn't point to any data in the file, the preview is empty.
- To proceed to the next step, click the Next button.
Mapping the columns with parameters in Synerise
In this part of the process, you will connect the columns from the file with their counterparts (the existing parameters) in Synerise. This way, you will point which parameters in Synerise will contain the profile information from the imported file.
You can also exclude parameters from the import. During the mapping process, you can't add new columns to the imported file.
On the user interface, you will be presented with two columns - the left column displays the names of the columns from the imported file, the other contains dropdown lists with the parameters available in Synerise. The dropdown lists indicate required parameters for a successful import.
- Next to the file column name, from the dropdown list, select the corresponding parameter in Synerise. Perform this step for all columns in your file.
- To exclude a parameter from import, next to the column name, click this icon:

Result: The icon changes to
Launching import
After steps described above you'll be redirected to the mapping summary.
- Verify that the mapping is correct.
- If you want to change the import mode, click Advanced settings and select the mode.
To learn about the modes, see Import modes. - To launch the import, click Run import.
- From How are you going to deliver the file?, select the method of delivering the file.
- Click Go to import template.
- Define the settings of the Scheduled Run node.
- Depending on the method of delivering the file, configure the settings of the node that you selected as the import method:
- If the data requires modification, configure the settings of the "Data Transformation Studio" node. If you have prepared a transformation for the data structure of the imported file, click Templates library and select it. If not, create it from scratch.
You can remove this node if your data doesn't require transformation. - In the Import profiles node, under Advanced settings, you can change the import mode.
To learn more about the modes, see "Import modes". - If your workflow is ready, click Save & Run.
Reserved parameters
You are not allowed to create the following parameters while mapping. These are default parameters available in Synerise (they already exist in Synerise).
| address | agreements | anonymous | anonymous_type |
| avatarUrl | birthdate | birthDate | businessProfileId |
| city | clientId | company | confirmation_hash |
| confirmed | countryCode | country_id | created |
| customId | custom_identify | deletedAt | displayname |
| displayName | external_avatar_url | facebookId | |
| firstname | firstName | geo_loc_as | geo_loc_city |
| geo_loc_country | geo_loc_country_code | geo_loc_isp | geo_loc_lat |
| geo_loc_lon | geo_loc_org | geo_loc_query | geo_loc_region |
| geo_loc_region_name | geo_loc_status | geo_loc_timezone | geo_loc_zip |
| ip | lastname | lastName | last_activity_date |
| newsletter_agreement | ownerId | phone | province |
| receive_btooth_messages | receive_push_messages | receive_rfid_messages | receive_smses |
| receive_webpush_messages | receive_wifi_messages | sex | source |
| tags | time | type | updated |
| uuid | zipCode |