--- canonical: https://amplience.com/developers/docs/knowledge-center/key-terms/ title: Key terms description: A list of commonly used and key terms used across the Amplience product set, including Dynamic Content, Content Hub, Dynamic Media and Account Management. defined_terms: - term: "Account structure" description: "The combination of organizations, hubs and repositories in which content is stored for use with Dynamic Content." - term: "Asset" description: "A file that has been uploaded into Content Hub, categorized into asset types according to the file type." - term: "Asset library" description: "The collection of all assets available within the Amplience platform, accessible via Content Hub and the Dynamic Content Assets tab." - term: "Asset store" description: "A level of organization above folders and sub-folders for assets in Content Hub." - term: "Asset type" description: "A category assigned to a file when uploaded to Content Hub, for example image, video or text. An asset may be published dynamically, statically or both." - term: "Content Delivery API" description: "The Amplience next-generation Content Delivery API (Content Delivery v2), used to retrieve published content items and slots." - term: "Content form" description: "The area within Dynamic Content where you view, add and edit information for content items and slots." - term: "Content Hub" description: "The Amplience application used to manage assets such as images and video." - term: "Content id" description: "The unique identifier used by the Content Delivery API to identify a content item." - term: "Content item" description: "A piece of content created for consumption by users, for example a banner, based on a content type." - term: "Content library" description: "The area within Dynamic Content where you view and manage content and slots across repositories and folders in a hub." - term: "Content preview app" description: "A representation of how content will appear on your website or app at a particular point in time." - term: "Content type" description: "A template defining how content should be structured, created by registering a content type schema on a hub." - term: "Content type schema" description: "A JSON Schema definition that describes the structure and format of a type of content to be created in Dynamic Content." - term: "Delivery key" description: "A string of up to 150 characters assigned to a slot or content item, used instead of the content id to retrieve content via the Content Delivery API." - term: "Edition" description: "A collection of content scheduled to be published at a specified time, often representing a set of updates for a specific campaign purpose." - term: "Edition status" description: "A visual indicator of an edition's state: draft, scheduled, expired or published." - term: "Event" description: "Defines the start and end dates of a scheduled campaign and groups together the editions of content for that campaign." - term: "Gravatar" description: "A Globally Recognized Avatar used to represent Amplience users within the platform, based on their registered email address." - term: "Hub" description: "The space within Dynamic Content in which content is produced and scheduled, containing multiple repositories." - term: "Linked content" description: "A content item that contains links to other content items, such as a carousel linking to banner slides." - term: "Locale" description: "An ISO standard combination of a mandatory language code and an optional country code, used for localization in Dynamic Content." - term: "Localization" description: "The process of making content relevant for different regions. Dynamic Content supports field level localization and content item localization." - term: "Mime type" description: "A media type that indicates the nature and format of a file. The Amplience platform supports a range of MIME types for uploaded assets." - term: "Mixin" description: "A reusable part of a schema that allows the same data structures to be used in multiple content type schemas." - term: "Organization" description: "A top-level entity within which Dynamic Content hubs and repositories exist." - term: "Organization member" description: "A user who belongs to an organization and can be assigned roles giving access to hubs and repositories." - term: "Partial" description: "A form of mixin — a schema containing only a definitions section whose definitions can be reused across multiple schemas." - term: "Permissions" description: "Controls used to manage user access and actions in Dynamic Content, implemented through roles." - term: "Repository" description: "A collection of content within a Dynamic Content hub, with associated permissions and content types." - term: "Role" description: "A predefined set of permissions allowing an organization member to perform specific actions within an organization, hub or repository." - term: "Schema drift" description: "When content type schemas for the same content items become out of sync across different hubs, potentially causing validation errors during migration." - term: "Scheduling criteria" description: "The rules that must be met before an edition can be scheduled: the start date must be in the future and there must be no content version conflicts." - term: "Scheduling error" description: "An error that must be resolved before an edition can be scheduled, such as a content version conflict or slot validation error." - term: "Scheduling warning" description: "A non-blocking condition shown when scheduling an edition, for example when two editions targeting the same slots are scheduled within one hour of each other." - term: "Slot" description: "A container for content representing an area of a website, app or other channel. Content is published to slots when an edition goes live." - term: "Slot library" description: "The list of slots available to add to an edition, stored in a repository configured for slot content." - term: "Snapshot" description: "A specific version of a content item as it appeared when added or saved to an edition, ensuring scheduled content is exactly what was previewed." - term: "Visualization" description: "A preview of a content item showing how it will appear, available in the Content Library and for slots in an edition." - term: "Visualization environment" description: "The environment within which content previews are displayed, specified in the hub settings." - term: "Webhook" description: "A mechanism for Dynamic Content to automatically send messages or data to a third-party system when a specified event occurs, such as publishing content." - term: "Webhook event" description: "A notification triggered when a specific action occurs in Dynamic Content, such as content being published or saved." audience: Business User date_published: 2022-12-01 date_modified: 2025-04-30 --- # Key terms ## A #### Account structure The combination of organizations, hubs and repositories in which content is stored for use with Dynamic Content. More about [account structures](https://amplience.com/developers/docs/concepts/account-structure/). ### Asset A file that has been uploaded into Content Hub. Assets are categorized into [asset types](#asset-type) according to the file types from which they were uploaded. ### Asset library The collection of all the assets available to you within the Amplience platform. The asset library can be accessed using Content Hub and the Dynamic Content Assets tab. More about [the asset library](https://amplience.com/developers/docs/user-guides/assets/locate/organize/). ### Asset store Used as a level of organization above folders and sub folders for assets in Content Hub. More about [asset stores](https://amplience.com/developers/docs/user-guides/assets/locate/organize/). ### Asset type A category that's assigned to a file when it's uploaded to Content Hub, for example, image, video, text. Depending on the asset type, an asset may be published, dynamically, statically or both. Refer to the full list of [supported asset types](https://amplience.com/developers/docs/knowledge-center/faqs/assets/#supported-asset-types). ## C ### Content Delivery API Our next generation [Content Delivery API](https://amplience.com/developers/docs/concepts/content-delivery) (sometimes referred to as Content Delivery v2). The previous generation of API is referred to as the original Content Delivery API. | Current names | Old name | | ------------------------------------------------------ | ---------------------- | | original Content Delivery API, Content Delivery v1 API | Content Delivery API | | Content Delivery API, Content Delivery v2 API | Content Delivery 2 API | ### Content form An area within Dynamic Content where you view, add and edit information for content items and slots. The content form is displayed from the content library. More about the [content form](https://amplience.com/developers/docs/user-guides/basics/dynamic-content/content-library/#the-content-authoring-experience). ### Content Hub The application in the Amplience platform that's used to manage assets. Also used as a generic term for where all assets, including images and video are uploaded to and stored in the Amplience platform. More about [Content Hub](https://amplience.com/developers/docs/user-guides/basics/content-hub/). ### Content id The unique id used by the [Content Delivery API](#content-delivery-api) to identify a content item. A content item can also be retrieved using a [delivery key](#delivery-key). ### Content item A piece of content that is created typically for consumption by your users, for example, a banner. Each content item is created based on a [content type](#content-type). ### Content library The area within Dynamic Content where you can view and manage the content and slots that have been created for repositories and folders in a chosen hub. Content can be viewed in grid or list view. More about [content library](https://amplience.com/developers/docs/user-guides/basics/dynamic-content/content-library/#the-content-library-window). ### Content preview app A representation of how content will appear on your website or app at a particular point in time. Previews can only be displayed for dates in the future. See [developing content previews](https://amplience.com/developers/docs/dev-tools/guides-tutorials/content-previews). ### Content type A template for how content should be structured. Each content type is created by registering a [content type schema](#content-type-schema) on a hub and associating it with a repository. Used by users to create content items and slots. A content type consists of the content type schema URL, together with a label and optionally an icon, card and one or more visualizations. See also [content type schema](#content-type-schema). ### Content type schema A schema that defines a type of content to be created, including its structure and format. Defined using the JSON Schema format and created using the schema editor or stored externally. See also [content type](#content-type). ## D ### Delivery key A string of up to 150 characters that can be assigned to a [slot](#slot) or [content item](#content-item) and used instead of the [content id](#content-id) to retrieve content. Available with our [next generation Content Delivery API](https://amplience.com/developers/docs/concepts/content-delivery), but not the original Content Delivery API. ### Dynamic Content hub The space within which content is produced and scheduled. Hubs are organized into repositories and folders. See [Hub](#hub). ## E ### Event Defines the start and end dates of a scheduled campaign, and groups together the [editions](#edition) of content for that campaign. Events usually represent a major campaign such as Black Friday or New Year sales. Editions are scheduled individually within an event. ### Edition A collection of content that is scheduled to be published at a specified time. Content can be added to slots in an edition or directly to an edition. Editions have a scheduled start and end date / time and often represent a set of content updates for a specific purpose. For example, a New Year sales event may include separate editions for teaser banners, a womenswear campaign and a free shipping promotion. ### Edition status A visual indication of an [edition’s](#edition) state shown in the Dynamic content edition window and scheduling tab. The edition status can be: draft, scheduled, expired or published. A newly created edition has a status of draft and is set to scheduled when it is scheduled for be published. Once the end date of an edition has passed, it is set to expired. ## G ### Gravatar Amplience users can be represented within the platform by their Globally Recognized Avatar. If a [gravatar](https://gravatar.com/) is registered for a user's email address, that profile icon is used rather than an icon generated using initials and colors. ## H ### Hub In Dynamic Content, the space within which content is produced and scheduled. Hubs can contain multiple [repositories](#repository). Customers may have multiple hubs and access permissions set for each hub. Users may be provided with access to one or more hubs. Content cannot be shared between hubs. In cases where content needs to be shared (between brands, for example), that content would need to be organized into multiple repositories within one hub. In cases where multiple brands do not share content, then multiple hubs could be used to maintain separation. You can define an endpoint for each hub to which content will be published. Multiple hubs may share the same endpoint, but the same hub cannot publish to multiple endpoints. ## L ### Linked content A content item that contains links to other items. One example is a carousel that contains links to one or more carousel slides or banners. The content items linked from the carousel are stored separately to the carousel itself and can be used in multiple pieces of content. See [Creating linked content](https://amplience.com/developers/docs/user-guides/produce-content/create/#creating-linked-content). ### Locale A locale is an ISO standard combination of a language code, which is mandatory, and an optional country code. Locales are used in both field level and content item [localization](#localization) in Dynamic Content. See [locales](https://amplience.com/developers/docs/user-guides/produce-content/localize/#locales). ### Localization The process of making content relevant for different regions and countries. Dynamic Content supports two types of localization: field level localization and content item localization. When using field level localization users add data for each [locale](#locale) within a single content item. With content item localization separate content items are created for each locale. See [localizing content](https://amplience.com/developers/docs/user-guides/produce-content/localize). ## M ### Member See [organization member](#organization-member). ### Mime type A media type (also known as a Multipurpose Internet Mail Extensions or MIME type) indicates the nature and format of a document, file, or assortment of bytes. The platform supports a range of mime types. More about [supported mime types](https://amplience.com/developers/docs/knowledge-center/faqs/assets#supported-asset-types). ### Mixin A reusable part of a schema, that allows you to use the same data structures in multiple places. More about [mixins](https://amplience.com/developers/docs/schema-reference/mixins/#introduction). ## O ### Organization A top level entity within which Dynamic Content [hubs](#hub) and [repositories](#repository) exist. More about [organizations](https://amplience.com/developers/docs/concepts/account-structure/#organizations). ### Organization member Each user who belongs to an organization is a member of that organization. Members can be assigned [roles](#role) that give access to an organization's hubs and repositories. More about [organization members](https://amplience.com/developers/docs/user-guides/manage-accounts/members/). ## P ### Partial A form of [mixin](#mixin). ### Permissions Used to control user access and actions. In Dynamic Content, an environment's permissions are implemented using [roles](#role). More about [permissions](https://amplience.com/developers/docs/concepts/permissions/). ## R ### Repository A collection of a particular type of data, such as content, that is available from Dynamic Content. Repositories are organized within a [hub](#hub) and each has associated permissions. This makes it possible to specify who can create and edit content in a particular repository. You can specify that a particular repository contains slots. This allows slots created within this repository to be shown in the slots library and added to editions. As you can control which content types are made available to each repository, it is possible to have multiple content repositories, each with a different set of content types available to use to create content. ### Role A predefined set of permissions that allow an organization member to perform specific actions for content in an organization, hub or repository. More about [roles](https://amplience.com/developers/docs/concepts/permissions/#roles-summary). ## S ### Slot A container for content, representing an area of a website, app or other channel such as an in-store display. A slot might represent an entire page of your website, or a particular area of the page. Content is scheduled by adding slots to an edition and choosing the content to be published to these particular slots. When an edition goes live, the chosen content will be published into the specified slots. This allows content planners to control what content is published, to what location and at what time. You can also add content directly to an edition without using slots. See [Slots](https://amplience.com/developers/docs/dev-tools/guides-tutorials/slots). ### Slot library The list of [slots](#slot) available to add to an edition. The library can be opened when an edition is created, viewed or edited. Slots will generally be created when your integrations are set up or updated, and stored in a repository marked for that purpose. ### Snapshot A representation of a content item exactly as it appears at the point when it was added or saved to an edition for scheduling. A snapshot is a specific version of a content item. By creating snapshots, Dynamic Content allows planners to be certain that the content, including any linked items, they preview and schedule is exactly the version of the content that will appear when the edition goes live. See [snapshots](https://amplience.com/developers/docs/concepts/publishing-scheduling/#snapshots). ### Scheduling criteria The set of rules that determine whether an edition can be scheduled. The edition start date must be in the future and the edition must not contain any content version conflicts. ### Scheduling error An error state that must be resolved before an edition can be scheduled. - Content Version Conflict: An edition cannot be scheduled if slots within that edition contain two different snapshots of the same content. - Slot validation error: An edition cannot be scheduled if it does not contain at least one valid slot. An empty slot may be treated as invalid depending on its definition. ### Scheduling warning A condition where an edition may be scheduled, but a warning is shown to let you know about possible unexpected behaviour. One example is possible overlapping content: If two editions are scheduled to publish content within one hour of each other, you will be warned that, if the editions share the same slots, content may be overwritten. ### Schema drift When content type schemas for the same content items become out of sync with each other across different hubs. If you attempt to use the CLI tool to migrate content items where there is schema drift, validation error may prevent migration. In this case, content items can be migrated by ignoring schema validation. See [Steps for migrating content](https://amplience.com/developers/docs/dev-tools/cli-tool/copy-import-export/#considerations-for-migrating-content). ## V ### Visualization A preview of a content item. Visualizations are available for content in the Content Library and for content added to slots in an edition. To use visualizations a default visualization environment must be set in a hub’s visualization settings. See [developing visualizations](https://amplience.com/developers/docs/dev-tools/guides-tutorials/visualizations) and [viewing visualizations](https://amplience.com/developers/docs/user-guides/produce-content/visualize/). ### Visualization environment The environment within which content previews are displayed. This environment is specified in the hub settings window and will generally be set up at the beginning of a project. ## W ### Webhook A mechanism for Dynamic Content to automatically send messages or data to a third party system when a specified event occurs, such as publishing or saving content. More about [Webhooks](https://amplience.com/developers/docs/integrations/webhooks/) ### Webhook event A notification that is triggered when a certain action occurs in Dynamic Content. Developers create webhooks that subscribe to selected webhook events. See [webhook payloads](https://amplience.com/developers/docs/integrations/webhooks/payloads) for the supported webhook events and sample payloads.