Custom item types for non-product business data
Data hub custom item types model business data such as articles, locations, or hotel properties alongside products, and can publish to Marketing as general catalogs.
Entries on this page are generated by AI from vendor sources. How AI is used
Defining schemas, objects, relationships and catalogs.
| Month | Changes |
|---|---|
| 2026-01 | 10 |
| 2026-02 | 1 |
| 2026-03 | 1 |
| 2026-04 | 9 |
| 2026-05 | 6 |
| 2026-06 | 8 |
| 2026-07 | 8 |
| 2026-08 | 11 |
| 2026-09 | 15 |
| 2026-10 | 16 |
Select a month to view the whole-record timeline. This clears timeline filters.
Platforms with at least one feature state classified in this capability (primary or secondary, minor updates included), in the site's fixed order. Select one to filter the timeline. Counts are not shown side by side: they reflect how finely each vendor documents, not how much it offers.
Filters apply to the timeline. The chart and platform totals describe the whole record. Selecting a chart month clears timeline filters to show that same whole-record scope.
Matches the Release Matrix evidence: latest state reached in the selected period, entries under review excluded, primary and secondary capabilities included.
No recorded changes match these filters.
Within each period: major updates as cards, then notable ones as rows; newest first in each group. Minor updates below.
Data hub custom item types model business data such as articles, locations, or hotel properties alongside products, and can publish to Marketing as general catalogs.
Data hub contexts tailor product data (prices, availability, assortment) per store, region, or price list in one item type, with context-specific overrides.
In limited availability, lets admins define up to 10 custom business fields per entity for Action campaigns, journeys and orchestrated campaigns, recorded in dedicated datasets.
Catalogs can be assigned to a Team, with Team-level permissions to view, edit, export, or delete them, scoping catalog access without granting it workspace-wide.
Custom Objects lets businesses model their own data as real objects for their use case; now available to all Klaviyo accounts.
Relational schemas will be able to link to primary identity fields and other supported fields in standard schemas, without segmentation enablement.
Now Preview (29 Oct 2026). Current summary: In limited availability, lets admins define up to 10 custom business fields per entity for Action campaigns, journeys and orchestrated campaigns, recorded in dedicated datasets.
CRM index pages can now be filtered by properties of associated objects, not just the object's own fields.
A new overview tab reviews data health issues and lets admins create properties, objects and pipelines in one place.
The rebuilt Smart CRM index for Contacts, Companies, Deals, Tickets, Tasks and Custom Objects offers flexible board/Gantt/report views, collapsible filters, and AI column insights, live for all portals.
Build audiences combining Catalog data with profile fields and event history, without copying catalog details onto every profile.
Loyalty event mapping got a visual builder with field search, per-row status, and JSONata preview; renamed from Event Definitions to Event Mappings.
Orchestrated campaign email conditions can now reference related records via relational data, not just standard profile attributes.
New Bulk API endpoints load and query Marketing Object data at scale.
Marketing Object schema changes can be tested in a sandbox and deployed to production with change sets; schemas replicate from production when a sandbox is refreshed.
Build a Marketing Object's schema from scratch instead of only from templates.
Smart CRM is planned to update records automatically rather than relying solely on manual edits.
Journeys/campaigns using Audience Composition audiences without a primary identity descriptor will stop working from the October release.
Copies a data extension's columns, data types, primary keys and records from Marketing Cloud Engagement into a Marketing Object in one step, as a one-time copy with no ongoing sync.
Now GA (4 Sep 2026). Current summary: The rebuilt Smart CRM index for Contacts, Companies, Deals, Tickets, Tasks and Custom Objects offers flexible board/Gantt/report views, collapsible filters, and AI column insights, live for all portals.
Real-Time CDP B2B Edition now supports time-series relational schemas in custom objects for segmentation.
Behavior Activation now supports up to four linked behavior tables per activation via the Audience API, up from a single table; Console support pending.
Salesforce Marketing Cloud V2 export connector now supports composite primary keys of up to four fields when creating Data Extensions.
Easier UI to add new fields and individual records to a Marketing Object.
The Sales Data Kit can now be managed independently of other data configuration.
A centralized Data Model Management page lets admins create, edit, rename and delete custom objects and export properties and the object graph.
Adds metadata, filtering, user-defined tags/folders and inline actions to the XDM schema browse page.
The schema page flags misconfigured related models by checking join key cardinality and warning on incorrect relationship settings.
Now GA (4 Sep 2026). Current summary: The rebuilt Smart CRM index for Contacts, Companies, Deals, Tickets, Tasks and Custom Objects offers flexible board/Gantt/report views, collapsible filters, and AI column insights, live for all portals.
Marketing Objects are a high-throughput, low-latency store for marketing data, loaded from external systems by CSV import and readable in emails with Handlebars or AMPscript.
Catalogs support a geolocation field type and distance-based Catalog Selection operators for proximity targeting like nearest store or items within a radius.
Admins can specify the allowed set of values for fields in Marketo Engage through Picklist Management.
Additional WhatsApp interaction data, including message type, replies, delivery status, and reactions, is now captured for audiences.
Campaigns gain data-model visibility, associations and custom labels with custom objects on Enterprise, segment support using Campaigns as the primary object, and conditional property logic on campaign properties.
Marketing Events now behaves like a standard CRM object: a full record layout with activity timeline, custom properties and campaign associations, field-level permissions, export, conditional logic, and support as the primary object for reports and segments.
General catalog imports through Data hub now auto-create missing schema attributes as string fields from imported file columns.
Relational schemas now support multi-field composite keys, with DDL/Excel loading auto-creating composite relationships.
XDM entities gain inline action menus and support for deleting schemas, classes, field groups, and data types not used by datasets or enabled for Profile.
Once a schema has a dataset, breaking edits such as field renames, deletions, type or class changes are blocked; additive changes remain allowed.
Admins can define default property values that auto-populate on record creation across manual entry, workflows, and APIs.