Data Sources
Every place a customer interacts with the business — and every internal system that already holds data about them. This is where raw events and records originate before entering the Ingestion Layer.
👤 Customer Touchpoints
Web / Mobile Apps
Highest-volume source of behavioral events across web and native apps.
IoT Devices
Telemetry from connected devices tied to a customer or account.
In-Store Kiosks
Self-checkout and product lookups from physical store locations.
Chat / Voice / Bots
Live chat, chatbots, and voice assistants capturing customer intent.
Email / SMS
Outbound and inbound engagement across email and SMS channels.
Call Center
Call metadata, IVR selections, and outcomes from the contact center.
Social Media
Mentions, comments, DMs, and ad engagement from platform APIs.
How to Consume
Cxos.Ingestion.Api · Command
POST https://ingest.cxos.io/v1/events
Authorization: Bearer <client-token>
Content-Type: application/json
{ "event": "product_viewed", "user_id": "cust_004821",
"context": { "channel": "web" }, "properties": { "sku": "sku-1029" } }
202 Accepted
🏢 Business Systems
CRM (Salesforce)
Accounts, contacts, opportunities, and case history synced from Salesforce.
Commerce (Shopify)
Order, product, and cart data from the commerce platform.
Support (Zendesk)
Support ticket history linked to the same customer profile.
Marketing (HubSpot)
Lifecycle stage and lead-score data from marketing campaigns.
ERP / Billing
Billing status, invoices, and subscription data tied to the account.
How to Consume
Cxos.Connectors.Salesforce / .Shopify / .Zendesk / .HubSpot / .ErpBilling · Command
// Registered via the central connector registry, not called directly:
{
"connector": "Cxos.Connectors.Salesforce",
"instance_id": "sfdc_prod",
"auth": { "type": "oauth2_jwt", "keyvault_ref": "sfdc-prod-cert" },
"sync_mode": "cdc"
}
// Each connector publishes normalized events to Cxos.Ingestion.Api on your behalf.
📁 Files & Integrations
CSV / JSON / Parquet
Bulk file exports landed and ingested on a schedule.
Databases
Operational stores replicated via change-data-capture or scheduled extract.
APIs & Webhooks
Generic REST/webhook path for systems without a dedicated connector.
How to Consume
Cxos.Connectors.Files / .Cdc / .Generic · Command
// File-based: drop into the per-source Azure Blob Storage landing zone
abfss://landing@cxosdata.dfs.core.windows.net/partner_loyalty_export/loyalty_2026-08-01.parquet
// Generic REST/webhook: register a field-mapping config, no new codebase
{ "connector_id": "conn_partner_survey", "mode": "webhook",
"field_mapping": { "event": "$.event_type", "user_id": "$.customer.external_id" } }
🔌 Platform Connectors
Named connector packages that bring each business system's data into the shared ingestion contract.
| Connector Package | Consumer |
|---|---|
Cxos.Connectors.Salesforce |
Identity & Profile Service (Intelligence & Services) · CRM (Salesforce) Reverse ETL (Destinations & Activation) |
Cxos.Connectors.Shopify |
AI & Insights (LTV/RFM scoring) · Web / App Personalization |
Cxos.Connectors.Zendesk |
AI & Insights (churn/CSAT signal) · Support (Zendesk) Reverse ETL |
Cxos.Connectors.HubSpot |
Query & Analytics Engine · Marketing (HubSpot) Reverse ETL |
Cxos.Connectors.ErpBilling |
AI & Insights (payment-risk scoring) · Operational Services (dunning alerts) |
Cxos.Connectors.Files |
Data Lakehouse raw zone (Unified Data Foundation) |
Cxos.Connectors.Cdc |
Data Lakehouse mirrored tables (Unified Data Foundation) |
A customer browses products on your website, adds an item to cart on mobile, receives an email, then completes a purchase in-store.