Help Center

Once you familiarize yourself with what a CDP use case is and have browsed some of our most common use cases by industry, you may have an idea of where you want to begin. Now, before that use case can be executed, you need to answer a few questions before starting the setup. Repeat the process outlined in this article for every use case you plan to accomplish with BlueConic.

Why does your use case matter?

Before you start to implement a use case, first ask yourself whether there is a Value-Based Outcome associated with it. Value-Based Outcomes are defined areas of focus that help you measure the value of a CDP to your overall business and goals. This will not only help get everyone on board with your use case, but it provides the why behind the effort.

Before you begin

Now, you can begin to document some of the details necessary prior to setting up your use case. While every use case looks different and may include unique nuances, focusing on these five areas before you begin should set you up with a strong foundation.

1. Key stakeholders

   The first step is identifying who needs to be involved in the implementation of this use case and who will be the project owner to ensure everyone is on the right track. While you may not know who will be executing every function of your use case at this stage, it is important to know who your point-of-contact for all questions are and what teams will need to be involved in the conversations.

   
   

   Checkpoint

   Do you know who, at your company, should play a role, either managing or executing, in your use case?

2. Target audience

   Next, pinpoint the audience this use case is targeted towards, including any necessary details for segmentation, qualification, and touchpoints. This is the time to assess what you know about your customers and what data you still need to gather.

   
   Checkpoint

   Do you know who your target audience is for your use case and how to reach them?

3. Data types

   Once your target audience is identified, you will want to take an audit of the data you already know about that audience and any data gaps you may need for execution. For the data you already have collected, you will want to be familiar with the types, formats, systems, and quantities. For any customer data gaps, you will want to have an idea of what new data collection process, sources, or transformation methods are needed. It is also important during this stage to ensure that you have a unique identifier that can be used for this use case to differentiate customers from each other.

   
   Checkpoint

   Do you know the online, offline, and uniquely identifying data required for this use case?

4. Platforms

   This step may be ignored in some circumstances, but most use cases involve either bringing in data or sending out data to other platforms outside of BlueConic. If this is true of your use case, it is important to determine which platforms are required ahead of execution so you can gather the necessary access credentials and determine what types of data need to be shared.
   

   
   Checkpoint

   If your use case requires other platforms, do you know what they are, who owns them, and how to access them?

5. Measurement and ROI

   Finally, in order to verify the results of your use case, it is important to outline the standards of measurement and success. This includes determining any baseline KPIs that exist in your company today, setting goal metrics, figuring out where and how results will be reported, and defining the role time plays.
   

   
   Checkpoint

   Do you know what success for your use case looks like?

Once you have these five areas defined more clearly, you can begin to implement your use case in BlueConic. If you have any questions along the way, please contact your BlueConic Customer Success Manager.