Uploading audience data via CSV allows you to import structured first-party data (1PD) into Loop for segmentation and activation. This guide walks you through the process.
When to Use CSV Uploads
CSV uploads are ideal for importing CRM data, customer lists, or offline audience data for enrichment and future use. If you need to upload a one-time segmented file for immediate activation, refer to Custom Segment Upload.
Preparing Your CSV File
Before uploading, ensure your CSV file meets these requirements:
File Format: Must be CSV (.csv) with UTF-8 encoding.
Column Headers: Clearly labeled (e.g.,
email
,device_id
, etc.).Data Types Supported: Emails, MAIDs, phone numbers, national IDs, and custom attributes.
No Duplicates: Ensure unique identifiers per row.
Data Formatting:
Emails: Must be all lowercase (e.g.,
[email protected]
).NID: Only numbers, no special characters (e.g.,
34848988
).Phone Numbers: Format as
(country code)(area code without 0)(number)
(e.g.,541151190123
).Hashed Data: Can be in SHA-256 or SHA-512. If uploaded in plain text, it will be automatically hashed in SHA-256.
How to Upload a CSV to Loop
Step 1: Start the Upload Process
Navigate to Sources in the left-side menu.
Click Create New.
Select Upload a File.
Step 2: Name and Describe Your File
Enter a name and description to help you identify the data source later.
Click Next.
Step 3: Configure Upload Settings
Click Upload a File and select your CSV.
Choose your field separator (
,
,;
,:
,|
, orTab
).Select the country of the data.
Specify whether the data source is from a CRM or an app.
Please upload CRM files (that contain PII data such as emails, phones or IDs) separately from files with Mobile Advertising IDs (MAIDs).
Drag your file into the upload section or click to browse and select it from your computer.
Step 4: Map Your Data Fields
Loop will parse the first rows of the file and display the detected columns.
Assign each column to Loop’s expected data fields.
Verify that all required fields are correctly mapped.
Click Next to proceed.
Step 5: Submit and Monitor Processing
Click Create to begin processing.
Supported Fields and Data Types
Fields for CRM files or email, phone or ID lists
Field Name | Description | Variable Type | Possible Values |
| Unique identifier for a user’s device. Required | String | UUID format ( |
| Partner-assigned external ID for web cookies | String | Custom value |
| User identifier via email | String | Plain text (lowercase) or SHA-256/SHA-512 hashed |
| User identifier via phone number | String | Numeric, formatted as Plain or SHA-256/SHA-512 hashed |
| National identifier (e.g., DNI, CI, CC) | String | Numeric only, no special characters. Plain or SHA-256/SHA-512 hashed |
Retargetly ID | A mapping to the user ID assigned by Retargetly | String | Plain text |
External ID | A mapping to a previously defined ID (e.g. an own platform ID) | String | Plain text |
Mobile phone/APP files
Field name | Description | Variable type | Possible values |
Android | Unique identifier for a user’s Android device. Required | String | UUID format ( |
iOS | Unique identifier for a user’s Android device. Required | String | UUID format ( |
Best Practices for CSV Uploads
✅ Use hashed emails (SHA-256) for privacy compliance.
✅ Regularly update and clean your lists to maintain accuracy.
✅ Ensure data fields are properly formatted before upload.