UserReadOut

Unique identifier for a user who has signed in. user_id can be in any format (e.g. users' email, internal user UUID or serial ID). The only restriction is that the first character must not be an underline _. Miso will use this id to cross-reference your User records with your Interaction records.

Age of the user. We will internally convert it to year of birth.

City or zipcode the user is based in.

Country the user is based in.

The date the user’s account was created as an ISO-8601 date or datetime string.

Dictionary of custom attributes about the user. As with the Product API, you can specify attributes specific to your business in a {"KEY" : VALUE} format, where KEY must be a string, and VALUE can be:

• a string or an array of strings

• a number or an array of numbers

• an array of objects

• a bool

• null

• Example:

{
    "custom_attributes": {
        "acquisition_channel": "Facebook Campaign 2020",
        "declared_interests": ["Drama", "Romance"]
    }
}

These custom attributes types must be consistent across all User records in your data set. Records with inconsistent types will fail to be inserted.

Text description of the user. This can be the user's own bio or the internal notes about the user. If available, Miso will analyze this description to better profile a user.

The user's gender.

Group or Account ID from your CRM. This is useful in B2B scenarios. For example, you can use group_id to associate a user with their company or account. We will use this information to infer the user's interests and fine-tune their personalization and search results. For example, users from the same group might have similar interests on the site, and we can improve their user experience accordingly

The user's full name.

URL to the profile image of the user.

State the user is based in.

The date the user’s account was updated as an ISO-8601 date or datetime string.