Algolia connection
Overview overview
Use the Algolia destination connection to send ۶Ƶ Experience Platform audiences to Algolia for personalized search and recommendations. Before you can use the Algolia destination connector, you must first set up the Algolia User Profiles source connector. During the source connector setup tutorial, you will create the Algolia User Token identity. This identity is required for mapping when you configure the destination connector.
This tutorial provides steps to create an Algolia destination connection and dataflow using the ۶Ƶ Experience Platform user interface.
Use cases use-cases
To help you better understand how and when you should use the Algolia destination, here are sample use cases that ۶Ƶ Experience Platform customers can solve by using this destination.
Personalization consistency personalization-consistency
Use this destination connector to deliver a consistent personalization across your site from home page to search.
For example, as a marketer, you might want to build rich audiences in ۶Ƶ Experience Platform from multiple user data sources, including Algolia. You can use the Algolia destination connector to share the audiences for targeting strategies, leading to a boost in campaign personalization and conversion.
To implement this use case, you must use both the Algolia User Profiles source and Algolia destination connectors.
You would start by importing your existing Algolia user profiles into ۶Ƶ Experience Platform Real-Time CDP and other sources to begin creating rich audiences with the source connector. Marketers would create audiences using the profile data that can be sent to Algolia for search and recommendation personalization.
Then, use the corresponding Algolia User Profiles source connector to ingest and augment customer profiles back into Real-Time CDP.
Prerequisites prerequisites
-
To connect to the destination, you need the View Destinations and Manage Destinations, Activate Destinations, View Profiles, and View Segments access control permissions. Read the access control overview or contact your product administrator to obtain the required permissions.
-
To export identities, you need the View Identity Graph access control permission.
Supported identities supported-identities
Algolia supports the activation of identities described in the table below. Learn more about identities.
AlgoliaUserToken source identity to the userToken in the Algolia platform.Supported audiences supported-audiences
This section describes which type of audiences you can export to this destination.
Export type and frequency export-type-frequency
Refer to the table below for information about the destination export type and frequency.
Connect to the destination connect
To connect to this destination, follow the steps described in the destination configuration tutorial. In the destination configuration workflow, fill in the fields listed in the two sections below.
Authenticate to destination authenticate
To authenticate to the destination, fill in the required fields and select Connect to destination.
- Application ID: The Algolia application ID is a unique identifier assigned to your Algolia account.
- API Key: The Algolia API Key is a credential used to authenticate and authorize API requests to Algolia’s search and indexing services.
For more information on these credentials, see the Algolia .
Fill in destination details
To configure details for the destination, fill in the required and optional fields below. An asterisk next to a field in the UI indicates that the field is required.
- Name: Fill in the preferred name for this destination.
- Description: Short explanation of the destination’s purpose.
- Region: The options are US or EU. Select the region where the customer data is stored.
Enable alerts enable-alerts
You can enable alerts to receive notifications on the status of the dataflow to your destination. Select an alert from the list to subscribe to receive notifications on the status of your dataflow. For more information on alerts, see the guide on subscribing to destinations alerts using the UI.
When you are finished providing details for your destination connection, select Next.
Activate audiences to this destination activate
- To activate data, you need the View Destinations, Activate Destinations, View Profiles, and View Segments access control permissions. Read the access control overview or contact your product administrator to obtain the required permissions.
- To export identities, you need the View Identity Graph access control permission.
Read Activate profiles and audiences to streaming audience export destinations for instructions on activating audiences to this destination.
Map attributes and identities mapping-attributes-identities
During the Mapping step, you must map the AlgoliaUserToken source identity to the userId target identity.
Validate data export exported-data
To verify if audiences have been exported to the user profiles successfully, check your Algolia dashboard and navigate to Advanced Personalization and click on User Inspector. Find a user profile associated with the exported ۶Ƶ Experience Platform audience and search for it in the User Inspector. You will see the audience ID in the segment section.
Data usage and governance data-usage-governance
All ۶Ƶ Experience Platform destinations are compliant with data usage policies when handling your data. For detailed information on how ۶Ƶ Experience Platform enforces data governance, read the Data Governance overview.
Additional resources additional-resources
Refer to the following Algolia documentation for more information:
Next steps next-steps
By following this tutorial, you have successfully created a dataflow to export audiences from Experience Platform to your Algolia application. For more information about the Algolia platform, see the .