Glossary

Developer edition

An evaluation version of Dynamic Content.

Dynamic Content hub

The space within which content is produced and scheduled.

See Hub.

Content Hub

Where all assets, including images and video are stored in the Amplience platform.

Hub

The space within which content is produced and scheduled.

Hubs can contain multiple repositories. Customers may have multiple hubs and access permissions can be 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 organised 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.

Repository

A collection of a particular type of data, such as content.

Repositories are organised within a 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.

Development terms

Content Type

A schema that defines a type of content to be created, including its structure and format.

Content types are defined using the JSON schema standard.

Content types are added to hubs then associated with repositories. This allows you to create your own library of content types and share them wherever they are required.

Webhook event

A notification that is triggered when a certain action occurs in Dynamic Content. Developers create webhooks that subscribe to selected webhook events.

Planning terms

Event

An organisational grouping containing one or more editions.

Events have a start and end date and will usually represent a major campaign such as Black Friday or New Year sales. Editions are scheduled individually within an event.

While an event will generally represent a campaign, it can also act as a grouping to organise any collection of content changes, such as a website refresh, for example. Events can contain many editions, each consisting of content releases used for a specific purpose.

Events can optionally contain an attachment, which may be useful for including additional information such as a project brief and is currently specified using a URL.

There can be many events on your timeline.

Edition

A collection of content that is scheduled to be published at a specified time.

An edition contains one or more slots to which you add the content to be published.

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.

Editions can be scheduled to go live at the same time as each other or at different times, however different content items cannot be published to the same slot at the same time.

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.

Slot Library

The list of slots 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 to a slot using the content browser, or when it was saved to an edition in the production view.

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.

Edition Status

A visual indication of an edition’s state shown in the edition window and planning calendar.

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 it is scheduled for publication. Once the end date of an edition has passed, it is set to expired.

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.

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.

UI related terms

Planning view

The view in which events and editions are managed.

Users may choose to show events and editions in a calendar view or as a list. Each view provides equivalent functionality, so you can choose the most appropriate way to view, edit and schedule your events and editions.

Production view

The view in which content items and slots are created, edited and previewed.

Content created and edited in the production view can be saved to an edition to make it available in the planning view. The content can then be added to a slot within an edition and scheduled for publication when the edition goes live.

Content preview app

A representation of how content will appear on your website or app at a particular point in time.

Content previews are opened by choosing a date in the planning calendar and are displayed in a separate window.

You can create your own preview app that simulates your website or app and provides an accurate view of how your content will appear on the specified date. The preview can be as advanced as required and can even be a complete simulation of your web site, app or other delivery channel.

Previews can only be displayed for dates in the future.

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.

Visualization Environment

The environment that content previews are displayed within.

This environment is specified in the hub settings window and will generally be set up at the beginning of a project.

results matching ""

    No results matching ""