FAQs

General information

  • Yes, it is mandatory to have your IPB sites in Pegasus and for IPBs the deadline is end of 2015. We are ready to get your Tuborg, Somersby and Grimbergen sites onboard and Carlsberg will be ready after Q1 2015.
  • If you do not currently have a website for your IPB, it is not as urgent, though we would encourage you join as soon as you can.
  • It is not mandatory for LPBs, but we encourage and welcome you to get your LPBs on Pegasus.

The costs include:

  • Access to the Content Management System
  • Cloud-based hosting at Microsoft Azure
  • Analytics
  • On-going technical support
  • Maintenance of the servers with the latest patches and security updates.
  • Group enhancement on features within the Pegasus package

The local teams are responsible for all final assets (text, images, video, etc.) to provide a point of contact for communication, tests and release of final results and content upload.

There should not be an increase in your resource costs, as you will only need to upload content (no coding).

If you have concerns about the cost in your local market, please send an email to pegasus@carlsberg.com

About the Platform

It is flexible and you can adapt the pages to your needs. You can also choose to develop additional features, which would need to be scoped by the project team.

Yes, there is. We can check on specific languages for you.

Yes, it is optimized based on the device dimension.

Front-end templates will be developed for, and tested in, the newest version of the following browsers.

  • Internet Explorer
  • Firefox
  • Google Chrome
  • Safari
  • Chrome Mobile for Android
  • Safari for iOS

Older browsers will be supported, but not fully (the experience will be scaled back):

  • Internet Explorer 8, 9, 10 (note, IE8 support will be phased out during 2015)
  • Firefox (Mac/PC Latest stable version -1)
  • Google Chrome (Latest stable version -1)
  • Safari (Mac Latest stable version -1)
  • Mobile browsers, Android (2.3+, Chrome Mobile) / iPhone (iOS 5.0+, Safari)

Yes, the contents are smart phone optimized.

Yes, this is possible. You can make additional tabs/pages as needed.

IPBs: If you need to make changes using HTML and CSS that change the look and feel of the site, then the Global Brand Manager needs to be involved and the work needs to be additionally scoped. Changes to JS are not possible.

LPBs: There is flexibility regarding changes to CSS, JS and HTML but it could have an impact on the scope and cost of the project.  Please discuss your needs with the Pegasus implementation team at the start of the project. 

Yes, subpages can be created from the backend. Content can be shown in three levels right now. If more levels are needed, please contact the Pegasus team at pegasus@carlsberg.com

You can create campaign templates to get a new subsite to your brand site

Falcon Social is a communication platform built on social media management tools for engagement, publishing, and analytics. The Pegasus platform implements some of falcon API and read registered social channels and displays content in back office dashboard to import into the branded stile to display item over there.

All social content available through Falcon will be included in Pegasus. In Falcon, you will be able to pull pieces of content from the media storage.

Falcon is a separate service and so will continue to be a separate cost.

Social content is in Falcon and ready to share. Web content is in the media folder. You can shuffle through other countries’ sites at the footer of the home page on the sites.

Yes, you can manually upload these, however if you need it to be automated, then please contact the team at pegasus@carlsberg.com.

It depends upon how the custom feature will impact the existing system, as it would be implemented on the Pegasus platform, which affects all sites.

Group will make the decision whether to implement and to accommodate it in the back office.

Yes, you can still use the platform. You can control which product shots are displayed and only show the SKUs relevant to you. We can also control the URL.

All of the main up-to-date browsers, such as Firefox, Google, IE, and Safari. It may not work well with some older versions

A store locator is being built into the Carlsberg global site. Once that is ready, as it is built in Pegasus, the store locator will then become available for all the other sites set up in Pegasus.

Working in the platform

The age gate is interface for asking the user for their age in order to verify that they are of the legal drinking age and therefore allowed to visit the site.

There are 4 options:

- Birthday: Asks for birth year and verifies the user is of the minimum age, which was set in the back-office. If birth year is the same as the minimum year, it will then ask for birth month to identify the exact age for verification. It will further ask for birth date if the birth year and month are the same as the minimum

- Yes/No: This Type of age gate interface asks that you are of legal drinking age. The user answers yes or no.

- Inherits: This Type of age gate will inherit all age gate settings from a parent age gate setting.

- Off: This Type of age gate will stop asking age gate on site/instance.

Static content is a type of content repository and the Flow section of your site is populated from the content repositories.

For conventional purposes, all content which was created manually will be placed inside static content. The applicable content types are promo, social, social carousal and article.

Note: Article content is a special type of content only present in grimbergenbeer.com and somersbycider.com.

Dynamic content is one type of content repository and the Flow section of your site is populated from the content repositories.

For conventional purposes, all content which is generated automatically using Falcon Social will be placed inside dynamic content.

The applicable content types are promo, social, social carousal and article.

The structure of The Flow is defined at the global (brand) level - this means that it should only be administered by Tuborg's global brand managers, as the structure applies across all markets.

The business logic behind the structure uses fall-backs. This means that if there is no available content within a certain folder type, then it will look for content from the next type.

The fall-back logic goes from: Branded -> Static -> Dynamic

If content can't be found in Branded, it will look in Static, then if no content it will look in Dynamic.

Then the same fall-back logic is applied from Language level up to Global (root brand) level.  If content isn't found at Language level, it will look at Market level, then it will look at Global (root brand) level.

If you are looking to sort content items with The Flow, our present solution is to have items created within the Dynamic folder (at Language level).  This way you will be able to apply a sort order within the Dynamic folder

No, the site cannot be loaded when JS is disabled.

No, currently only YouTube video URLs or YouTube video IDs are allowed for playing videos.

You can restrict, for example, agencies' access rights regarding content, so that the brand team must give approval before content is uploaded.

You can put rights on content elements but anyone can use the content once it is published.

Support

For sites in progress, you should open a discussion in your project Basecamp site.

For live sites, please contact the Carlsberg IT service desk.

Please report it to support team via the Carlsberg IT Service Desk

It will be provided by the support team in your project Basecamp site. 

If login fails and your account is locked after multiple failed attempts, please contact the support team via Basecamp for sites in progress or the IT service desk for live sites. 

If you forgot your Password, please contact support team to request new one or reset your password. For sites in progress, you can report this in your project Basecamp. For live sites, please contact the IT service desk.

Either you have not been provided access to the back office or the site might be down or in maintenance mode. For sites in progress, you can report this in your project Basecamp. For live sites, please contact the IT service desk.