You want to provide relevant search and discovery results and doing so heavily relies on data in your Algolia account to be accurate and fresh. By automatically indexing records and events from your data warehouse into Algolia, you no longer need to worry about data consistency because data is no longer flowing in from multiple sources in different formats, and you can focus on building world-class customer experiences.
Go to the Destinations overview page and click the Add destination
button. Select Algolia and click Continue. You can then authenticate Hightouch to Algolia with an API key.
Enter the following required fields into Hightouch:
Once you've set up your Algolia destination and have a model to pull
data from, you can set up your sync configuration to begin syncing data. Go to the Syncs overview
page and click the Add sync button to begin. Then, select the relevant model and
the Algolia destination you want to sync to.
When syncing insight events to Algolia, you must provide the following fields:
Event Name: Name of the event. Typically the action performed.
Event Type: Type of the event. The allowed values are "click", "conversion", or "view".
Index: Name of the targeted index.
User Token: A user identifier. Depending if the user is logged-in or not, several strategies can be used from a sessionId to another technical identifier. You should always send pseudonymous or anonymous userTokens.
YOu can also provide these optional fields:
Timestamp: Time of the event expressed in milliseconds since the Unix epoch.
Query ID: Algolia queryID. This is required when an event is tied to a search.
Object IDs: An array of index objectIDs. Limited to 20 objects. An event can't have both objectIDs and filters at the same time.
Filters: An array of filters. Limited to 10 filters. An event can't have both objectIDs and filters at the same time.
Positions: Position of the click in the list of Algolia search results. This field is required if a queryID is provided. One position must be provided for each objectID.
When an event is tied to an Algolia search, it must also provide a queryID. If that event is a click, their absolute positions should also be passed. Consult Algolia's documentation for more information on event fields.
To date, our customers haven't experienced any errors while using this destination. If you run into any issues, please don't hesitate to . We're here to help.
Hightouch provides complete visibility into the API calls made during each of your sync runs. We recommend reading our article on debugging tips and tricks to learn more.