HomeDev GuideAPI Reference
Dev GuideAPI ReferenceUser GuideGitHubNuGetDev CommunitySubmit a ticketLog In
GitHubNuGetDev CommunitySubmit a ticket

Get started with DXP

Describes how to get started with Optimizely Digital Experience Platform (DXP). The onboarding process includes provisioning of environments and deployment setup. The onboarding steps are also described as part of the Cloud Accelerator Package.


Service provisioning

When your order is provisioned and activated, a technical contact associated with your order receives an email from Optimizely with the following information:

  • Default URLs for each of the environments  included in your order.
  • Contact information for support from Optimizely.
  • Login credentials are needed to log in to the Optimizely environments.
  • Contact information for support from Optimizely. 

After receiving this information, you are ready to onboard and deploy websites.

Deployment scenarios

  • Create a CMS site and deploy – I want to create a site based on the Optimizely CMS sample templatesand start development using Optimizely Digital Experience Platform.
  • Deploy a CMS site –I have an existing Optimizely CMS site that I want to onboard to Optimizely Digital Experience Platform and continue to develop it using this service.
  • Create a Customized Commerce site and deploy – I want to create a site with Optimizely Customized Commerce and start development using Optimizely Digital Experience Platform.
  • Deploy a Customized Commerce site – I have an existing Optimizely Customized Commerce site that I want to onboard to Optimizely Digital Experience Platform (DXP) and continue to develop it using this service.
  • Deploy code changes – I already use Optimizely DXP and have an existing site for which I want to deploy upgrades.
  • DXP self-deployment guide

Cloud Accelerator Package

The Cloud Accelerator Package is designed to increase working knowledge around Optimizely Digital Experience Platform (DXP). The package includes tools to help bridge technical and operational gaps and ensure a firm onboarding and deployment process.

Onboarding process

This section shows the components of Cloud Accelerator.

1. Technical overview – kickoff

When an order is provisioned, and you have received the service provisioning information from Optimizely, a Customer Success project manager sets up a kickoff meeting. During this meeting, you review DXP services, roles and responsibilities, and steps to develop and launch to Production. Information also includes expectations for communication, processes, and deadlines.

About DXP

In Optimizely DXP, a Web App is a solution built on the Optimizely platform and operating as an Azure Web App including an SQL Database, a BLOB storage, and an Optimizely Search & Navigation index. See Development considerations.


Separate environments ensure that your websites have developed and tested content before it is viewed in public. See also Environments.

  • Integration environment – Involves the process of moving code and content between environments, such as from Development considerations to preproduction (UAT) to production, as part of a continuous deployment process. You can deploy Optimizely solutions using methods and tools supported by most development environments.
  • Preproduction environment – A staging website where you test and assure the quality of content before it is transferred to the production environment.
  • Production environment – The live, public website where editors and visitors interact with your website.

Elastic auto-scaling occurs when performance criteria are exceeded. There is no set number of servers, CPUs, or memory; extra allocation is provided when needed. If a sudden spike in activity occurs, capacity scales up quickly and scales back slowly as demand ebbs.



To ensure seamless operation during upcoming campaigns or marketing events with anticipated high site traffic, you should open a proactive Support ticket 3 to 4 weeks in advance to give Optimizely time to assess your campaign's requirements and ascertain if supplementary resources are necessary for optimal performance.

A copy of the content called a "slot" is created during deployment. Configuration transforms are applied to the slot, and when it is verified, it is swapped with the content on the website for seamless interaction. See Deployment process.

2. Training

Developing for the DXP_is a one-day training course where two seats are included with your Cloud Accelerator Package purchase. Persons attending this course should have skill equivalent to _CMS Development Fundamentals. See Optimizely Education Services.

3. Implementation and load test monitoring

Deployment to Preproduction provides the opportunity to load test and validate sites before going live. Through the DXP Management Portal, you can access self-service functionality for deploying between environments. Features include:

  • One-click deployment
  • Configuration transforms
  • Validations when deploying
  • Maintenance page
  • Deployment progress and details
  • Error handling and logging

See DXP self-deployment guide.

Deployment scenarios

See Deploying and DXP self-deployment guide.


Review these recommendations:

4. Go Live Certification

Before deploying to Production, Optimizely ensures that everything on the following checklists is completed as part of the Go Live Certification.

Optimizely Managed Services task checklist

  • Set up Pingdom monitoring.
  • Set up Application Insights monitoring.
  • Enter Reporting Pingdom and Application Insights CIs in the Omni tracker.
  • Add the URLs for the above-created Pingdom alerts to the Zen Desk Pingdom Alerting CI App.
  • Verify Application Insights is gathering and displaying data.
  • Verify proper setup of the local cache before Go Live.
  • Ensure auto-scaling is configured based on load test results.
  • Ensure a proper number of default instances is configured based on load test results.
  • Ensure a proper App Service plan is configured based on load test results.
  • Ensure BLOBs are stored in the Azure storage account and not in AppData.
  • Validate that SSL bindings are set up if required.
  • Validate CDN is properly configured to receive traffic.
  • If required, validate that the VPN is properly set up.
  • Ensure DNS mapping verification is complete.
  • Check the site with Host entry before DNS is mapped before Go Live (one working day in advance).
  • Ensure application and system logging are enabled in the production environment and point to the appropriate BLOB containers (log-events and log-web).
  • Verify that the cloud services packages are installed to configure for DXP.
  • Ensure the website and cloud services have the starting instance count configured correctly and auto-scaling is set up and properly configured on production.

Partner or developer task checklist

DNS provider task checklist

  • Reduce Time-to-Live (TTL) to 5 to 10 Minutes. This should take place several days before Go Live.
  • Enter appropriate Go Live DNS records to cut over live traffic to the Microsoft Azure DNS app service.

Back-up and restore management

Optimizely provides redundancy precautions; see also Failover.

  • Content Database
    • Transaction log back-up every 5 minutes
    • Full back-up hourly
    • Point-in-time restore up to 35 days in the past
  • Configuration and code
    • Entire application back-up every 24 hours
    • Configuration backup on the same schedule
  • Azure Storage Accounts (BLOBs)
    • Geo-Redundant

5. Go Live Support

Optimizely's Customer Success team provides support throughout onboarding until your site goes live. During onboarding, copy your onboarding Customer Success project manager on communications to ensure prompt assistance.

Responsibilities from Optimizely DXP Support and Partner or Client Management:

Optimizely's Support team is available throughout the onboarding process and after the launch of your website. Optimizely Managed Services Service Desk will support these service requests during business days:

  • Non-standard deployments.
  • CDN configuration changes.
  • Placing IP addresses on the allow list.
  • URL aliasing.
  • DNS changes.
  • Adding or removing user access.
  • VPN configuration.

Contact information

DXP Dashboard

The DXP Dashboard provides an overview of your site's usage and performance. It includes self-service capabilities as part of your DXP, access to data about usage, and availability for components associated with your subscription.

Related topics



Password self-reset is disabled. Email  customer support to reset a password for you.



When using the Optimizely World website for the first time, you will need to register.

Password self-reset is disabled. Email customer support to reset a password for you.