Prepare your event implementation

​

Attach user tokens to events

• Attach a user token to each event so Algolia can link events to the same user over time.
• Persist anonymous user tokens and authenticated user tokens across sessions. This lets you retrieve user profiles at search time.

// Set a global user token
aa('setUserToken', 'user-1');

// Send a click event associated with "user-1"
aa('clickedObjectIDs', {
    index: 'movies',
    eventName: 'Added to favorite',
    objectIDs: ['movieID1'],
});

// Send a click event associated with "user-2"
aa('clickedObjectIDs', {
    userToken: 'user-2',
    index: 'movies',
    eventName: 'Added to favorite',
    objectIDs: ['movieID1'],
});

​

Event properties

• Link events to an existing index. When computing user profiles, Algolia ignores events whose objectID values don’t match records in the index.
• Events without a queryID still contribute to personalization. Algolia doesn’t show them in search analytics.
• You can send events in batches. Each event timestamp should reflect when you collected the event.

​

Send conversion events with subtypes

• When a user adds an item to their cart, send a conversion event with the addToCart subtype and matching objectData.
• When a user purchases an item, send a conversion event with the purchase subtype and matching objectData.

​

Check your events implementation

1. Visit your website and interact with it to generate events.
2. In the Algolia dashboard, check the Events debugger to confirm that Algolia receives your events.

​

See also

• Google Analytics BigQuery export