Identifies the unique record for the asset in Salesforce Marketing Cloud. This system-generated value is immutable and serves as the primary reference for all internal relationships, audit logs, and API operations. It links the asset to its associated metadata such as owner, category, and asset type, and is required for replication tracking and dependency resolution during publishing or enterprise sharing.

Stores the customer-defined key or external identifier (Id) for the asset. This human-readable key is unique within a business unit and allows developers or marketers to reference the asset programmatically through REST or SOAP API operations. Unlike the system-generated Id or ObjectId fields, this key maintains referential integrity during migrations or environment synchronization. When not provided, the system automatically derives it from the asset name.

Contains the system-controlled, read-only text string that globally identifies the asset object. Unlike the Id field, which represents the local record Id within a specific environment, this field remains consistent across services, API layers, and replicated versions of the same asset. It enables the platform to track and reconcile an asset's identity across business units, environments, and publishing workflows.

Specifies the display name that identifies the asset in the Content Builder module, the REST API, and automation tools. This value is defined by the user and used by marketers to locate, reference, and reuse assets across multiple campaigns. Renaming an asset updates its metadata but does not affect integrations that reference the CustomerKey.

Provides a human-readable explanation of the asset's content, purpose, or intended audience. This description improves search accuracy, filtering, and collaboration within shared libraries. It can be updated freely and is displayed in both the UI and API results to assist with documentation and compliance review.

Identifies the user or business unit that owns the asset. This value defines edit and publish permissions and establishes accountability within enterprise environments. Ownership metadata is propagated to shared business units to preserve audit traceability. Changing this value can modify access rights in approval or publishing workflows.

Displays the full name of the asset owner for visibility and collaboration. This value mirrors the user record that is associated with the OwnerId field and helps administrators coordinate updates and enforce brand stewardship policies.

Holds the email address of the asset owner for audit reports, approval notifications, and workflow communication. This field supports compliance by enabling direct contact with content custodians and updates automatically when the owner's profile changes in Account Settings.

Links the asset owner to their internal user record. This numeric Id verifies permissions when publishing or sharing assets and functions as a join field for ownership validation across enterprise business units.

Records the date and time when the asset was first created in Salesforce Marketing Cloud. This timestamp is automatically generated and cannot be modified. It supports reporting dashboards, content lifecycle analytics, and compliance audit trails to identify creation trends and authorship.

Identifies the user who originally created the asset. This Id persists even if ownership later changes and supports accountability in activity-based reporting or historical audits. It ensures that original authorship is preserved for governance and performance review.

Shows the full name of the user who created the asset. This information appears in system logs, API metadata, and collaboration interfaces, allowing reviewers to attribute original authorship during approval or migration processes.

Holds the email address of the user who created the asset. This address is used to identify the original creator in audit notifications or cross-business-unit requests. It remains static even if the creator's role or access level changes later.

Links the asset creation event to the specific internal user record. This Id enables precise permission validation, and it is referenced in governance reporting and automation scripts to attribute imported assets to valid users.

Captures the most recent date and time when the asset was modified. This value updates automatically upon any change to the asset's content or metadata. It underpins version tracking, synchronization, and rollback operations, helping administrators identify assets requiring review before publication.

Identifies the user who most recently modified the asset. This field provides traceability in shared environments and enables auditors to determine who performed the last update. It is referenced in version control processes to associate each revision with a specific editor.

Shows the name of the user who last modified the asset. This value appears in audit logs and the Content Builder details pane, informing collaborators of recent updates and supporting distributed review workflows.

Holds the email address of the user who most recently modified the asset. This address supports workflow notifications or change-request follow-ups and stays synchronized with user profile data to maintain audit consistency.

Links modification events to the user account that performed them. This Id connects the revision history to permission models, ensuring accurate accountability in compliance and quality-assurance reports.

