Integrations
      Back to home
      1. Help Center
      2. ELT+ | Technical User Documentation
      3. Integrations

      Integration: Algolia

      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.

      Key Topics

      Click on the links below to take you to the section where you can learn more about this Integration

      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:

      • Pro (V1 and V2)

      NOTE: You are considered V2 if...

      • Your account says Pro V2 in the Daasity App

      Not sure? Reach out to Support@Daasity.com

      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:

      Entity Relationship Diagram (ERD)

      The embedded diagram houses the ERD for the Daasity Algolia integration illustrating the different tables and keys to join across tables. Hover over the embedded diagram to reveal controls to zoom and scroll.

      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

      • 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

      Related Resources