Create destinations

Configure destinations to deliver items and attributes to Marketing and Search.

Prerequisites

Knowledge

Understanding of item collection concepts.

Process

Ensure that you review the items and validate the schema. 

Permissions 

For Data hub, ensure you have the Item Collections Admin permissions.

For Marketing destinations, appropriate access management roles to view synced catalog data.

For Search destinations, appropriate user permissions to view the synced catalog data.

Setup

For Marketing destinations, the target Marketing project must be connected to your Data hub workspace.

For Search destinations, there must be an existing Search catalog in the staging or production environment.

Steps to create a destination

1. Navigation

1. Go to Data hub > Items in your Bloomreach workspace. 

2. Click the item type whose items you want to deliver. Item types are listed under their collection.

3. Click the Destinations tab.

4. Click + Add destination.

2. Choose and connect a destination

1. Choose a relevant destination:

   • Select Marketing as the destination. Choose the Marketing project linked to the workspace that should receive the item type's items, and enter the catalog names. Item types can connect to the same project, but each one needs its own catalogs, and the names must be available in that project. Catalog names don't need to match the item type's name. Data hub suggests a catalog name from the item type's name. To change the catalog's system name, click Edit.
   • Select Search as the destination. Choose your target Search catalog and environment (staging or production). Custom item types don't support the Search destination.

2. Click Apply.

3. Click Review and save changes. Review the modifications and deselect any changes you don't want to save. Click Save configuration. Data hub starts a Destination items update job automatically.

3. Go to destinations

Marketing destination

On sync completion, click Go to destination under the Destinations tab. This redirects you to the Marketing application to verify data under Data & Assets > Catalogs.

Click View next to the created product, variant, or general catalogs. Under the Attributes tab, you can control the attribute searchability settings.

Search destination

The sync job overwrites any existing data in the Search catalog. Check the Jobs tab for status, then log into your Search environment to see the synced data in the Catalogs application.

How Marketing destinations work

When you create an Marketing destination, you select which Marketing project should receive your items. Data hub automatically creates catalogs in that project to store the item type's data.

For a product item type with variants, the system creates two catalogs:

• Product catalog lookup: Contains product-level data for looking up products by their product ID.

• Variant catalog lookup: Contains variant-level data with denormalized product attributes for looking up individual variants.

The system keeps these catalogs synchronized with the item type's data and maintains the schema configuration automatically.

How Search destinations work

When you create a Search destination, you select a target catalog in a specific Search account and environment (staging or production). Data hub synchronizes item data and attribute configurations to the selected Search catalog, maintaining consistency with your schema. View the data received in the Catalogs application. Here, configure the searchability, facetability, and displayability settings.

Reserved names for custom attributes

If a custom attribute in a product item type uses a reserved name, it appears in Marketing and Search with a main. prefix, for example main.title. In the destination, reference the attribute by its prefixed name. For the full lists, see the Marketing reserved names and Search reserved names.

Data synchronization with destinations

Once you configure a destination, Data hub syncs the selected item type's items when its data changes. When you save changes in the Data hub interface, the sync starts automatically. For API updates, you choose whether a successful Records update starts the following jobs. For details, see Automatic success triggers.

What syncs automatically

• New items added to the item type.

• Updated items when records change.

• Schema modifications that affect item attributes.

• Item deletions when corresponding records are removed. 

Monitor sync status

Check the jobs interface to see the destination sync job status. Each sync operation creates a job showing how many items were synced, whether the sync succeeded or failed, and any errors encountered during synchronization.

The destinations view in your collection also displays the last sync date and current status for each destination. 

FAQs

Can I have multiple Marketing destinations in the same collection?

Yes, through different item types. Each item type can have one Marketing destination, so a collection with three item types can have three Marketing destinations. Adding another item type doesn't give the original item type a second destination.

Can two product item types send data to the same Search catalog?

No. Within the same Search account and environment, each product item type needs its own catalog.

What happens to my Marketing catalogs if I delete the destination?

Deleting a Marketing destination also deletes the catalogs created in that Marketing project. The system warns you before deletion, but this action removes the catalog data from Marketing.

What happens to my Search catalog if I delete the destination?

Deleting a Search destination removes the connection between Data hub and that catalog, but the catalog itself remains in Search. The catalog will no longer receive updates from Data hub.