Destinations

👍
Data hub rollout
Data hub provides new unified API integration methods for sending data to multiple Bloomreach products. Access is being rolled out in phases. For new implementations, we recommend using Data hub where available. Existing product-specific integrations remain fully supported for Marketing, Search, and Conversational agent.

This guide introduces you to the concept of destinations.

What are destinations

Destinations define where your item data flows so Bloomreach applications can use it. In most implementations, you'll create two destinations: Marketing for marketing and personalization (and Conversational agent for conversational search), and Search for search and merchandising.

Key features

One destination maps to one application type in each collection. For example, you can have a single Marketing destination and a single Search destination.
Items in your collection automatically sync to a given destination.

Why destinations matter

Destinations let you push your curated item data to the Bloomreach products that deliver immediate business value, such as personalization in Marketing or search and merchandising in Search.

Destination types

Marketing destinations

Marketing destinations sync your items to Marketing projects for marketing automation and personalization use cases.

Search destinations

Search destinations sync your items to Search catalogs for search and merchandising features.

Configure destinations

For configuration guidance, see the detailed setup guide.

Next steps

Now that you understand destinations:

Monitor jobs to track destination sync operations.