How user profiles are built
Send accurate events to build relevant user profiles. Algolia requires events that describe how users interact with your app. For example, an online bookstore might track when users:- Click a specific book in a listing.
- View the genre or author on the book’s details page.
- Add the book to their cart.
- Buy the book.
This feature isn’t available on every plan.
Refer to your pricing plan to see if it’s included.
Schema
A user profile is represented in JSON format and includes a unique identifier for the user and their preferences (affinities).JSON
Properties
| Name | Type | Description |
|---|---|---|
userID | string | A unique string that identifies and tracks users across various systems. |
lastUpdatedAt | string | Date at which the user profile was last updated. |
affinities | array of affinities | Properties generated by Algolia’s Advanced Personalization feature to provide insights into the user’s preferences and interests. They’re used to personalize the user’s experience on your website or app. |
Affinity
| Name | Type | Description |
|---|---|---|
name | string | Name of the affinity. |
value | string | Value of the affinity. |
indices | array of strings | Names of the Algolia indices associated with the affinity. |
score | number | Strength of the user’s preference for that affinity. Each affinity has a score ranging from 1 to 20. A higher score signifies a stronger affinity. |
lastUpdatedAt | timestamp | Date of last update to this affinity. |