Integration Specifications

This article will help you learn about how Daasity replicates data from Algolia, limitations to the data we can extract and where the data is stored in the Algolia schema

Integration Overview

Algolia helps businesses across industries quickly create relevant, scalable, and lightning-fast Search and Discovery experiences.

The Daasity Algolia integration returns data related to the performance of Site Search which allows merchants to understand what are the most important and trending terms that customers querying on the merchant site. This information is important because customers typically search for what is not easily found upon their visit. Algolia users may reveal product and merchandising opportunities that will lead to increased revenue.

Integration Availability

This integration is available for:

• Enterprise

API Endpoints

The Daasity Algolia extractor is built based on this Algolia API Documentation. The following endpoint is used by Daasity to replicate data from Algolia:

• Top Searches

Entity Relationship Diagram (ERD)

Click here to view the ERD for the Daasity Algolia integration illustrating the different tables and keys to join across tables.

Algolia Schema

The Daasity Algolia extractor creates these tables using the endpoints and replication methods listed. The data is mapped from source API endpoint to the table based on the mapping logic outlined in each table.

• Searches

Unexpected error with integration lucid: Integration is not installed on this space

Searches

• Endpoint: Top Searches

• Update Method: UPSERT

• Table Name: [algolia.searches]

JSON Element	Database Column
MD5(search + ':' + event_at)	search_id
search	search_term
startDate	event_at
count	searches
nbHits	hits
clickCount	clicks
conversionCount	conversions
averageClickPosition	average_click_position
Daasity: MD5(search + event_at)	__sync_key
Daasity: account_id	_account_id
Daasity: timestamp when loaded into DB	__synced_at