Skip to main content
Capturing real-time user interactions as events gives you actionable insights via click and conversion metrics, and they help you increase your customer engagement and conversions. Events are used to activate Algolia features and products like NeuralSearch, Dynamic Re-Ranking, Query Categorization, Recommend, and Personalization.

​
Before you begin

To follow this guide, you need to build both search results and category pages with one of these UI libraries: For other methods of collecting events, see Get started with events.

​
Manage the Insights library

InstantSearch loads the search-insights library for you from jsDelivr. You don’t need to install it or set it up yourself. If you’re using a Content Security Policy to protect your site and you want to let InstantSearch load search-insights for you, make sure to add https://cdn.jsdelivr.net in your list of trusted sources for JavaScript. 
script-src https://cdn.jsdelivr.net/
If you prefer hosting your own version of search-insights, you can add it to your project:
  1. Install the Insights client
  2. Initialize the Insights client (optional)
InstantSearch doesn’t load search-insights when it detects it on the page.

​
Enable events collection

You can enable the automatic collection of events from your InstantSearch apps in the Algolia dashboard (without coding), or when setting up your InstantSearch app (with coding). Enabling automatic events collection takes care of the following:
  • Add the search-insights library to your project and make it globally available as window.aa
  • Set an anonymous userToken for sending events to the Insights API and for search requests
  • Include the queryID parameter in the search response
  • Send default click and view events for your InstantSearch widgets
Go to the Events hub in the Algolia dashboard to check the default events arriving from your website or app. For more information, see Validate your events.

​
No code

  1. Go to the Algolia dashboard and select your Algolia application.
  2. On the left sidebar, select Data sources > Events > Settings.
  3. Click Enable automatic events collection.

​
Code

Enable the insights option: 
const search = instantsearch({
  searchClient,
  indexName: "YourIndexName",
  insights: true, 
});
// Add your InstantSearch widgets here
search.start();

​
Understand which events to track

You may want to send events that are not automatically captured by InstantSearch widgets. To understand which events you should send, think about the different steps a user takes through your website to perform desired actions. For example, a user might: Be presented with a list of real estate properties after performing a search from your homepage. Then click on a property to view more details. Finally, convert by contacting the realtor. In this example, you should track the following events:
  • Property Clicked by using the clickedObjectIDAfterSearch method.
  • Property Contacted by using the convertedObjectIDAfterSearch method.
A conversion is any user action that’s valuable to your business; a user purchasing from your store or subscribing to your newsletter are examples of common conversions. — GA4 About conversions

​
Keep track of query IDs

Conversion events are often triggered on pages that InstantSearch doesn’t cover, such as your item details pages. To relate the conversion events back to the search request made on your search results or category pages, you need to keep track of the query IDs across your pages.

​
Track conversion events

​
Using InstantSearch widgets

You can use the sendEvent function to send conversion events from your InstantSearch app. 
hits({
  templates: {
    item(hit, { html, components, sendEvent }) {
      return html`
        <h2>${components.Highlight({ attribute: "name", hit })}</h2>
        <p>${hit.description}</p>
        <button
          onClick="${() =>
            sendEvent("conversion", hit, "Item Added To Favorites");
          }"
        >
          Add to favorites
        </button>
      `;
    },
  },
});
Unlike click events, setting custom conversion events doesn’t prevent the custom click event from being sent.

​
On pages without InstantSearch widgets

Conversion events represent user actions that are important to the success of your business. For example:
JavaScript
// A user reached the bottom of an article page
window.aa("convertedObjectIDsAfterSearch", {
  eventName: "Article Read",
  index: "YourIndexName",
  queryID: "query-1",
  objectIDs: ["objectID-1"],
});
The window.aa object is the API client for the Insights API and is globally available if you enabled automatic events collection. The queryID parameter is used by Algolia to relate the event to a prior search. If the event is not directly related to a search, for example, it’s triggered on the homepage, use the convertedObjectIDs method instead.
JavaScript
// A user watched a video
window.aa("convertedObjectIDs", {
  eventName: "Video watched",
  index: "YourIndexName",
  objectIDs: ["objectID-1"],
});

