Terminology

Term

In CX Enterprise and this guide

Other common Adobe usage

The unified web experience at experience.adobe.com where you open marketing applications, set preferences and notifications, and reach shared interface services (for example, Customer Attributes and Audience Library). Formerly Adobe Experience Cloud.

Not the same product as Adobe Experience Platform (customer data infrastructure, sandboxes, datasets). Not Adobe Creative Cloud (design and media apps).

Appears when you connect data collection, identity, or platform agents to your solutions; some navigational search and AI features are Platform-backed.

A data and orchestration platform. Do not use “Experience Platform” when you mean the CX Enterprise shell or home page.

Where Help and in-product links send you for documentation, tutorials, learning playlists, release notes, and community context for Adobe solutions. Start at Experience League home.

Complements the Adobe Help Center, which emphasizes account, plan, billing, downloads, and cross-product troubleshooting for individuals and teams. Use Help Center for password resets, plan changes, and similar tasks; use Experience League for product how-to content.

In-product assistants and orchestrated agents described in this guide’s AI topics; access and credits depend on product entitlements.

Other Adobe surfaces (for example, Firefly or Express) use “AI” features with different scopes and policies.

Your IMS organization: the boundary for enterprise licensing, user directories, SSO, and Admin Console administration in CX Enterprise. See Organizations and account linking.

Not an Analytics report suite, a Target property, or an Experience Platform sandbox (those are product-specific containers).

Enterprise control plane at adminconsole.adobe.com for users, product profiles, and identity; linked from CX Enterprise Administration topics. See User and product management.

Different from in-product admin inside each app (for example, Analytics admin tools or Journey Optimizer permissions screens).

A license bundle in Admin Console that grants access to a product or capability; users must belong to a profile to be entitled. See Manage products and profiles.

Not interchangeable with every in-product “workspace,” “container,” or “property” name; those vary by solution.

Connecting an application login (for example, Analytics or Target credentials) to your Adobe ID for the organization so services recognize one user. See Organizations and account linking.

Not the same as directory sync, SSO, or federation setup (those are org-wide identity decisions in Admin Console).

The persistent visitor identifier used across solutions; often deployed with tags or Web SDK. Still commonly referenced as Experience Cloud ID or MID in older Analytics discussions. See the ID Service overview.

Distinct from a single app’s legacy cookie name or from Experience Platform identity graph concepts, though they can relate in an implementation.

CRM or enterprise attributes you upload and map for use in Analytics, Target, and related workflows via the People service. See the Customer Attributes topics.

Do not equate with Audience Manager traits alone or with every Real-Time CDP profile field without checking the product boundary.

CX Enterprise UI to compose and share audiences across integrated applications.

Audience Manager and Target also use “audiences,” but segmentation rules and destinations differ by product.

Segment (Analytics)

A rule-based audience definition you can build in Adobe Analytics and, when supported, publish toward shared audiences.

In Audience Manager, segments combine traits; naming overlaps, but implementation is not identical. In Target, “audiences” replaced older “segment” labels in many places.

Shared folders and files for collaboration between CX Enterprise marketing workflows and approved Creative Cloud users. See Assets overview.

In Creative Cloud, “assets” usually means design files (PSD, AI, INDD). Same word, different sharing and governance model.