Requirements and limits

• 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

• Select between 1 and 20 affinities for each index you personalize.
• The following attribute names are reserved for Algolia and can’t be used as affinities:
  • app_id
  • client_id
  • session_id
  • updated_at
  • __index_level_0__
  • objectID
  • ^_ds_.*

​

Affinity values

• Each attribute can have up to 100 unique values.
• The following attribute values are reserved and are ignored:
  • not-set
  • {}
  • Unknown
  • unknown
  • ***
  • “ (empty)
  • None
  • none
  • N/A
  • n/a
  • NULL
  • null
• When using nested attributes there can be up to 250 levels of nesting. If an attribute contains more than 250 levels of nesting, scores won’t be generated for that affinity.

​

Events

• 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.
• Real-time personalization requires at least 3 events per user to generate affinities.