​
Track click events

​
Override default click events

The hits and infiniteHits widgets expose a sendEvent function. Use it to send click events when users interact with your search results. 
hits({
  templates: {
    item(hit, { html, components, sendEvent }) {
      return html`
        <div onClick="${() => sendEvent("click", hit, "Item Clicked")}">
          <h2>${components.Highlight({ attribute: "name", hit })}</h2>
          <p>${hit.description}</p>
        </div>
      `;
    },
  },
});
You can set more events on specific parts of your template. In the following example, when users click the View more info button, two events are sent to the Insights API:
  • A click event with the eventName “Item More Info Clicked”.
  • A click event with the eventName “Item Clicked” (through event propagation).
hits({
  templates: {
    item(hit, { html, components, sendEvent }) {
      return html`
        <div onClick="${() => sendEvent("click", hit, "Item Clicked")}">
          <h2>${components.Highlight({ attribute: "name", hit })}</h2>
          <p>${hit.description}</p>
          <button
            onClick="${() => sendEvent("click", hit, "Item More Info Clicked")}"
          >
            View more info
          </button>
        </div>
      `;
    },
  },
});
To only send the most specific event per clicked element, you can use Event.stopPropagation in your event handler. 
hits({
  templates: {
    item(hit, { html, components, sendEvent }) {
      return html`
        <div onClick="${() => sendEvent("click", hit, "Item Clicked")}">
          <!-- ... -->
          <button
            onClick="${(event) => {
              event.stopPropagation(); 

              sendEvent("click", hit, "Item More Info Clicked");
            }}"
          >
            View more info
          </button>
        </div>
      `;
    },
  },
});
When InstantSearch captures a custom click event that you defined, it doesn’t send the default click event. In the following example, when users click the View more info button, only the “Item More Info Clicked” event is sent. 
hits({
  templates: {
    item(hit, { html, components, sendEvent }) {
      return html`
        <h2>${components.Highlight({ attribute: "name", hit })}</h2>
        <p>${hit.description}</p>
        <button
          onClick="${() => sendEvent("click", hit, "Item More Info Clicked")}"
        >
          View more info
        </button>
      `;
    },
  },
});

​
Track additional click events

For Algolia Recommend and Personalization, capture additional click events when users select individual items:
  • On your home page
  • From recommendations
To send click events with the Insights client, add the following code whenever a user clicks on an item—for example, on your homepage.
JavaScript
window.aa("clickedObjectIDs", {
  index: "YourIndexName",
  eventName: "Item Clicked",
  objectIDs: ["objectID-1"],
});

​
Optional: set up personalization

For effective personalization, you need to identify users across sessions. It’s best to use an identifier from your authentication system after users sign in. For more information, see User token. After getting the identifier from your system, set it as the authenticatedUserToken parameter.
JavaScript
// Get a unique, pseudonymous identifier for signed-in users
const authenticatedUserToken = getUserTokenAfterSignIn();
window.aa("setAuthenticatedUserToken", authenticatedUserToken);
If you can’t get persistent user identifiers from your system, you can store the anonymous user token in a cookie after obtaining user consent.
JavaScript
// If user consented
aa("init", {
  partial: true,
  useCookies: true,
});
If you don’t use persistent user identifiers, a new anonymous user token is generated on every page refresh. Personalization benefits from the same click and conversion events, plus it can use view events to enrich user profiles. Your InstantSearch components for the search results and category pages automatically collect view events. To capture additional view events, such as on your homepage, add this code:
JavaScript
window.aa("viewedObjectIDs", {
  index: "YourIndexName",
  eventName: "Items Viewed",
  objectIDs: ["objectID-1"],
});

​
Examples

​
Add events to a React InstantSearch application

⌘I