Imports in Bloomreach Engagement load customers, events or catalog items from a file, a database or a storage bucket, either once or on a repeating schedule. They are the usual route for data that does not come from tracking: order history, loyalty balances, product feeds, attributes computed in a warehouse.
Category
Bloomreach Dev, Data Architecture
Also known as
import; scheduled import; data import
In practice
Give every scheduled import an owner and an alert. Imports fail more quietly than tracking does, and a segment built on a stale imported attribute keeps sending as if nothing happened.
Something out of date?