Identifies the enterprise-level business unit that governs the asset. This value represents the root organization in an Enterprise 2.0 hierarchy and remains constant even when the asset is replicated or shared across subordinate units. In contrast, the MemberId field specifies the individual business unit that owns or manages the asset locally.

Stores the Marketing Cloud Member Id (MID) for the business unit that owns the asset. This value defines the operational context for editing, localization, and data governance. Whereas the EnterpriseId field identifies the overarching enterprise parent, this field determines ownership and access permissions within that unit and is evaluated alongside EnterpriseId to resolve sharing scope and publishing rights.

Defines the date and time when the asset becomes active or available for use. When no value is supplied, the asset is active immediately upon creation.

Defines when the asset expires or becomes inactive. After this date, the asset can no longer be used in new sends or automations but remains accessible for reporting. Used together with the ActiveDate field, it enforces lifecycle governance to prevent reuse of outdated content.

Specifies the format or media category of the asset (for example, HTML, Text, Image, or JSON). This field determines which rendering engine and delivery channels are supported and ensures compatibility between asset design and targeted output medium.

Identifies the asset's structural type definition within Salesforce Marketing Cloud. This system reference links the asset to internal metadata that controls supported properties, channels, and rendering logic.

Indicates the internal technical name of the asset type. This value is used in API filtering and classification, enabling automation scripts to determine processing rules for specific asset formats during import or export.

Provides the user-friendly display name of the asset type. This label appears in the Content Builder interface and reporting views to describe the content kind (for example, Email Template or Image File), helping users recognize content categories quickly.

Links the asset to the category or folder where it resides. Categories organize assets hierarchically for storage and access control and are evaluated when determining folder permissions and applying Content Builder filters for retrieval.

Displays the name of the category or folder that contains the asset. This value supports navigation and search within Content Builder's folder hierarchy and maintains consistency between UI and API folder structures.

References the parent category of the folder containing the asset. This value defines the hierarchical relationship between nested folders and supports inherited permissions and breadcrumb navigation.

Contains the main content of the asset. This field can hold HTML markup, JSON configuration, or text that is used to render messages and pages. The message compiler reads this field directly during send execution to generate personalized output.

Defines fallback design data that used when neither the primary Content nor SuperContent field is available. This field ensures a consistent layout by providing default visuals or placeholders and preserves rendering integrity in conditional-content assets.

Contains enhanced content that overrides the standard Content field during rendering. Typically used for localized or dynamic variations, this field allows targeted delivery of alternate layouts or messages when conditions are met.

Stores a Base64-encoded binary representation of a file that is associated with the asset. Supported media include images, documents, or templates uploaded to Content Builder. The file is validated for size and type according to the FileProperties field before distribution or publication.

Holds structured metadata about file-type assets, including file name, extension, size, and content type. These properties are generated automatically during upload and used to validate compatibility, enforce storage policies, and optimize asset delivery performance.

Contains the HTML markup that is used for the 'Forward to a Friend' version of the asset. This version renders when a recipient forwards the message using the platform's forwarding feature. This field preserves layout, branding, and personalization tokens where permitted to maintain a consistent experience across email clients.

Provides the plain-text equivalent of the 'Forward to a Friend' view. This version appears when a recipient's mail client or the forward flow supports text-only rendering. Including this view ensures accessibility and reliable delivery in environments that restrict HTML.

Contains the primary HTML that is used by the compiler to render the asset during message generation. This field can include layout elements, reusable blocks, and personalization tokens that resolve for each recipient. Maintaining valid, lightweight HTML improves rendering accuracy and deliverability.

Defines named content regions, or slots, within the asset's HTML layout. Each slot acts as a placeholder where blocks or dynamic content can be inserted during authoring or send compilation. Well-defined slots standardize layouts while preserving design flexibility.

References the base HTML template that governs the asset's structure and styling. The template determines available slots, shared components, and default formatting. Using consistent templates enforces brand standards and accelerates campaign creation.

