Account and project creation

Upon signature, Bloomreach Engagement will create an account and project(s) for you, and will send project access invitations to the relevant users. It is important that the invited users accept this invitation in a timely manner as it expires after a certain amount of time. It is recommended that the users check their spam boxes too in case the invitation falls there.

Your responsibilityBloomreach's responsibility
1. Accept project access invitation
2. Make sure you can access the project URL
3. Make sure you can login into the project
4. Check access for all team members
1. Create the account
2. Create the project(s)
3. Invite users to the project

You can read more about setting up your Bloomreach Engagement project in our documentation.

Determining data structure

Determining the data structure is the most important part of the integration. Everything that is tracked inside Bloomreach Engagement powers the Single Customer View, which in return enables communicating with the right customers at the right time, making them the right offers in the right channels.

In order to ensure consistency between all parties, a 'Tracking Document' will be created. The Tracking Document (TD) is a spreadsheet describing the data structure of the project, such as event naming conventions, properties types and initial sources of data in Bloomreach Engagement.

Full list of events and attributes will be kept in the Tracking Document created by you together with the Bloomreach team. Contents of the tracking document should be mostly decided in the beginning of the project and should not change significantly throughout the integration.

Your responsibilityBloomreach's responsibility
1. Initial filling the tracking document with relevant information according to your systems & business use-cases defined in the scope document
2. Ensuring that the tracking document is kept up to date
1. Tracking document creation
2. Guidance, suggestions and provisioning

Read more about Bloomreach Engagement's data structure and single customer view in our documentation.