❗️

New integrations

As of May 2021, all new integrations are required to use [API based catalog feed management](🔗) to send data and perform index updates.

If you are a B2B customer or a customer operating in multiple markets, Bloomreach recommends that you use a multi-view feed. The purpose of a multi-view feed is to allow you to customize data for specific views without having to repeat large chunks of data. This effectively simulates in the API having multiple individual catalogs with less overhead. The integrations team will advise you on which type of feed is most appropriate for your needs.

## XML feed templates

## View ID field

The **view ID** allows Bloomreach to filter the catalog to only show the products and versions of products that you want a particular site visitor or subsite within your account to see. Multi-view feeds are required to include a view_id field, which must always be declared with values. Values must be separated using a special character such as ^.

The values for view_id should be consistent across the feed, API, and pixel. B2B customers will normally provide an alphanumeric ID to represent their users catalogs. For multi market customers, we recommend using [ISO 3166 country codes](🔗).

## Multi-view field values

In addition to declaring view_id, you need to decide which of your other fields will contain view specific information. View specific values must be provided in the same order as the view IDs declared in the view_id field. Once you have made a field view specific, it must always be view specific in the feed.

This product has three view IDs: ac1, ac2, and ac3. The following table contains the prices and sale prices for each view:

## Variants in multi-view feeds

If your catalog has variants, such as SKUs, you will have to declare view_id values for each variant. This allows you to include or exclude certain variants for different views.

Read more details about variants in the feed templates above.

## Designing multi-view feeds for multimarket accounts

For multimarket accounts, multi-view feeds can get more complicated as many product attributes can change between different territories, such as sizes, definitions, urls, and prices. Before creating your feed, you should first decide which fields and values need to be view specific, and identify ways to avoid complicating the feed.

🚧

For URL and image URLs

Consider declaring only the URL and image URLs for the main market. You could then drop the domain from the URLs in your API response, keeping them relative to the local market view.

You could also create fields for “rel_url” and “rel_image”, which are the URL and image URL respectively minus the domains and market subfolders if they exist. In your API, you would use rel_url and rel_image in place of url and image.

Once you have decided which fields need to be view specific, we suggest placing the view specific fields inside the variants section of your product feed. This allows you to inform the API that certain sizes or colours are only in stock for specific markets. You must also inform the Bloomreach integrations team which fields you have decided to be view specific so that the correct handling of these fields can be set during feed processing.

## Multi-view delta feeds

For multi-view delta feeds, you must include the following fields:

• view_id

• pid

• skuid

• availability

You must also include all variant information, that is, all product variants and view specific values. You cannot only update a single view value or variant.