Overview
A View is a reusable, saved configuration for browsing an object type — Contacts, Content Instances, Orders, Documents, and more. It bundles what to show (the columns) with what to include (a saved filter), plus presentation (column grouping, labels, sort, timezone). Once saved, you apply a view to a table in one click, export it, or use it as the data source for a Journey Manager section. For the mental model, see Core concepts.Views is a shared feature. The per-module pages — Content Views, Commerce
Views, Customer Data Views — are the same feature surfaced in each module; this
is the canonical reference.
Where to find it
- The Views utilities — list and editor for saved views.
- A Views & segments picker on a module’s list table, to apply a saved view.
- Journey Manager sections, which bind to a view as their data source.
Properties
| Property | Type | Required | Description |
|---|---|---|---|
title | string | Yes | Name of the view. |
slug | string | Yes | Identifier — a view is addressable by id or slug. |
object_type | enum | Yes | The object type the view browses. |
type | string | Conditional | A sub-type scope (required for Content Instances and Orders). |
template_id | reference | Conditional | The Template scope (required for Content Instances and Documents). |
profile_ids | array | No | Profile scope (for Contacts and Organizations). |
timezone | string | No | Applied to the view’s date and time columns. |
object_fields | array | Yes | The selected columns and their display settings (groups, labels, order). |
filters | object | No | The saved filter — plus relationship filters — applied to the results. |
relationships | array | No | The relationship columns the view includes. |
Columns
A view’s columns can include:- Fields — the object’s own properties and Attributes.
- Relationship columns — fields or aggregates from related objects.
- Taxonomies & Tags — classification columns.
- Workflows — a record’s workflow and current step.
- Insights — computed aggregations.
Filtering
A view stores a filter that decides which records appear, including filters on related objects. The filter is the saved companion to the advanced-filter builder — you build conditions once and save them with the view. Results are ownership-aware: a Journey Manager only sees the records they own, while a super admin or Master sees everything (see Ownership).Exports
A view’s dataset can be exported (CSV / XLSX) as a background job, then downloaded.Behaviour & rules
- A view in use can’t be deleted. If a view backs a Journey Manager section or an export configuration, deleting it is refused until those references are removed.
- Removing an in-use column is blocked. You can’t remove a column that a Journey Manager layout page still uses — remove it from the layout first.
- Addressable by id or slug. Either resolves the view.
Seeds
View definitions travel between environments as structural Seeds — each is aviews item carrying the view’s full
configuration (columns, filter, and scope) in its data.
Governance & permissions
Only a super admin or Master can create, edit, and delete views.API access
Views have full CRUD, plus a query endpoint that returns the view’s filtered, paginated results and a support-data endpoint that returns the column headers. See the API reference.Related
Segments
Saved audiences, picked alongside views on list tables.
Object types
The object types a view can browse.