Stores the preheader text that appears beside or below the subject line in many inboxes. This short summary gives recipients additional context and encourages opens. The compiler evaluates this text at send time, and marketers can edit it in Content Builder.

Specifies the subject line used for an email asset. The subject line directly influences open rates and must accurately reflect message content. This field can include personalization tokens that resolve during send execution.

Links the asset to an associated subscription-management experience. This connection enables recipients to manage preferences such as topics, frequency, and channels. Integrating assets with subscription centers supports compliance and reduces opt-out churn.

Holds the plain-text representation of the asset for recipients who use text-only mail clients or prefer simplified messages. This field conveys the same information as the HTML version and includes required compliance text. Providing both formats improves accessibility and deliverability.

Defines the configuration for the 'View as a Web Page' option in email assets. When this option is enabled, recipients can open the message in a browser to view a fully rendered version independent of client restrictions. This feature also aids troubleshooting and content review.

Specifies which view or template the compiler should use to generate the final version of the asset. This field directs the system to resolve the appropriate slots and content blocks for the selected channel. Using the correct source view ensures consistent presentation across automations and triggered sends.

Lists all content slots that are available within the asset. Each slot represents a defined region that can contain blocks or dynamic content during design. Establishing clear slot definitions provides structure and prevents layout errors.

Lists the content blocks that compose the asset. Blocks are reusable modules such as images, text, buttons, or dynamic content elements that are inserted into slots. Standardized blocks speed production and preserve brand consistency.

Specifies the minimum number of content blocks that are required for the asset to be considered complete. Authoring tools might enforce this rule to prevent incomplete designs and maintain layout integrity.

Specifies the maximum number of blocks that the asset can contain. This limit prevents overloaded layouts, improves rendering performance, and ensures a balanced design across devices.

Lists the block types that are permitted within the asset. Restricting allowed blocks maintains technical compatibility and enforces creative guidelines. Validation occurs during authoring and send compilation to ensure compliance with design standards.

Identifies the template that defines the asset's foundational layout and default styling. Templates establish reusable frameworks that simplify localization and seasonal updates while maintaining visual consistency.

Contains user-defined metadata fields that extend the standard asset schema. Custom fields capture workflow details, targeting notes, or reporting tags used during production. They appear in both the UI and APIs for automation and governance.

Stores a set of key-value pairs that represent dynamic asset data. These values can be accessed by AMPscript or personalization logic during message compilation. Maintaining concise, well-structured data improves performance and readability.

Lists the delivery channels through which the asset can be used (for example, 'Email', 'SMS', 'Push', or 'Social'). Declaring supported channels guides validation and prevents use of incompatible assets. Clear channel assignment streamlines content discovery for multi-channel teams.

Tracks the sequential version number of the asset. Each increment represents a published or saved milestone that supports rollback and approval workflows. Version tracking provides transparent change history for audit and collaboration.

A Boolean field that returns a value of 'true' when the asset is locked to prevent edits or deletion, typically during approval, publication, or governance review. It returns a value of 'false' when the asset is open for modification. This state integrates with Content Builder approvals to safeguard approved content during campaigns.

Defines the current workflow state of the asset (for example, 'Draft', 'Approved', 'Published', or 'Archived'). Status determines whether the asset can be used in sends and whether additional approval is required before editing. Consistent status management improves operational visibility and compliance.

Stores tags that are associated with the asset for filtering, search, and reporting. Tags help teams organize libraries by theme, campaign, or audience. Using standardized tags improves discoverability and reduces duplication.

Contains a mapping of business-unit Ids (MIDs) that are authorized to access or use the asset. This field ensures that shared content remains visible yet protected from unauthorized modification.

Defines the configuration rules for sharing assets across business units that have Content Builder Sharing enabled. This field controls how those assets behave once they are shared, whether they replicated, synchronized, or linked as read-only copies. These settings maintain enterprise-wide content consistency while preserving source control.