Historical Imports
It is possible to import data to your project from sources outside of Bloomreach Engagement. These can be CSV or XML files (uploaded through the import wizard or through a URL feed), integrated SQL databases, imports from file storage integration (Google Cloud Storage, SFTP and Amazon S3).
For more information about imports, please visit our documentation.
| Your responsibility | Bloomreach's responsibility |
|---|---|
| 1. Data validation and quality according to the Tracking document 2. File creation and upload in the correct format 3. Data mapping 4. Import execution | 1. Guidance 2. Connection QA 3. Data mapping QA |
Transactional data
Ingesting historical transactional data is an essential prerequisite for many reports and use cases to be implemented to their fullest potential in Bloomreach Engagement. This data is imported in the form of 'purchase' and 'purchase_item' events with event attributes in accordance with the Tracking Document.
For example, when a customer buys 1 unit of product A and 2 units of product B within one transaction,
this will be tracked in a single purchase event and two purchase_item events (1 for product A and one for product B; the quantity is recorded in an event attribute).
| Type | Description |
|---|---|
| Manual Upload | Purchase and purchase_item data will be uploaded, according to the most recent version of the Tracking Document, manually to the Bloomreach Engagement platform in CSV or XML format. |
| URL Download | Data will be uploaded to Bloomreach Engagement by importing XML or CSV files from a HTTPS secure URL. |
| File storage (e.g. SFTP) Download | Data is uploaded to Bloomreach Engagement by importing XML or CSV files from a file storage owned by you. Secure connection is ensured via exchange of credentials and SSH keys. |
| Database (SQL) | Transactional data will be imported from an SQL database owned by you, via the database connector present in the Bloomreach Engagement Import Wizard. You are responsible for building views and creating SQL queries used for ensuring secure data extraction. |
| Shopify Integration | Bloomreach Engagement has a native integration with Shopify, which allows it to pull historical transactional data and other events. You can learn more about it and how to set it up in our Shopify documentation. |
Customers
Ingesting historical customer data is an essential prerequisite for unlocking the full potential of the Bloomreach Engagement platform. Customer attributes should be imported according to the format defined in the Tracking Document.
| Type | Description |
|---|---|
| Manual | Customer attributes will be uploaded manually directly to Bloomreach Engagement Import Wizard as a CSV or XML file, according to the most updated version of the Tracking Document. |
| URL Download | Customer attributes will be uploaded to a HTTPS secured URL via CSV or XML files. |
| File storage (e.g. SFTP) Download | Customer attributes will be uploaded via client-owned SFTP as a CSV or XML file/s. Secure connection is ensured by exchange of credentials and SSH keys. |
| Database (SQL) | Customer attributes are imported from the client-owned SQL database in the proper format (CSV or XML), via the database connector present in Bloomreach Engagement Import Wizard. You are responsible for building views and creating SQL queries used to ensure secure data extraction. |
| Shopify Integration | Bloomreach Engagement has a native integration with Shopify, which allows it to pull historical customer data and other events. You can learn more about it and how to set it up in our Shopify documentation. |
Consent
Ingesting historical marketing communication preferences is essential for managing data privacy regulations and customer preferences. These preferences (opt-ins/opt-outs) are represented as 'consent' events in Bloomreach Engagement and should follow a predefined structure with all mandatory fields as detailed in the Tracking Document.
| Type | Description |
|---|---|
| Manual Upload | Customer consents will be uploaded manually to Bloomreach Engagement platform as CSV or XML file. |
| URL Download | Customer consents will be imported in the form of CSV or XML file uploaded to a HTTPS secured URL. |
| File storage (e.g. SFTP) Download | Customer consents will be imported in the form of CSV or XML file uploaded to a HTTPS secured URL. Verify that SFTP integration is in place. |
| Database (SQL) | Customer consents are imported from the client-owned SQL database, via the database connector present in the Bloomreach Engagement Import Wizard. The client is responsible for building views and creating SQL queries used to ensure secure data extraction. |
Consent events are not in the scope of Shopify integration and have to be integrated via other custom methods.
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).
Updated about 1 year ago