Users
Export your CRM data and import it into Kevel Audience. Please note that attributes imported through files typically take 4 hours to be available in the Segment Builder UI and in the Custom Attributes UI.
User data is in nature unique to each business, and hence we do not enforce any schema or perform any validation. However, to leverage some helpers in the Audience UI, we have a recommendation related to demographic user attributes.
- Import CRM data to use in activations;
- Complement the users' profile with their CRM data.
We automatically lowercase the following User IDs from the default ID Types list:
Additionally, if a transformation is required for any ID type before being imported (for example hashing plaintext emails), we also lowercase and trim the original ID before transforming it.
Import Data as User Attributes
When you import a file, each field will be added as a custom User Attribute in the User Profile. Some notes:
- The file must have at least one field which identifies the user (See User Identifiers). You can select which field contains the User ID and the associated User ID type.
- By default, the attribute merge strategy is set to merge. This means imported attributes will be combined with the existing attributes. Attributes not included in the file will remain unchanged in the User Profile.
- If you're importing a CSV file, all attributes will be treated as text values.
This restricts the ability to segment the user using numeric rules (e.g.,
numberOfOrders > 20won't work). As a workaround, you can apply castTo transformations to known numeric fields. - If you're importing a JSON-lines file, attributes will retain their original JSON value types (e.g., numbers, booleans, strings), allowing full segmentation flexibility.
Add Imported Attribute Names to Destinations' Activated Parameters
A common use case is to import CRM data in order to immediately activate it via a pre-configured Destination. To further facilitate this use case, a list of Destinations can be selected when creating a User data import and any attribute name found in the file will be automatically added as an Attribute Activated Parameter.
Once imported, details about added Activated Parameters can be found in the import results page.
In the "Added Activated parameters to destinations" section, we can see a summary of how many new Activated Parameters were added to each Destination, as well how many were already in the Destination, and finally any parameter that could not be added as it did not respect the naming restrictions.
In the "Fields breakdown" section we can see information about each Destination per attribute name, as well as any associated warning.
Some notes:
- You can enable the addition of imported attribute names as Activated Parameters for any Destination that supports Attribute-based Activated Parameters. Destinations that only support Segment-based Activated Parameters are not compatible with this feature.
- Some destinations have restrictions on the naming of the Activated Parameters. Any imported attribute name that does not respect these restrictions will not be added as an Activated Parameter. This information will be surfaced in the import results.
- For JSON files, attribute names to be added as Activated Parameters are detected from the first 100 lines. New attributes that appear afterward will be imported to the User Profile, but will not be automatically added to the selected destinations.
File and Folder Sources
We support importing CRM data from different Sources.
The following formats are supported:
E-goi Contacts Source
This third-party integration loads user data from an E-goi Contact List and imports it as attributes and user IDs. If the contact information contains an email, it will be transformed into sha256 representation and merged into any existing profiles. The E-goi contact ID is also imported and allows you to use the E-goi Destination, which will use that ID to attach tags to activated users.
To configure this import you should first select E-goi Contacts from the Source Type dropdown and then provide an E-goi API key with permissions to List All Contacts and Get My Account Info, as well as the List ID from which you want to download and import contact data. If you want to import only a subset of Contacts from that List that belong to a given Segment, you may fill in the Segment Id input. Otherwise, you may leave that field empty.
An API key can be created in your Integrations dashboard by choosing to Create a New Key and make sure the necessary permissions are selected:
The set of required permissions are the following:
- Get all contacts
- Get all contacts by segment
- Get my account info
The list id can be taken from your E-goi dashboard and should be the numeric ID before its title:
The segment id can be taken from you List view on the E-goi dashboard, and should correspond to the numeric value that prefixes the segment name:
Notice that the user import from this type of Source does not allow you to specify any transformations.
E-goi Attribute Mapping
This source imports a selected subset of E-goi Contact fields, mapping them either to user ID types or to user attributes. User attributes are mapped from the original E-goi fields using the format: egoi.account<ACCOUNT-ID>.list<LIST-ID>.<E-GOI-ATTRIBUTE>
Here, <ACCOUNT-ID> is the E-goi account ID linked to the provided API key and is automatically detected, so it does not need to be entered explicitly. <LIST-ID> is the List ID specified in the form, and <E-GOI-ATTRIBUTE> is the original Contact field being imported into Kevel Audience.
For example, importing the status field from an E-goi Contact might result in
egoi.account123.list321.status, if the API key used belongs to the E-goi account 123 and the user submitted 321 as
the List to import.
The following describes the fields that are consumed from the E-goi Contacts and how they are mapped into User Attributes:
| E-goi Contact Field | User ID or Attribute | Description |
|---|---|---|
contact_id | User ID: Internal E-goi User ID Type | The contact_id field is mapped into an internal user ID type whose main purpose is to be used by the E-goi Destination |
email | User ID: Email SHA256 | The E-goi plain-text email field, if available, hashed and mapped to a SHA256 User ID |
status | Attribute: egoi.account<ACCOUNT-ID>.list<LIST-ID>.status | The Contact status |
consent | Attribute: egoi.account<ACCOUNT-ID>.list<LIST-ID>.consent | The Contact consent |
email_status | Attribute: egoi.account<ACCOUNT-ID>.list<LIST-ID>.emailStatus | The Contact email status, if an email is available |
cellphone_status | Attribute: egoi.account<ACCOUNT-ID>.list<LIST-ID>.cellphoneStatus | The Contact cellphone status, if a cellphone is available |
phone_status | Attribute: egoi.account<ACCOUNT-ID>.list<LIST-ID>.phoneStatus | The Contact phone status, if a phone is available |
Please refer to E-goi Contact API documentation for more information about the existing Contact fields and their possible values.