The customer table
you actually own
Native Objects is Orbee's data model. Customers, Vehicles, Service Orders, Inventory, and Web Events modeled as governed tables you control — with custom properties for the fields your operation cares about and custom objects for the things your operation tracks that nobody else does. The golden record automotive has been missing.
A curated data model that covers automotive out of the box
Orbee ships with a managed set of native objects. Each has a set of essential default fields the table can't live without — and beyond those defaults, every table is extensible.
The golden record, and every vehicle behind it.
Customers is harvested from CRM, DMS, web, call, and offline sources with collision management built in — one row per identity-resolved shopper. Vehicles covers everything owned, serviced, traded, or financed across any rooftop.
- One row per resolved shopper
- Collision management & prioritization
- Documented joins to Inventory
Service Orders and full VIN-level Inventory.
Every service appointment, repair order, warranty claim, and parts transaction — sourced from DMS. Active and historical inventory positions with full VIN-level detail and engagement signals from Web Events.
- Repair orders & warranty claims
- VIN-level inventory history
- Engagement signals attached
First-party events captured by Orbee Native.
VDP views, SRP filters, finance forms, trade-ins, click-to-call, click-to-text — with consent state and identity resolution baked in.
- Automotive-specific taxonomy
- Consent state on every event
- Identity-resolved at capture
Not a virtualized model hitting live source systems.
Static, materialized tables you can trust.
Most CDPs query live source systems through abstraction layers, with all the latency and brittleness that implies. Native Objects works differently.
ClickHouse-backed
Static, materialized tables backed by ClickHouse for billion-row-scan performance — records that load in milliseconds.
Cheaper than a data lake
Building static tables is dramatically cheaper than managing endless data permutations in a data lake.
Production-ready
Tables live in the production ClickHouse cluster with automated schema management and minimal downtime guarantees.
Extend the managed tables — or create entirely new ones
Custom properties and custom native objects join the same governance model as the managed defaults: documented in the catalog, queryable in Studio, visible in Explorer.
Boolean flags
is_customer, has_used_our_car_wash, service_contract_active — fields specific to your operation.
Calculated & enriched fields
lifetime_value, top_three_makes_viewed, plus equity from JD Power, recall data from NHTSA, call intelligence from Marchex.
Lots & Floorplans
Custom objects for multi-rooftop car storage, or RV dealers modeling inventory by configuration, slide count, and sleep capacity.
Custom objectPrograms & offers
Custom objects for OEM-program-enrolled dealers tracking program-specific touches and outcomes, or service contract and warranty programs.
Custom object
A CDP is only as useful
as the customer table underneath it.
Most platforms either skip that layer entirely or hide it behind a proprietary schema you don't get to see. Native Objects is documented, the schema is yours, and the customer record is something your team can query, extend, and trust — independent of which DMS or CRM populated it. If you're going to own one thing inside Orbee, this is it.
A data model you actually own.
Live walkthrough of native objects populated with your group's data sources.
Governed & documented · Extensible by your team