CXF object and module names are kept in English across all languages
(Activities, Workflows, Contacts, Orders, Engagement Funnels, …). Each term below
links to its full reference page.
Core
| Term | Definition |
|---|
| Object types | The identifiers for the kinds of objects in CXF — the foundation for attributes, endpoints, schemas, and seeds. |
| Properties | The fixed, built-in fields CXF defines for an object — its base structure, which can’t be added, renamed, or removed. |
| Attributes | Typed, validated custom fields you add to an object; single or grouped, and scoped by Template or Profile. |
| Taxonomies | A classification system of multiple, hierarchical, localized taxonomies, restricted per template or object type. |
| Tags | Flexible, global labels you assign to objects for organization and discovery, with optional hierarchies. |
| Custom Relationships | No-code, bidirectional links between any two object types, with configurable cardinality and optional pivot fields. |
| Workflows | Tracks a record through the ordered steps of a business process, with checklist items and rotting alerts. Surfaced per module (Content, Customer Data, Commerce). |
| Hierarchies | A parent-child tree that automatically maintains each record’s order and path. |
| Archive | Reversible deletion that hides records from normal listings while keeping them recoverable. |
| Activities | Collaborate on any record with comments, tasks, and approval requests in a threaded feed. |
| Bookings & Schedules | Appointment scheduling where hosts publish availability and accept bookings under automatic rule enforcement. |
| Ownership | Assigns users as owners or followers of records to control who can see and change them. |
| Views | Reusable saved configurations for browsing an object type — which columns to show, which records to include, and presentation. Surfaced per module. |
| Log | The audit trail of who did what to which record, with field-level before/after diffs. |
Content
| Term | Definition |
|---|
| Content Template | The blueprint defining a content family’s type, custom attributes, authoring rules, and behavior. |
| Content Instance | A concrete record created from a Content Template, authored across versions. |
| Content Version | A single rendition of a content instance, identified by language × environment × status (draft/published). |
| DAM | Digital Asset Management — the library of files (images, video, documents, links) in folders, with variations and sources. |
| Publishing Window | A named, reusable time range that drives scheduled publication — publishing at its start and unpublishing at its end. |
Customer Data
| Term | Definition |
|---|
| Contact | The unified record of a person and the core Customer Data object; computed type ghost, lead, contact, or vendor. |
| Profile | A reusable bundle of attributes plus authoring defaults, attached to a record to extend and segment it; shared by contacts, organizations, and users. |
| Organization | A hierarchical entity grouping contacts (a company with departments and people), with profile-driven attributes. |
| Document Template | The blueprint for customer documents — contact-bound, attribute-driven records with no versions. |
| Document | A record created from a Document Template, bound to a contact. |
| Segment | A dynamic group of records of one object type, defined by a saved filter; membership updates automatically. |
Commerce
| Term | Definition |
|---|
| Order | A commercial transaction — a sale, purchase, transfer, invoice, or other type — that moves through statuses and updates inventory automatically. |
| Order Template | The blueprint for a kind of order — fixing its type and rules (workflow, allowed contacts and products, naming, taxonomies). |
| Inventory | Tracks how much of each item is in stock at each location, driven automatically by order status changes. |
| Price Lists | Named tiers or cost structures that organize the prices items sell at, with volume pricing across lists. |
| Payments | Taking payment on invoices through payment methods, payments, and transactions, with refunds and contact balances. |
Orchestration
| Term | Definition |
|---|
| Engagement Funnel | A structured, multi-step interactive flow that guides a contact through data collection, decisions, and engagement. |
| Events & Automation | CXF’s event-driven engine — an Event Template unifies what triggers it with a visual automation flow that runs in response. |
| APIs Playground | A no-code environment to build and test reusable endpoints by mapping CXF operations to Contact API routes. |
| Bundle | An aggregation of multiple endpoint responses into one section-based payload, with per-section A/B and segment targeting. |
| AI Agent | A configurable, LLM-powered assistant with its own purpose, personality, and guardrails, reachable through a chat endpoint. |
| Conversation | Real-time, two-way messaging between a contact and an agent (human, funnel, or AI) across web chat and WhatsApp. |
| Journey Manager App | A custom, dashboard-style internal app assembled from reusable Sections and layout pages to navigate and operate any object. |
Docs explorer
| Term | Definition |
|---|
| Sitemap | A visual tool to map pages, sections, and components, linking CXF resources to each node. |
| Endpoint | A browsable HTTP reference for each endpoint you’ve built — request shape, parameters, ready-to-run cURL, and OpenAPI spec. |
| Schema | A read-only documentation view of your data model — the attributes and taxonomies that templates and profiles define. |
| Seed | Export/import of CXF objects across environments — structural seeds carry full fidelity one by one; instance seeds bulk-load template instances. |
Settings
| Term | Definition |
|---|
| Account / Organization | Account-level settings — organization identity and billing, license and plan, and the Users catalog. |
| Users | The catalog of people with access to your CXF; each has roles and profiles. |
| Usage | Analytics of your resource consumption, measured in CHIPS (Computed and Hosted Information Processed). |
| API Key | A key that authenticates calls to CXF’s APIs, optionally restricted by allowed URLs and IPs. |
| Integration | A connection to a third-party service — email, SMS, video, messaging, or AI — configured with its credentials. |