Send your event data from RudderStack to Algolia Insights.
Algolia is a popular site search and discovery platform. It helps businesses build and optimize their users’ product search and discovery experience, resulting in enhanced online engagement, increased conversion rates, and better user lifetime value.
RudderStack supports Algolia Insights as a destination to which you can seamlessly send your customer data.
Before configuring Algolia Insights as a destination in RudderStack, verify if the source platform is supported by Algolia by referring to the table below:
Assign a name to the destination and click Next. You should then see the following screen:
This section details the connection settings required to configure Algolia as a destination in RudderStack.
Enter your Algolia API Key and Application ID.
To get the Algolia API key and Application ID, go to your Algolia dashboard. Under the API Keys menu, copy the values under Application ID and Search-Only API Key.
Under Event Settings, you can add the Event Name and its corresponding Event Type. These are optional fields and can also be passed via the track call.
The event-eventType mapping passed via the track call will get a higher precedence over the mapping specified in the dashboard.
If the event-eventType mapping is not specified in the dashboard and these fields are not passed in the track call as well, then the event will be discarded.
Finally, click Next. Algolia will now be enabled as a destination in RudderStack.
The track call lets you send events related to your customers’ product usage. The required fields are event, eventType, index, and either objectIds or filters.
Note that the Event Name (event) and Event Type (eventType) can be mapped in the dashboard while configuring the destination. Note that the eventType value set in properties in the track call will have a higher precedence over the dashboard mapping.
In case you have already specified the mapping in the dashboard, you don’t need to send the same eventType in the track call.
To send a new event via track which is not specified in the dashboard, make sure you include the eventType inside the properties of the call. Otherwise, the event will be discarded.
The following table includes all track fields with their relative mapping to the Algolia fields:
RudderStack looks for these fields within the properties field of the event payload. userId or anonymousId is mapped to userToken in Algolia.
cookies, the cookies that are categorized as necessary are stored on your browser as they are as
for the working of basic functionalities of the website. We also use third-party cookies that
analyze and understand how you use this website. These cookies will be stored in your browser
consent. You also have the option to opt-out of these cookies. But opting out of some of these
have an effect on your browsing experience.
Necessary cookies are absolutely essential for the website to function properly. This
category only includes cookies that ensures basic functionalities and security
features of the website. These cookies do not store any personal information.
learn more about cookies and why we use them, visit our cookie
policy. We'll assume you're ok with this, but you can opt-out if you wish Cookie Settings.