# Imported Segments ### Overview Imported segments are used for two purposes: * You have a custom list of players that you build outside of Smartico and you want to make a segment from them * You want o update some properties in Smartico side with data that is not available in the normal integration flow between your platform and Smartico. ### How to Import a Segment To create an imported segment navigate to the Segments section, click on the "Create" button, and select the "Import Segment" option:
Once clicked It will open a window where you'll have to add a name for the segment and upload the already prepared CSV file. Please note that there is a special formatting required for the data in order for the import to be successful. You can also download a template of the CSV file.
Depending on a Label setting in the CSV file, you must have one or two mandatory columns - the *user\_ext\_id* and *core\_sm\_brand\_id.* In most cases the only mandatory column is user\_ext\_id. ***user\_ext\_id** -* is the user's external ID (without the brand indication in the beginning):


***core\_sm\_brand\_id -***** is** the brand ID for the brand of which the given user belongs. You can find this number in the user profile, the number standing before the user's external ID. In the example case is 31. Note that ***core\_sm\_brand\_id*** column is required in case you have multiple brand and non-unique user\_ext\_id across them. For example you have user with id 55 in brand A and user with same ID in brand B. In order for Smartico to understand which exactly user should be imported, you need to specify the ID of brand
Once prepared the CSV file should look like this:
After adding the file, a quick check will identify any errors in the uploaded user data. Once the check is completed, you can proceed with the import by clicking '"Continue".
Once you click "Continue", the file validation process will begin. During this phase, you can decide whether to proceed with the import or stop the process.
If you choose to proceed with importing the CSV file, the import process will begin, and the segment will be created. However, it will remain in the 'Importing' status until all users are successfully imported.
You can check the Import status inside the segment as well.
After the import is complete, you can view the successfully imported users under the 'Imported Users' tab. Any users who do not match existing usernames in the system will also be displayed under the 'Imported Users' tab.
### Updating other properties of user while importing segment You can add multiple columns in your CSV with names that correspond to name of properties in Smartico system. For example you have found that some deposits where not sent to Smartico and you want to update properties **acc\_last\_deposit\_date** and **acc\_last\_deposit\_amount**. You will need to prepare a file with additional columns exactly with these names and values for users that you want to update. For the format of values, please see table below. ### CSV Import – Guidelines & Rules When creating a **CSV Segment**, please follow these important rules and behaviors to ensure a successful upload: #### ✅ **File Requirements** * The file must be in **plain text CSV** format (comma-separated). * **Do not use quotation marks** in any fields. * Each property in the file must match a supported **data type** (see below). #### **📊 Supported Data Types** | Data Type | Description | | ------------------ | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | `string` | Text values | | `numeric` | Numbers only | | `enum` | Numeric enumeration values | | `boolean` | Use `true/false` or `1/0` | | `date` |
  1. Different date formats are supported such as:

\*below you can find the full list with supported date formats

2. Timestamp in milliseconds (e.g. 1704147742000). Use an Epoch converter to convert dates

