Customers

Overview

The information in the Customers table is directly sourced from the Customer entities in CloudBilling. Therefore, the customer configuration in CloudBilling impacts how the various fields are populated in the table. If a customer has multiple addresses, the first address in the UI will be synced to the database.

In CloudBilling, the customers exist in an organised tree structure called Customer Clusters. Let’s consider a customer named “ABC Netherlands”, with customer code “123”, and the cluster structure All Customers -> Netherlands -> ABC Netherlands (123). Here “ABC Netherlands (123)” is the customer cluster, “Netherlands” is the parent cluster, and “All Customers” is the grandparent cluster. In the dataset table, this structure is defined as:

1. ClusterName = ABC Netherlands (123)
2. ClusterPath0 = All Customers
3. ClusterPath1 = Netherlands
4. ClusterPath2 = ABC Netherlands (123)

For further contextual information on how customers are configured in CloudBilling, view the Customers page.

---

Fields

Name	Type	Description
Key	Integer	Primary Key - Customers Table.
Code	String	A unique external identifier for a customer used to link purchases with a customer.
Name	String	The name of the customer.
Country	String	The country the customer is located in.
City	String	The city the customer is located in.
Postcode	String	The postcode the customer is located in.
AddressLine1	String	Address Line.
IsSuspended	Boolean	Whether billing is suspended for a customer. If 0, no billing will occur for this customer.
BillFrom	Integer	Foreign Key - Date Dimensions Table. The date from which a customer should be billed (yyyymmdd). If not specified in CloudBilling, the createdDate is used.
ClusterName	String	The name of the cluster a customer belongs to.
ClusterPath0 . . . ClusterPath9	String	Ten separate fields that represent the cluster structure a customer belongs to in CloudBilling. There are only ten fields because no cluster structure has exceeded 10 fields yet.
Created	Integer	Foreign Key - Date Dimensions Table. The date when a customer was created (yyyymmdd).
Modified	Integer	Foreign Key - Date Dimensions Table. The most recent date a customer’s properties were changed (yyyymmdd).