In our eight-part blog series, you will gain insights into the implementation of a customer data platform. After the initial planning stage, in which the project’s organization and requirements were defined, we are now in the implementation stage. In this stage, specifications have already been decided on, the basic configuration was implemented, and a data repository was created. At this point, the configuration of the use cases can be started.
Most customer data platforms offer so-called journey builders for the configuration of the defined use cases. These are often designed as simple point-and-click interfaces and consist of different elements that can be categorized into three types as follows:
In order to be best prepared for the go-live – and in addition to the final CDP implementation of the created data repository, some historical data is required, which should be transferred to the CDP. It makes sense to integrate customer data, consents, purchase histories or product data from a certain period. However, which data sets are useful in individual cases depends strongly on the defined use case.
Important: Particular care should be taken when migrating consent forms. In close coordination with the legal department, the period of time that the data may be used for the personalization of content should be defined for all data points.
Once the use cases have been configured in the CDP and historical data has been migrated, the final and decisive phase can begin: quality assurance and go-live.
Don't miss a thing.
Subscribe to our latest blog articles.