FAQs - Brevo Customer Data Platform (CDP)

Overview and answers to your most common questions concerning the Brevo Customer Data Platform (CDP).

❓What are the onboarding and setup steps for the Brevo CDP? 

The onboarding steps may differ depending on your Enterprise Solution paying plan for the Customer Data Platform. To learn more, select the tab corresponding to your plan below:

CDP Essential CDP Pro
  1. Complete the Marketing CRM onboarding, as your data will be imported from your Brevo CRM sub-accounts. 
  2. Attend a workshop to select the scores from the Scoring Library and discover the Analytics environment.
  3. Implementation of scores and Business Intelligence (BI) environment within a maximum of 4 weeks from the kickoff. 

❓What are the options to import my data into the Brevo CDP? 

The Brevo CDP allows you to import data from many different resources from your Brevo sub-accounts to FTP servers or databases and data warehouses. To learn more, check our dedicated section Connect your data sources and destinations to the CDP

❓Do I need to prepare my CSV or JSON files in a specific format? 

Yes. The Brevo CDP allows you to import structured data from FTP files for one-shot or recurring automated imports. When importing your data to the Brevo CDP via FTP servers, certain data need to be in a specific format to be imported correctly. Expand the accordion below to discover our requirements to properly set up the files that contain your data before importing them: 

📄 Requirements for FTP files
  • Include only one sheet in your file.
  • Create one file per entity. An entity is the type of data you are importing such as contacts, orders, or products for example. 
  • Save your file with UTF-8 or UTF-8 BOM encoding. These types of file encoding allow for reading the content of your file when it contains special characters.
  • Include at least one source key for each file. A source key represents a column from your file that acts as a unique identifier for your contacts such as their email address or phone number. 
  • Save your file in one of the following formats:
    .CSV with any separator
    (Microsoft Excel, OpenOffice Calc, Google Sheets, Numbers, ...)
    .JSON
    (JavaScript Object Notation)
  • If you want to import your data from a CSV file, follow these additional requirements: 
    • Define the first line as the header. The header is used to determine the number of columns in the file and map its content during import.
    • Include the same number of columns for each line of your CSV file. Each line should contain a single record, and text values should be enclosed in double quotes ("). 

❓ What are the different scores available to enrich my data? 

Add computed columns to your datasets to combine and enrich your data. You can either:

  • Select ready-to-use scores from our library of more than 30 classic CRM scores, such as RFM, Purchase Timing Deviation, preferred store or product categories. Expand the accordion below to discover our list of main scores available ⬇️. 
    📄 List of the main scores available in the scoring library
    Score Description
    RFM Multi-dimensional score categorizing customers based on their Recency, Frequency, and Monetary value.
    Purchase Timing Deviation The Purchase Timing Deviation Score segments customers by their buying cycles to predict future purchases. Categories like 'Recent Purchase,' 'Approaching,' 'Overdue,' and 'Significantly Overdue' help forecast next purchases and identify disengagement risks.
    All ordered product categories List of all product categories ordered by the customer.
    Top 3 product categories purchased from Top three product categories most frequently ordered by the customer.
    Nb of distinct product categories Total number of unique product categories ordered by the customer.
    Favorite store Store where a customer has made the most orders.
    All stores with 1+ order List of all stores name where the customer has made at least one order.
    Number of distincts stores with 1+ order Total number of unique stores where the customer made at least one order.
    First order store Store where the customer made their initial order.
    Last order store Store where the customer made their most recent order.
    Segmentation - Multi-buyer Boolean tag indicating whether a customer has made more than two orders.
    Segmentation - Multi-category Boolean tag indicating whether a customer has ordered products from more than two categories.
    Segmentation - New Customer Boolean tag indicating whether a customer has made a single order.
    Segmentation - Regular Customer Boolean tag indicating whether a customer has made more than two orders.
    Segmentation - Omnichannel Boolean tag indicating whether a customer has made orders from at least two different channels.
    Segmentation - Multi-store Boolean tag indicating whether a customer has made orders from at least two different stores.
    Segmentation - Active customer Boolean indicating if a customer has any orders.
    Orders - Total amount Total monetary value from all orders made by the customer.
    Orders - Average value Average monetary amount from all orders made by the customer.
    Orders - Total count Total number of orders made by the customer.
    Orders - Total number of items Total number of items ordered by the customer.
    Orders - Average items per order Average number of items per order made by the customer.
    Orders - Average time between orders Average time (number of days) between consecutive orders made by the customer.
    Orders - Number discounted orders Total number of orders with discounts made by the customer.
    Orders - Rate of discounted orders Proportion of discounted orders out of total orders made by the customer.
    Orders - Average discount rate Average discount percentage applied to the customer's orders.
  • Create custom aggregates based on other objects and apply a compute such as sum, average, last value, on other table fields. For example, Sum of Subscriptions Amounts only for Subscription for which the subscription product = Marketing CRM. 
  • Enter an SQL query to create custom computed fields. SQL formulas are only based on the columns of the current object. For example, you can create a computed column Age based on the column Birthday with the formula EXTRACT (YEAR FROM age(birthdate))

❓How can I analyze customer data transformed with the CDP? 

We offer built-in analytics and exploration dashboards, as well as the possibility to create custom dashboards powered by Looker with the Brevo CDP. After unifying and enriching your data with the Brevo CDP, you can explore and analyze it from your Brevo Analytics dashboard. From there, you will find:

  • Seven pre-made dashboards, including a Customer Knowledge report to get valuable insights on your customers from all your touchpoints and sources.
  • Custom and exploration dashboards powered by Looker. Create some ad-how queries, visualize them in a data and information visualization (Dataviz), and combine reports to create a full dashboard. 

To learn more, check our dedicated section Analyze your data in the Getting Started with the Brevo CDP article. 

You can also connect your Business Intelligence tools to the Brevo CDP. To learn more, check our dedicated question below.

❓ Can I connect Business Intelligence (BI) tools to the Brevo CDP?

We already offer built-in analytics and exploration dashboards, as well as the possibility to create custom dashboards powered by Looker with the Brevo CDP. However, you can also connect your Business Intelligence tools to the Brevo CDP.

Create syncs from the Brevo CDP to send all your CDP tables to your datawarehouse, database, or to FTP server. If your BI tool is already connected to the datawarehouse or database, you will be able to use the CDP tables directly indised your existing BI tool. 

❓ How do I contact the Brevo CDP support team? 

To contact our CDP support team, write an email to support@brevo.com with CDP in your email object so that your ticket is assigned to a support member with CDP expertise. 

Since the CDP platform is a complex tool, it requires precise information so that we can help you in the best ways possible. Your help request needs to include: 

  • Account information. Mention the Brevo sub-account involved, e.g., The Green Yoga - Production
  • Summary. Provide a one-sentence summary of your issue, e.g., Error XXX when saving my dataset after the change XXX
  • Actions taken. Describe in bullet points the actions you performed leading up to the issue. You can include screenshots or videos to illustrate the issue. 
  • Observed result. Explain in one or two sentences what outcome was produced by your actions, and add a screenshot. 
  • Expected result. Describe in one or two sentences what you expected to happen instead. 
  • Investigations. Detail any steps you took to investigate or troubleshoot the issue on your own. 

⏭️ What's next? 

🤔 Have a question?

If you have a question, feel free to contact our support team by creating a ticket from your account. If you don't have an account yet, you can contact us here.

If you’re looking for help with a project using Brevo, we can match you with the right certified Brevo expert partner.

💬 Was this article helpful?

0 out of 0 found this helpful