| | `multicurrency` | Numeric values representing multi-currency fields | | `referenced value` | Numeric values referencing predefined lists or values | **Supported date formats:** | Date format | Example | | ---------------- | ------------------- | | YYYY-MM-DD | 2024-03-25 | | YYYY-MM-DD h:m:s | 2024-03-25 22:22:32 | | YYYY-MM-DD h:m | 2024-03-25 22:22 | | h:m:s YYYY-MM-DD | 22:22:32 2024-03-25 | | h:m YYYY-MM-DD | 22:22 2024-03-25 | | MM-DD-YYYY | 03-25-2024 | | MM-DD-YYYY h:m:s | 03-25-2024 22:22:53 | | MM-DD-YYYY h:m | 03-25-2024 22:22 | | h:m:s MM-DD-YYYY | 22:22:65 03-25-2024 | | h:m MM-DD-YYYY | 22:22 03-25-2024 | | YYYY/MM/DD | 2024/03/25 | | YYYY/MM/DD h:m:s | 2024/03/25 22:22:32 | | YYYY/MM/DD h:m | 2024/03/25 22:22 | | h:m:s YYYY/MM/DD | 22:22:32 2024/03/25 | | h:m YYYY/MM/DD | 22:22 2024/03/25 | | MM/DD/YYYY | 03/25/2024 | | MM/DD/YYYY h:m:s | 03/25/2024 22:22:22 | | MM/DD/YYYY h:m | 03/25/2024 22:22 | | h:m:s MM/DD/YYYY | 22:22:22 03/25/2024 | | h:m MM/DD/YYYY | 22:22 03/25/2024 | | YYYY.MM.DD | 2024.03.25 | | YYYY.MM.DD h:m:s | 2024.03.25 22:22:22 | | YYYY.MM.DD h:m | 2024.03.25 22:22 | | h:m:s YYYY.MM.DD | 22:22:22 2024.03.25 | | h:m YYYY.MM.DD | 22:22 2024.03.25 | | MM.DD.YYYY | 03.25.2024 | | MM.DD.YYYY h:m:s | 03.25.2024 22:22:22 | | MM.DD.YYYY h:m | 03.25.2024 22:22 | | h:m:s MM.DD.YYYY | 22:22:22 03.25.2024 | | h:m MM.DD.YYYY | 22:22 03.25.2024 | #### ⚙️ Upload & Validation Process 1. **Initial Validation:** * The system checks only the **first 20 users** in the CSV file. * If there’s an incorrect value in these rows, an error will specify the problematic column.
2. **Full Import:** * If invalid values are found **after** the first 20 users, those specific rows will be **skipped** and there is a message with the number of the skipped users.
#### 🚫 Unsupported Properties * Some user properties **cannot be updated via CSV import**. * These will appear **greyed out** in the UI and will be **skipped automatically** during the upload.
### Update points/gems/diamonds via CSV You can update points, gems, and diamonds for specific users via CSV.\ Using the **‘Import Segment’** feature in Segments, you can upload a CSV file and choose to add, deduct, or set values for user balances. The required columns in the CSV depend on what you want to update and the type of operation. Below are the supported columns: * `ach_points_balance` – updates current points (used for store, tournaments, mini-games) * `ach_points_ever` – updates level progress points (only for leveling) * `ach_points_leaderboard` – updates leaderboard ranking points * `ach_gems_balance` – updates current gems balance * `ach_diamonds_balance` – updates current diamonds balance * `operation_type` – required when updating any balance; * options: **add, deduct, set** {% hint style="warning" %} Note: If you're updating any currency column, the `operation_type` column is mandatory. {% endhint %}

BO: Update points/gems/diamonds via Import Segment

You can only apply one type of operation (add, deduct, or set) across all balances within a single row in the CSV. For example, if you’re updating both the points and gems balances in the same row and choose the add operation, both balances will be increased - you cannot add points and deduct gems in the same row. However, you can apply different operations per user. For instance, you can add points and gems for one user and deduct them for another within the same CSV file. Below is an example of a CSV file that deducts points, gems, and diamonds from specific users.
### Upload ‘User Markers’ via CSV You can **set** User Markers using a CSV import in Segments. This update also allows you to modify properties that accept array values. {% hint style="warning" %} I**mportant:** Uploading tags via CSV will completely overwrite any existing tags for a user. It is not possible to append new tags or remove specific ones using this method. If you need granular control over tags, please use the REST API. {% endhint %}

BO: User markers in User profile page

**Required CSV Column -** `core_tags` **Accepted Formats:** * **\[ ]** - Sets empty value * **\["text"]** - Sets a single user marker containing text. * **\["text", "text1"]** - Sets multiple text-based user markers. * **\["text", 10]** - Sets multiple user markers containing both text and numeric values. * **\[10]** - Sets a numeric user marker. * **\[10, 20]** - Sets multiple numeric user markers.

BO: Importing CSV segment with User markers

**⚠️ Important**: Updating markers via CSV import\ \ When updating markers using a CSV file, you can use either Excel / Google Sheets or a plain text editor (e.g. Notepad). However, there is an important difference in how these tools format the file. * **Excel / Google Sheets** automatically add the required quotation marks and escape characters, so the file usually passes validation without extra work. * **Plain text editors (like Notepad)** do not add this formatting for you. This means you must manually format the values correctly, otherwise the import will fail validation. Required format for marker values (example): ``` core_tags: "[""SMS TEST"", ""TEST ACCOUNT"", ""AFF TEAM"", ""CRM_TEAM_BASIC""]" ```