Guides
/
Personalization
/
Advanced Personalization
/
Configure personalization
/
Prerequisites
Jan 13, 2025
Consider requirements and limits
On this page
A healthy Advanced Personalization setup requires familiarity with its requirements and limitations.
Your Advanced Personalization configuration can be modified up to five times per day and must adhere to the following limits on:
- Indices
- Affinities
- Events.
Indices
- You can personalize as many of your indices as you like.
- The maximum number of indices you can create depends on your plan.
Affinities
Affinities are attributes that you want to use to personalize search results.
- You must select at least one and no more than 20 for each index you personalize.
- Some attribute names are reserved and can’t be used as affinities:
app_id
,client_id
,session_id
,updated_at
,__index_level_0__
,objectID
,^_ds_.*
.
Affinity values
- Each attribute must have no more than 100 unique values.
- Some attribute values are reserved and will be ignored:
not-set
,{}
,Unknown
,unknown
,***
,None
,none
,N/A
,n/a
,NULL
,null
. - When using nested attributes there must be no more than 250 levels of nesting. If an attribute contains more than 250 levels of nesting, scores will not be generated for that affinity.
Events
To be used for generating user profiles, the events you send to Insights must adhere to the limits detailed below.
- Only valid events can be used to generate user profiles.
- You must include the user token in each event. The user token must be the same as the one used in your search queries.
- There must be at least one returning user in your events. A returning user is a user with more than one session in the last 30 days.
- When configuring your events, you must select at least 1 view details event per index. For optimal performance, send add to cart and purchase events too.
- You can’t send more than 10 million events per day. If you need to exceed this limit, contact the Algolia support team.
Did you find this page helpful?