Regular Imports

To fully leverage the functionality of Bloomreach Engagement, it is necessary to ingest data on a regular basis. This includes transactional, customer, consent, and catalog data. There are multiple ways the data can be ingested into Bloomreach Engagement, which you can find outlined below. Please, review the individual responsibilities.

Transactional data

In order to unlock the full potential of Bloomreach Engagement, it is necessary to ingest customer transactional data on a regular basis. This is imported in the form of 'purchase' and 'purchase_item' events with event attributes in accordance with the Tracking Document.

To learn more about importing transactional data, see our Importing events documentation.

The following integrations are available.

Customers

In order to accurately target customers with campaigns, it is necessary to import customer data on a regular basis.

To learn more about importing customer data, see our Importing customers documentation.

The following integrations are available.

Consents

In order to accurately target customers with campaigns, it is necessary to import marketing communication preferences (opt-ins/opt-outs,etc) on a regular basis. These preferences are represented as 'consent' events in the Bloomreach Engagement platform following a predefined structure with all mandatory fields as detailed in the Tracking Document.

To learn more about importing consents (i.e. consent events), see our Importing events documentation. To learn more about consents in general, see our Consent management documentation.

The following integrations are available.

Catalogs

To leverage catalog data for campaigns, it is necessary to ensure the needed catalogs are regularly uploaded into the Bloomreach Engagement platform.

To learn more about importing catalogs, see our Importing catalogs documentation.

The following integrations are available.

Troubleshooting

• Ensure that your tracking code is deployed according to the most up to date version of Tracking Document
• Verify that needed integrations are in place (e.g. SQL, BQ, SFTP)
• Make sure tracked data are available on the appropriate location (e.g. purchase data on appropriate BQ location)

📘

Updating items in catalogs

We recommend you to update items in an existing catalog rather than deleting all items and reimporting them, for example, on a daily basis. The latter approach may lead to running campaigns referencing empty catalogs as there is a delay between a deletion request, the actual deletion, and the time when newly imported items become accesible.

We recommed:

• in case of inactive items or out-of-stock items:
  • Update products and use an attribute to indicate when a product is out of stock or inactive. Then, in campaigns and recommendations, use an appropriate filter to filter out only active items or items in stock.
• in case of dramatic changes of the catalog feed on a daily basis (e.g., 1000 items on day 1, which become substituted with 800 different items on day 2)
  • Implement an 'imported_timestamp' attribute. Then, in campaigns and recommendations, use an appropriate filter to include only items imported in the last 24 hours.