Skip to main content

Overview

The Mission Control database is organized into three core models that handle the full data pipeline from event ingestion through customer identity resolution and user management.

Event Model

Data from every connected client is processed through Kafka and stored in the Events table. The tracking tag is responsible for fetching client click data and sending it to Kafka consumers.

Data Flow

Tables

Raw event data ingested through Kafka. This data is further processed by the “Process Data” script for evaluating, analyzing, and scrubbing.
Contains processed user details including orders, visits, and transaction details.
Stores credit given to each source that a user has come through. Tracks orders and visits by customer.
Records order information by media source for the Customer Interaction platform.
Tracks the number of times users visit a specific website, aggregated by date.

Customer Model

This model retains data from third-party sources like Shopify and HubSpot. The Data Collector script processes data from these sources and stores it in the Integration Customer table.

Data Flow

Tables

Raw customer data from third-party integrations.
Manages the mapping and routing of customer data from the Integration Customers table to the eventapp tables. Divided into three sub-tables:eventapp_dataobjectconfigeventapp_idtypeeventapp_attribute
Stores customer credentials (email, customer ID) resolved from the Integration Customers table.
Retains additional customer details such as name, address, and contact information.
Records customer events (currently stores Gorgias data).

Users Model

Handles client onboarding and authentication. When a new client registers through the client registration form, their details are stored in the useraccount_client table with a corresponding client_id. Login credentials (email and password) are stored in the users table under the same client_id.

Tables

Client account details created during registration.
User authentication and profile data.