Algolia

introduction algolia is a powerful search and discovery platform that helps businesses deliver fast, relevant, and personalized search experiences on websites and apps it provides a hosted search api that allows developers to build lightning fast search functionality with features like typo tolerance, filters, facets, and ranking customization —so teams can optimize user experiences, improve retention, and drive growth getting started to properly use chord's algolia destination, both your algolia specific application id and api key must be provided for authentication application id your algolia application id can be found on the overview page or can be found alongside your algolia api key in your account settings api key when configuring chord's algolia destination, it is important to use your account write api key to find this key, follow the guidelines here log into your brand's algolia account and click on the settings link on the bottom left hand corner of your dashboard on the settings page, select api keys under the team and access section copy the key titled write api key index, query id & object ids chord's algolia destination automatically extracts and maps key algolia insights attributes from your analytics events index the algolia destination identifies the https //www algolia com/doc/glossary/#index from event properties using this fallback hierarchy properties index (preferred) properties search index (fallback) "undefined index" (default if neither exists) query id https //www algolia com/doc/guides/sending events/concepts/event types/#what is the query id are extracted from properties query id and are essential for attributing user interactions back to specific search queries this value should come directly from algolia's search api response object ids object ids are intelligently mapped from your product data single product events uses properties product id → becomes \["product id"] multi product events maps from properties products\[] product id → becomes array of all product ids example event structure { "type" "track", "event" "product clicked", "userid" "user123", "properties" { "query id" "7891011121314151617", "index" "products", "product id" "sku 001", "search index" "products", "position" 3, "search query" "coffee beans" }, "timestamp" "2025 01 15t10 30 00 000z" the algolia destination only processes supported e commerce events ( product clicked , product viewed , product added , order completed , product list filtered ) and requires that your product id values exactly match the objectid field in your algolia index for proper attribution connecting to the algolia cdp destination log into the chord data platform navigate to the cdp click the "add" button next to destinations select algolia from the destination catalog enter in the destination name, your algolia application id and your algolia api key click "create" to connect chord events relevant for destination not all chord tracking events are used downstream in your configured destinations the most relevant and important events in the chord tracking plan are mapped within the cdp destination, relayed and then ingested in the destination only track events are used downstream by algolia the chord tracking plan events used by the https //www algolia com/doc/guides/sending events/concepts/event types are chord tracking event algolia event type algolia event subtype order completed conversion purchase product added conversion addtocart product clicked click all other events (i e product viewed, product list filtered) view before connecting destinations in the chord cdp, please verify with all destination owners that all non chord cdp configured destinations are disabled running external destinations alongside configured chord cdp destinations can result in duplicate events downstream