World is now on Opti ID! Learn more

Helén Alseby
Oct 29, 2013
  3894
(0 votes)

Scheduling several versions of content for publishing in EPiServer 7 CMS

If you are running an online campaign, you might want several banner ads with different time spans to be shown on the landing page. This can be done by scheduling multiple versions of the landing page in EPiServer 7.

Let’s imagine the scenario “Campaign 2013” with two banners that are to be visible one day each.

Example of a campaign with banner ads in EPiServer 7

Do the following:

1. In edit view, upload the banners on the Files gadget.

2. Create a new page, and select a page type that has the rich-text editor in the main body.

3. Drag the first banner to the editor area of the landing page.

4. Select Options > Schedule for Publish. Select date and time for the content to be published and click Schedule.

5. Select New Draft from Here and replace the first banner with the other one.

6. Select Options > Schedule for Publish. Select date and time for the content to be published and click Schedule.

Adding more features to your campaign

This example shows a simple scenario. If you are running several campaigns using the same landing page, you can have the banner ads as blocks and drag them to the page. These blocks can then be scheduled in multiple versions for publishing in a similar way as for pages. Schedule an A/B test for a block by using the Self-Optimizing Block.

An overview of page or block versions can be found in the Versions gadget, which can be added to the left or right panes in the editorial interface. There you can access versions that have been previously published, are in draft mode or will be published in the future.

Before setting the page to be scheduled for publishing, you can also add Personalization to your banners if you want. For example, banners that differ depending on whether certain pages have been visited on the website.

If you want to test the campaign pages in draft version before publishing, you can run an A/B test in EPiServer CMO.

Additonal information

Oct 29, 2013

Comments

Please login to comment.
Latest blogs
Make Global Assets Site- and Language-Aware at Indexing Time

I had a support case the other day with a question around search on global assets on a multisite. This is the result of that investigation. This co...

dada | Jun 26, 2025

The remote server returned an error: (400) Bad Request – when configuring Azure Storage for an older Optimizely CMS site

How to fix a strange issue that occurred when I moved editor-uploaded files for some old Optimizely CMS 11 solutions to Azure Storage.

Tomas Hensrud Gulla | Jun 26, 2025 |

Enable Opal AI for your Optimizely products

Learn how to enable Opal AI, and meet your infinite workforce.

Tomas Hensrud Gulla | Jun 25, 2025 |

Deploying to Optimizely Frontend Hosting: A Practical Guide

Optimizely Frontend Hosting is a cloud-based solution for deploying headless frontend applications - currently supporting only Next.js projects. It...

Szymon Uryga | Jun 25, 2025

World on Opti ID

We're excited to announce that world.optimizely.com is now integrated with Opti ID! What does this mean for you? New Users:  You can now log in wit...

Patrick Lam | Jun 22, 2025

Avoid Scandinavian Letters in File Names in Optimizely CMS

Discover how Scandinavian letters in file names can break media in Optimizely CMS—and learn a simple code fix to automatically sanitize uploads for...

Henning Sjørbotten | Jun 19, 2025 |