Import CSV files
Overview
You can use a CSV (comma separated values) file to import users and accounts or events into your Intempt account.
Before you import
Set up your import files. Properly setting up your files helps you avoid import errors.
Set up your import file
The import file must:
- Be a .csv file.
- Include a header row in which each column header represents a column in the dataset. The column headers can be organized in any order without affecting the import. To join your CSV data to Intempt event, one of the columns in the file must match Intempt event attribute for the event you want to join your data with.
- Contain less than 500 columns.
- Be UTF-8 encoded if foreign language characters are included.
- Ensure all cell values containing commas are enclosed in quotes.
A CSV file with Users data only must meet the following criteria:
- At least one field matches theΒ user unique identifier - UserId, Email, Phone
A CSV file with Accounts data only must meet the following criteria:
- At least one field matches theΒ account unique identifier - AccountId, Company name.
A CSV file with User and Accounts data must meet the following criteria:
- At least one field matches theΒ account unique identifier - AccountId, Company name. and one field matches theΒ user unique identifier - UserId, Email, Phone
A CSV file with Events data only must meet the following criteria:
- At least one field matches theΒ one event timestamp and account or user unique identifier - AccountId, UserId.
Import users and/or accounts
Once you've set up your file for import:
- Click Import in the top right corner of the βListβ page.
- On the Imports page, click Start an import
- Choose the type of data in your file (Users, Accounts, or both), then click Next.
- Drag and drop your file or select it from your computer. Name your file if necessary, then click Next.
- On the Map Columns in Your File to Intempt Attributes screen, Intempt will automatically map the columns in your file to the relevant user or account attributes based on the header name, header language, and property name. Depending on whether you selected Users, Accounts, or both, the attribute options will be:
- If βUsersβ selected we will only display user attributes, if βAccountsβ only account attributes, if both - we will display users and account attributes choice.
The Mapping Guide displays the attributes required to create and/or update the user and accounts. If your file is missing any of the attributes needed to import the file, you should fix your import file and restart the import to avoid errors.
- If there are no errors, a success checkmark will appear in the Mapped column.
- If errors are detected, an alert icon will be shown in the Mapped column.
- If any columns were mapped to the wrong user or account attributes, click the dropdown menu in the Import As column and select the correct attribute.
If any columns don't map to an existing attribute, or mapped to the wrong attribute, click the dropdown menu in the Intempt field column. In the dropdown menu, you can do one of the following:
- Map the column to an existing attribute: Search for and select an existing property.
- Set up a new custom attribute: Click Create New Attribute and define the attribute in the right panel. The data in that column will be mapped to this new custom attribute.
Attribute Creation Requirements
Attribute creation requires the fields below:
Attribute's field | Description | Required |
---|---|---|
Attribute type | Determines if it is a user or account. Auto-selected and non-editable, based on the incoming attribute type. | Yes |
Name | The unique identifier that is used internally by Intempt to reference the attribute. | Yes |
Display name | The attribute's name, as shown in the user interface, is typically more readable than the name itself. | No |
Description | A brief explanation of the attribute's purpose and how it should be used. | No |
Example | A representative value or instance to illustrate how the attribute might be populated. | No |
Visibility | This defines whether the attribute should be visible for targeting (e.g., appear in the segment, event editor, etc.). | Yes |
Object type | The attribute's data type (e.g., String, Integer, Boolean, Date, etc.). | Yes |
Merge strategy | Defines how an attribute should be updated once new data is received. | Yes |
Merge strategy
You can define rules for updating attributes once new data is pushed to the attribute. For example, the value of the user's "Location" attribute changed from that of the United States to that of the United Kingdom.
First used value βIf both user profiles have a value, the oldest value (with the oldest timestamp) is used for the attribute. This is important when tracking the user's first option and relevant when tracking the user's original location.
Most recent value - keeps the value that was the last set. We recommend using this option most frequently as it represents the most up-to-date user's or account information. Any data item submitted most recently will be used as an attribute value for this merge strategy.
Most frequently used value - the value of the attribute used most often. Consider this example for an email address - the user submitted [email protected] 6 times and [email protected] 2 times. Intempt will use the email address that was used most frequently [email protected] (user might use multiple emails to sign up).
Finalizing the Import
- Once all columns are correctly mapped, click Import
You can view the import details on the Import page after completion.
Import events
Events allow you to capture user behavior and use it within Intempt. An import can create a new event or update data in an existing event.
Once you've set up your file for import:
- Click Import in the top right corner of the βEventβ page.
- On the Imports page, click Start an import
- Select whether you want to import a new event or add data to an existing event, then click Next.
- Name the new event or select an existing event from the dropdown list.
- Drag and drop your file or select it from your computer. Name your file if necessary, then click Next.
On the Map Columns in Your File to Intempt Attributes screen, Intempt will automatically map the columns in your file to the appropriate user, account, or event attributes based on the header name, header language, and property name.
The Mapping Guide displays the attributes required to create or update events. If any required attributes are missing, fix your import file and restart the import to avoid errors.
- If there are no errors, a success checkmark will appear in the Mapped column.
- If errors are detected, an alert icon will be shown in the Mapped column.
- If any columns were mapped to the wrong user, event, or account attributes, click the dropdown menu in the Import As column and select the correct attribute.
If any columns don't map to an existing attribute, or mapped to the wrong attribute, click the dropdown menu in the Intempt field column. In the dropdown menu, you can do one of the following:
- Map the column to an existing attribute: Search for and select an existing property.
- Only for new eventsSet up a new custom attribute: Click Create New Attribute and define the attribute in the right panel. The data in that column will be mapped to this new custom attribute.
Finalizing the Import
- Once all columns are correctly mapped, click Import.
You can view the import details on the Import page after completion.
Updated 26 days ago