Tulo Engage BI¶
Customer model¶
Timestamps
All timestamps are converted to local time for the organisation.
The customer model is an adaptation of the accounts in payway_data.pw_accounts
. The customer model in Engage BI can be found in the schema engage_bi
and is available in the view pw_customers_view
. The data in pw_customers_view
is materialized nightly into the table pw_customers
which is the table queries should be executed against.
The primary purpose of the customer model is to add context to an account if the customer is passive or active and also removes archived (deleted) accounts.
The customer model contains the following columns.
column | type | comments |
---|---|---|
id | string | Id of the customer/account, this is the id from the payway_data.pw_accounts table. |
organisation_id | string | The organisation that owns the subscription. |
customer_number | string | Legacy customer number, could be customer number from previous system or a customer number maintained by external subscription system. |
tulo_customer_number | string | Tulo customer number. |
string | Email address. | |
customer_type | string | Type of customer. passive, active or lead. Codes and values. |
mobile_number | string | Mobile number. |
first_name | string | First name. |
last_name | string | Last name. |
company_name | string | Company name. |
birth_date | date | Birthdate if available. |
age | int | Age if known. |
gender | string | Gender if known. "M" = Male or "F" = Female, "?" if unknown. |
origin | string | Account origin if available. |
created_from | string | Indicates how the account was created. Codes and values. |
created | timestamp | Timestamp customer/account was created. |
Active customers¶
Active customers are also located in view pw_active_customers_view
which is materialized nightly into the table pw_active_customers
which is the table queries should be executed against. The data contains customer/account information along with information about any subscriptions the customer might have, including distribution address if available. See subscription-model for more information about subscription data in this table.
Besides customer/account data, the model also contains information about the current subscription and it's delivery address if available.
Passive customers¶
Passive customers are also located in view pw_passive_customers_view
which is materialized nightly into the table pw_passive_customers
which is the table queries should be executed against. The data contains customer/account information along with information about the last active subscription the customer have hade, including distribution address if available. It also includes information about possible cancellation reasons and timestamps for both cancellation and deactivation. Data in this model is suitable for passive customer processing.
Besides customer/account data, the model also contains information about the last known subscription and it's delivery address if available.