Joining with External Customer Data and Transforming Data Using Bold Data Hub

In this article, we will demonstrate how to import tables from a CSV file, join with external customer data through transformations, and move the cleaned data into the destination database using Bold Data Hub. Follow the step-by-step process below.

Sample Data Source:
Tickets
Customers

Step-by-Step Process in Bold Data Hub

Step 1: Open Bold Data Hub

• Click on the Bold Data Hub.

Step 2: Create a New Pipeline

• Click Add Pipeline in the left-side panel.
• Enter the pipeline name and click the tick icon.

Step 3: Choose the Connector

• Select the newly created pipeline and opt for the CSV connector. You can either double-click or click on the Add Template option to include a template.

Step 4: Upload Your CSV File

• Click the “Upload File” button to select and upload your CSV file.

Step 5: Set the Properties

• Copy the file path and paste it into the filePath property field.

Step 6: Save and Choose the Destination

• Click Save, choose the destination, and confirm by clicking the Yes button.

Note: On-Demand Refresh will be triggered when the pipeline is saved. If needed, the pipeline can be scheduled in the Schedules tab.

Step 7: View Logs and Outputs

• Click the pipeline name in the left-side panel and switch to the Logs tab to view logs.

Step 8: Apply Transformations

• Go to the Transform tab and click Add Table.

• Enter the table name to create a transform table for customer satisfaction summary.

Note: The data will initially be transferred to the DuckDB database within the designated {pipeline_name} schema before undergoing transformation for integration into the target databases. As an illustration, in the case of a pipeline named “customer_service_data”, the data will be relocated to the customer_service_data table schema.

Learn more about transformation here

Joining with External Customer Data

Overview

Integrating Customer Support Center (CSC) data with Customer Relationship Management (CRM) data enriches support tickets with customer-related attributes. This helps in deeper analysis of customer demographics, spending behavior, and loyalty status.

Approach

We use a LEFT JOIN to merge ticket data with customer data, ensuring all tickets are retained even if some customers have missing CRM details.

SQL Query for Joining with External Customer Data

SELECT 
    t.Ticket_ID,
    t.Customer_ID,
    c.Customer_Name,
    c.Age,
    c.Gender,
    c.Income_Level,
    c.Customer_Segment,
    c.Loyalty_Program_Status,
    c.Reward_Points,
    c.Last_Purchase_Date,
    c.Total_Spend,
    c.Account_Status,
    c.Subscription_Type,
    t.Ticket_Category,
    t.Issue_Description,
    t.Ticket_Status,
    t.Priority,
    t.Resolution_Time,
    t.Agent_ID,
    t.Agent_Name,
    t.Customer_Satisfaction,
    t.Ticket_Creation_Date,
    t.Ticket_Resolution_Date,
    t.Ticket_Comments,
    t.Region,
    t.City,
    t.Country,
    t.Ticket_Cost,
    t.Phone
FROM {pipeline_name}.tickets t
LEFT JOIN {pipeline_name}.customers c 
ON t.Customer_ID = c.Customer_ID;