Destinations

This guide introduces you to the concept of destinations. 

What are destinations

Destinations define where an item type's data flows so Bloomreach applications can use it.

• Both item types can have one Marketing destination for marketing and personalization.

• Each product item type can also have one Search destination for search and merchandising.

A collection with several item types can therefore have several Marketing and Search destinations.

Key features

• Each item type connects to at most one destination per application.

• A destination receives the items of its item type, not every item in the collection.

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.

If a product item type has a context, its catalogs store context data, but only the catalog view uses it.

Search destinations

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

If the item type has a context, the Search catalog must be set up for multi-view.

Configure destinations

For configuration guidance, see the detailed setup guide.

Next steps

Now that you understand destinations:

• Monitor jobs to track destination sync operations.