This tutorial guides you through ingesting data from your Algolia User Profiles account into Adobe Experience Platform using the user interface.
Before you begin, make sure you’ve completed the prerequisites outlined in the Algolia User Profiles overview.
This tutorial assumes familiarity with the following Experience Platform components:
Experience Data Model (XDM) System: The standardized framework Experience Platform uses to organize customer experience data.
Real-Time Customer Profile: A unified, real-time customer profile based on aggregated data from multiple sources.
Sources: Ingest data from various sources and use Experience Platform services to structure, label, and enhance the data.
To connect Algolia to Adobe Experience Platform, provide the following credentials:
Credential | Description |
---|---|
Application ID | The unique identifier assigned to your Algolia account. |
API Key | The credential for authenticating and authorizing API requests to Algolia’s services. |
For more information, refer to the Algolia authentication documentation.
In the Experience Platform UI, select Sources from the left navigation to open the Sources workspace. Use the Categories panel or search bar to find your desired source.
To connect Algolia, choose the Algolia source card under Data & Identity Partners and select Set up.
If a source does not yet have an authenticated account, it shows the Set up option. Once authenticated, this changes to Add data.
To use an existing account, choose Existing account and select the Algolia User Profiles account you want to use. Then select Next.
To create a new account, select New account, then enter a name, an optional description, and your Algolia credentials. Select Connect to source and wait for the connection to establish.
After your Algolia User Profiles account is created, the Add data step appears. Use it to select and preview user profile data for ingestion.
Once done, select Next.
If using an existing dataset, choose one associated with a schema that includes the Algolia Profile field group. Make sure the Algolia User Token field is using the Algolia User Token identity namespace. If the Algolia User Token is not currently created or assigned, instructions are provided below.
If creating a new dataset, select a schema using the Algolia Profile field group.
You will need to create the Algolia User Token identity namespace if it doesn’t already exist in your organization.
Use the left navigation and select Identities to access the Identity Service UI workspace and then select Create identity namespace.
Next, provide a Display Name and an Identity Symbol for your custom namespace. During this step, you must also configure the type of your namespace. When finished, select Create.
Custom namespace config | Value |
---|---|
Display Name | Algolia User Token |
Identity Symbol | AlgoliaUserToken |
Select a type | Cookie ID |
Once added, the namespace appears in the list. You can now apply it in your schema.
Use the left navigation and select Schemas to access the Schemas UI workspace. Use the schemas workspace to create or update a schema with the Algolia Profile Details field group. Next, navigate to the User Token field and use the right-rail to select the Identity box. Additionally, use the input box to define the Algolia User Token identity namespace. When finished, select Save.
After the User Token field is assigned the Algolia User Token identity namespace, the identity appears in the user profile for any profile.
Use the mapping interface to map your source data to schema fields. For more information, refer to the mapping guide.
Next, use the scheduling interface to define the ingestion schedule of your dataflow.
Scheduling configuration | Description |
---|---|
Frequency | Configure frequency to indicate how often the dataflow should run. You can set your frequency to:
|
Interval | Once you select a frequency, you can then configure the interval setting to establish the time frame between every ingestion. For example, if you set your frequency to day and configure the interval to 15, then your dataflow will run every 15 days. You cannot set the interval to zero. The minimum accepted interval value for each frequency is as follows:
|
Start Time | The timestamp for the projected run, presented in UTC time zone. |
Backfill | Backfill determines what data is initially ingested. If backfill is enabled, all current files in the specified path will be ingested during the first scheduled ingestion. If backfill is disabled, only the files that are loaded in between the first run of ingestion and the start time will be ingested. Files loaded prior to the start time will not be ingested. |
Use the review page for a summary of your dataflow prior to ingestion. Details are grouped in the following categories:
Once you have reviewed your dataflow, select Finish and allow some time for the dataflow to be created.
By following this tutorial, you have successfully created a dataflow to bring intent data from your Algolia source to Experience Platform. For additional resources, visit the documentation outlined below.
Once your dataflow has been created, you can monitor the data that is being ingested through it to view information on ingestion rates, success, and errors. For more information on how to monitor dataflow, visit the tutorial on monitoring accounts and dataflows in the UI.
To update configurations for your dataflows scheduling, mapping, and general information, visit the tutorial on updating sources dataflows in the UI.
You can delete dataflows that are no longer necessary or were incorrectly created using the Delete function available in the Dataflows workspace. For more information on how to delete dataflows, visit the tutorial on deleting dataflows in the UI.