2026 Optimizely CMS 12 release notes
37 min
Follow this article to receive email notifications when new packages are available for Optimizely Content Management System (CMS) 12. Product packages are found on the Optimizely NuGet server and include the following products:
- DXP
Are you looking for the 2025 Optimizely CMS 12 release notes or the 2025 CMS (SaaS) release notes2025 CMS (SaaS) release notes?
Or release notes before January 2024 on the Optimizely World site?
You can find prior versions of user guides (2021 and older) and when functionality was released or deprecated at the following locations:
- Versioned user guides and release notes (2021 and older)Versioned user guides and release notes (2021 and older)
- Released functionalityReleased functionality
- Obsolete functionalityObsolete functionality
Release highlights
Date | Release | Type |
|---|---|---|
September 21 | Bug fixes | |
September 17 | Bug fix | |
September 8 | Bug fixes | |
September 1 | Bug fixes | |
August 31 | Enhancement | |
August 7 | Bug fix | |
Aug 5 | Bug fix | |
July 29 | DXP | Enhancement |
July 21 | Bug fixes | |
July 20 | Bug fixes | |
June 18 | Bug fix | |
June 10 | Enhancement | |
May 26 | Enhancement | |
May 22 | Bug fix | |
May 19 | Bug fixes | |
May 8 | Enhancements | |
May 5 | Bug fixes | |
April 28 | Bug fixes and enhancement | |
April 27 | Bug fix | |
April 24 | Beta feature | |
April 23 | Enhancement and bug fix | |
April 16 | Bug fixes | |
April 10 | Enhancements and bug fixes | |
April 10 | Announcement | |
March 30 | DXP | Enhancements |
March 26 | DXP | Enhancement |
March 13 | Enhancement | |
February 03 | Enhancement | |
January 28 | Bug fix | |
January 28 | Enhancement | |
January 23 | Enhancement and bug fixes | |
January 22 | Bug fix | |
January 20 | Bug fix | |
January 5 | Bug fixes |
August 14
Enhancement
Released the following tools in Optimizely Opal to help you manage your Optimizely Graph content in Optimizely Content Management System (SaaS), CMS 12 (PaaS), and CMS 13 (PaaS).
- graph_pinned_result – Manages pinned results and pinned result collections in Optimizely Graph.
- graph_synonyms – Manages synonyms in Optimizely Graph. Synonyms help you find content using alternative terms.
August 5—EPiServer.Azure 11.2.2
Bug fix
- CMS-50193 – Fixed an issue where service bus message consumption was slow under high load, which delayed content syncing across instances. The default PrefetchCount increased from 100 to 500 to improve service bus throughput.
June 10
Agent Visibility Analytics dashboard – Released the Agent Visibility Analytics dashboard in Optimizely AnalyticsAgent Visibility Analytics dashboard in Optimizely Analytics, which shows how AI platforms interact with your website so you can refine your content strategy for AI optimization. It draws on content delivery network (CDN) log data and Opal-generated insights, letting you monitor AI traffic patterns, see which AI platforms visit most often, and identify which pages attract the most AI attention.
April 24—Beta feature
Apply to join the Markdown for Agents for CMS 12 and CMS 13 beta on the Optimizely beta signup page.
- (Beta) Markdown for AI agents – Deliver a clean markdown version of your pages to AI agents at the edge, instead of full HTML. Because AI agents process markdown more efficiently than HTML, this reduces ingestion cost and improves the accuracy of AI-generated responses that reference your content. The feature does not affect the page experience for human visitors.
April 10—CMS major version policy
Active Development
All new product development is focused exclusively on the latest major version of CMS. No new functionality will be built for earlier major versions. The current latest version is CMS 13.
Optimizely actively monitors, triages, and fixes severe bugs and security issues for the current major version and one prior major version. The currently maintained versions are CMS 13 and CMS 12.
As part of this policy, Optimizely does not provide ongoing bug monitoring, bug fixes, security monitoring, or patch releases for older major versions (CMS 11 and earlier), except in cases involving severe security vulnerabilities raised by customers/partners. This approach allows Optimizely to continue investing in innovation and the long-term evolution of the platform while balancing the realities of maintaining the older versions of our software.
Support Policy
Optimizely will continue to provide support for all major versions of CMS for existing customers. Our support teams will work with customers to investigate, triage, reproduce, and provide guidance on reported issues, including security-related concerns. While customers may continue operating older versions of CMS, resolution options may vary depending on the age of the version, underlying platform dependencies, and technical feasibility.
CMS 13 represents one of the most significant releases for Optimizely CMS, with major investments in AI-powered capabilities, the new Visual Builder, Embedded DAM, performance improvements, extensibility, and modern developer tooling — all designed to support the next generation of digital experiences. We STRONGLY encourage customers to upgrade to the latest version to take advantage of these advancements.
End of Life
Optimizely does NOT enforce end-of-life through forced upgrades, disabled environments, or removal of access to older versions. Customers may continue using older major versions of CMS based on their business needs and migration timelines.
CMS Core
EPiServer.CMS.Core
September 8—12.24.2
Bug fixes
- CMS-55416 – Fixed the issue where opening a folder with a typical number of children, sorted alphabetically, became noticeably slower. The slowdown came from a performance optimization intended only for very large folders, such as the global assets root. That optimization also ran for ordinary folders sorted the same way. It now applies only to very large folders, so ordinary folders regain their previous performance.
- CMS-55615 – Fixed the issue where deleting a user or role was slow on sites with a large content structure. Deleting no longer scans the entire content tree to clear cached data. It now completes much faster.
- CMS-55934 – Fixed the issue where changing a List property's [CultureSpecific] setting did not update already-saved values for other languages. Other language versions of a page could show stale content after the change. They could also keep inheriting content from the master language when the property was meant to be independent. Changing the setting now updates existing content correctly in both directions. Content already saved with the incorrect setting before this fix requires a separate one-time update to display correctly.
July 20—12.24.1
Bug fixes
- CMS-53432 – Fixed an issue where content that had a ContentArea property nested inside a block list (PropertyCollection) failed to load and threw an ArgumentOutOfRangeException, making the content inaccessible in both edit view and on the website.
- CMS-53553 – Fixed an issue where a page could not be edited when one of its block list properties contained an empty reference value left behind by a deleted content item. The empty reference is now handled and displays as "Content not found," so editors can continue editing the page.
May 22—12.24.0
Bug fix
- CMS-52288 – Fixed NuGet security vulnerability warnings for MailKit and MimeKit that appeared in .NET 9 and later CMS 12 projects during package restore. The warnings occurred because the NuSpec dependency range allowed NuGet to resolve vulnerable older versions of these libraries. The NuSpec dependency range now specifies a minimum safe version, ensuring NuGet no longer resolves vulnerable versions.
April 28—12.23.3
Bug fixes
- CMS-43485 – Fixed an issue where the simple address URL lookup SQL query caused significant performance degradation on SQL Server.
- CMS-51529 – Fixed an issue where registering an unnamed client resource with dependencies caused a NullReferenceException on site startup.
January 22—12.23.1
Bug fix
- CMS-47283 – Fixed an issue where link validation warnings for XhtmlString properties were incorrectly displayed across all language versions of a content item, even when a broken link was present in only one specific language version.
CMS UI
EPiServer.CMS.UI
September 21—12.34.7
Bug fixes
- CMS-55030 – Fixed the issue where notification subscriber lookups ran one query per subscriber on sites using ASP.NET Identity. Notification processing slowed as subscriber counts grew. Subscriber lookups now use a single batch query instead.
- CMS-55293 – Fixed the issue where saving user display options in Swedish showed an incorrect confirmation message. The message stated the options had not been saved, when they actually had. It now correctly confirms the save succeeded.
- CMS-56030 – Fixed the issue where category and content-tree lookups through the Content Data API could take 30 seconds or more. The API no longer blocks a thread while waiting for this data, so it now responds without the added delay.
August 7—12.34.6
Bug fix
- CMS-54435 – Fixed an issue where the Project overview became slow or unresponsive in projects with a large number of items. The overview previously loaded every project item into memory to set the Publish project button's state, resulting in a heavy database query. Optimizely now calculates the button state using lightweight count queries, improving performance for large projects.
July 21—12.34.5
Bug fixes
- CMS-35016 – Fixed an issue where default values from an overridden SetDefaultValues method were not applied to blocks added to an IList property (for example, IList<Block>).
- CMS-53095 – Fixed an issue where upgrading the EPiServer.CMS umbrella package produced NuGet dependency version warnings because the CMS composition packages did not resolve to EPiServer.Hosting and EPiServer.Framework 12.24.0. The package dependencies now align so compatible versions are restored automatically, without manually pinning each package.
- CMS-51275 – Fixed an issue where a validation error indicator disappeared after you opened an inline block editor and clicked Cancel, even though the validation error was still present.
May 19—12.34.4
Bug fixes
- CMS-49311 – Fixed an issue where the Compare tool displayed empty properties or missing images. The issue occurred when you opened the comparison view or switched versions while data was still loading.
- CMS-49507 – Fixed an issue where you could not publish blocks from the quick edit dialog when a validator returned warnings. Warnings now behave the same as in the full edit view; only errors prevent publishing.
April 16—12.34.3
Bug fixes
- CMS-49002 – Fixed an issue where the Last changed by date in the user interface (UI) displayed an incorrect date when the user's browser time zone differed from the server time zone. The date now accurately reflects the server's time settings.
- CMS-48690 – Fixed the missing permission check in UsersController that allowed user deletion to succeed even when UIUserProvider.IsSupported() returned false for the delete action. Now, user handling is updated so that Delete has the same access control as Update and Create.
- CMS-49476 – Fixed an issue where tabs at the end of the tab bar in edit mode were inaccessible when a page type contained a large number of tabs. Now, you can navigate to any tab regardless of how many there are.
- CMS-50771 – Fixed the breaking change introduced in a prior minor release where the AcceptAntiforgeryTokenFromQueryAttribute class and its internal dependency AcceptAntiforgeryTokenFromQueryFilter were unintentionally removed from the public API. Both classes are now restored.
January 23—12.34.2
Enhancement
- Added a tooltip feature in CMS 12 that displays the names of active servers for each URL.
Bug fixes
- CMS-47914 – Fixed an issue where the ReadOnlyMiddleware was incorrectly redirecting health check endpoints, causing them to fail, particularly in failover applications. The health check path is now whitelisted in the middleware request validator to ensure proper functionality.
- CMS-47408 – Fixed an issue where a binary-breaking change in EPiServer.Cms.Shell.IContentExtensions.PreviewUrl prevented third-party plugins and add-ons from functioning correctly after upgrading EPiServer.Cms.Shell.UI from versions 12.20.0.0 to 12.33.5.0. This change, caused by the addition of an optional parameter, was addressed to restore compatibility.
- CMS-47134 – Fixed an issue where users could set their new password to their current password in the MySettings section, which was incorrectly accepted. The system now correctly displays a validation error, preventing the new password from being identical to the current one.
- CMS-46675 – Fixed an issue where you could not hide the AllowedTypes description (and now you can), providing you with more control over content type configurations.
- CMS-45964 – Fixed an issue where, when selecting content via a search component within a modal dialog for a ContentArea limited to a single content type (such as ImageData), clicking a search result would close the dialog without adding the selected content item to the ContentArea. Now, the selected content is correctly added.
- CMS-45741 – Fixed an issue where updating the content of a personalized inline block within a ContentArea could inadvertently overwrite the content of other personalized inline blocks in the same ContentArea. This fix ensures that changes to one inline block are isolated and do not affect others.
- CMS-43553 – Fixed an issue where the CMS UI's right panel or main content area would sometimes fail to stretch to full width, especially when opening multiple tabs rapidly. The layout now consistently maintains its intended full-width display.
- CMS-39989 – Fixed an issue where the old domain world.episerver.com was hardcoded in the UI for the feedback link and RSS Data fetcher, causing potential domain redirection problems. The domain was updated to world.optimizely.com.
CMS Cloud Platform
EPiServer.CloudPlatform.Cms
April 23—1.7.4
Enhancement
- Added configurable log sampling for Application Insights. You can now independently enable, disable, or sample database and Service Bus logs at a configurable percentage. This gives you finer control over which logs are indexed in Application Insights, reducing noise while preserving access to the diagnostic data you need. See Configure loggingConfigure logging for more information.
Bug fix
- Fixed the incorrect NuGet package dependency in EPiServer.CloudPlatform.CMS 1.7.3, which did not reflect the required minimum version of EPiServer.CMS.UI 12.33.3.
Content Delivery API
EPiServer.ContentDeliveryApi
April 28—3.12.7
Bug fix
- Fixed the NullReferenceException that occurred when retrieving a page with the Content Delivery API or syncing to Graph when an IList<PageReference> or IList<ContentReference> property contained an empty reference. Empty references are now filtered from the list, consistent with the behavior of the CMS edit UI.
January 28—3.12.6
Bug fix
- HAPI-2931 –Added support for Content Management API (CMA) to create content with any valid language codes, removing the previous restriction to OS-supported cultures. This allows for the creation of content in languages such as zh-CN (Chinese simplified) directly through CMA, even if not listed in CultureInfo.GetCultures().
January 20—3.12.5
Bug fix
- HAPI-2924 – Fixed an issue where special characters in the “Remaining URL” field of a LinkItem were not correctly encoded when returned by the Content Delivery API and Optimizely Graph.
CMP DAM in CMS
EpiServer.Cms.WelcomeIntegration
June 18—2.2.2
Bug fix
- CMS-53224 – Fixed a binary breaking change in the public DAMMetadata record. The OriginalAssetId constructor parameter, added in version 2.2.0, changed the constructor signature and broke binary compatibility. OriginalAssetId is now an init-only property, which restores the original signature. If you set OriginalAssetId, assign it as an object initializer property instead of passing it as a constructor argument.
April 27—2.2.1
Bug fix
- Fixed an issue where View in DAM asset replacement did not preserve editor constraints in the ContentArea and ContentReferenceList properties. The picker now applies asset type filters and folder scoping consistent with the standard replace flow.
April 10—2.2.0
Enhancements
- DAM metadata consistency – Improved consistency and availability of Digital Asset Management (DAM) asset metadata within CMS, ensuring that Description, FocalPoint, and Renditions data for images are now uniformly accessible with both the REST API and Optimizely Graph. This provides a more unified and reliable data experience, with all relevant metadata consistently saved in the CMS database regardless of the retrieval method.
- Cached metadata rendering – Added cached DAM asset metadata rendering support for templates. The DAM integration now reuses metadata stored in the CMS database to render assets without making extra calls to the CMP Graph API, improving page load performance. Three rendering methods are available:
- <dam-asset> TagHelper (recommended)
- RenderTagWithMetadata HtmlHelper
- IUrlHelper.DamAssetUrl extension for direct URL generation with optional rendition support (new)
- Asset tracking and cleanup – Enhanced DAM asset tracking and cleanup processes to ensure accurate management of deleted asset references. This improvement addresses previous limitations where rendition IDs were stored instead of asset IDs, and where public API methods for deleting or updating mapped identities were unavailable.
- AssetID storage – Implemented the storage of the primary AssetID within the metadata field when creating or updating mapped identities in tblMappedIdentity. This enables correlation of deletion webhooks (which carry the AssetID) with mapped identities, regardless of whether you initially selected a rendition or original asset.
- IDAMAssetService.DeleteByAssetId(assetId) endpoint – Added REST API endpoint for deleting mapped identity entries, which lets you remove orphaned mapped identities from tblMappedIdentity, preventing data inconsistencies. stale data, and inaccurate asset usage tracking.
- DAM Library picker – Added the ability to select multiple assets from the Optimizely DAM Library picker in a single operation. Editors can now add multiple assets to the Content Area and Content Reference List properties without repeatedly opening the picker, reducing friction when building content-heavy pages. The picker enforces minimum and maximum item limits configured on the property and provides live feedback during selection. You must also have EPiServer.CMS.UI 12.34.3 to access this feature.
Bug fixes
- CMS-49239 – Fixed an issue where the DAM asset picker did not display in the CMS editor due to an MSBuild target and item group name collision. Now, the target and item groups have package-specific names, resolving the conflict and ensuring proper module deployment.
- CMS-49316 – Fixed the issue where DamAssetInfo.Renditions was always null because renditions were not fetched when assetType was null. The rendition fetch logic now resolves the asset type from the API response when not explicitly provided, ensuring renditions are populated for all code paths, including the GUID-only overload of GetAssetMetadata and the DAM metadata scheduled job.
Optimizely Forms
September 17—EPiServer.Forms 5.10.10
Bug fix
- CMS-56207 – Fixed the issue where Optimizely Forms could rewrite every form property definition on every site restart, even when nothing had changed. On multi-instance sites, concurrent restarts could collide on these writes. An unhandled database timeout could then crash the site instead of failing gracefully. Startup now skips the write when a property definition already matches what is stored. The application now logs and skips a failure on one content type, so it no longer stops the site from starting.
July 21—EPiServer.Forms 5.10.9
Bug fixes
- AFORM-4786 – Fixed an issue where the Forms visitor data hidden element retrieved visitor data synchronously on an asynchronous call. Under load, this blocked request threads and could cause thread pool starvation and increased latency. Visitor data is now retrieved asynchronously.
May 5—EPiServer.Forms 5.10.8
Bug fix
- AFORM-4768 – Fixed the issue where sites failed to start due to a constructor conflict in EPiServer.Forms when using StructureMap for dependency injection after upgrading to CMS.Graph 4.3.1.
May 5—Optimizely.Cms.Forms 1.5.1
Bug fix
- AFORM-4767 – Fixed the issue where images stored in the global assets folder returned a wildcard hostname instead of the primary hostname when queried through FormContainer in headless Forms implementations.
March 13—Optimizely.Cms.Forms 1.5.0
Enhancement
- Added smooth deployment support for Optimizely Forms with Optimizely Graph. Form data is now preserved during Optimizely Graph index rebuilds, preventing data loss and ensuring forms continue to function as expected after activating smooth deployment.
January 5—Optimizely.Cms.Forms 1.4.2
Bug fixes
- AFORM-4730 – Fixed an issue where the delta synchronization job would fail when content was deleted, preventing users from successfully indexing content. The delta indexing job now runs as expected, ensuring content can be indexed without errors even after deletions.
- AFORM-4733 – Fixed an issue where the Optimizely.Cms.Forms.ContentGraph package was incorrectly attempting to index non-Form content, leading to an ArgumentException and indexing failures for regular content (pages, blocks, and folders). The Forms ContentGraph package now correctly processes only Form-related content, ensuring smooth indexing for all content types.
- AFORM-4734 – Fixed an issue where a NullReferenceException would occur during site initialization when EPiServer.Forms, Optimizely.Cms.Forms.ContentGraph, and Optimizely.ContentGraph.Cms packages were present, preventing the site from starting. Sites now initialize successfully with these packages installed.
Optimizely Image Library Service
EPiServer.ImageLibrary.ImageSharp
May 8—2.0.6
Enhancement
- Updated the bundled SixLabors.ImageSharp minimum version from 3.1.7 to 3.1.11, which patches a moderate-severity vulnerability. Reference EPiServer.ImageLibrary.ImageSharp 2.0.6 to take the patched dependency. See the upgrade package reference guidanceupgrade package reference guidance.
May 8—1.0.6
Enhancement
- Updated the bundled SixLabors.ImageSharp minimum version from 2.1.10 to 2.1.11, which patches a moderate-severity vulnerability. Reference EPiServer.ImageLibrary.ImageSharp 1.0.6 to take the patched dependency. See the upgrade package reference guidanceupgrade package reference guidance.
Optimizely Language Manager
EPiServer.Labs.LanguageManager
January 5—5.5.3
Bug fix
- LM-714 – Fixed an issue where the Learning Management (LM) system was using an outdated version (0.21.1) of the axios package, which contained a known vulnerability. Language Manager was upgraded to use axios version 0.22.0, aligning with the version used by CMS, to eliminate this security risk.
Optimizely MAI connectors
September 1—EPiServer.ConnectForMarketingAutomation 6.1.7
Bug fix
- MAI-2254 – Fixed an issue where connector credentials were removed after an Optimizely Digital Experience Platform (DXP) deployment or application restart when the MAICryptoKey was not configured. Credentials that cannot be decrypted are now retained instead of deleted, a warning is logged at startup when the MAICryptoKey is not configured, and affected connectors display the message Unable to decrypt credentials. Verify that the 'MAICryptoKey' is configured correctly in appsettings.json.
Optimizely Eloqua Connector
September 1—EPiServer.MarketingAutomationIntegration.Eloqua.5.1.2
Bug fix
- MAI-2253 – Fixed an issue where the Eloqua connector submitted a form to Eloqua twice. This occurred when an existing contact submitted the form without the Eloqua tracking cookie, such as after clearing cookies or when using a private browsing window.
Optimizely Marketo Connector
September 1—EPiServer.MarketingAutomationIntegration.Marketo.5.1.4
Bug fix
- MAI-2236 – Fixed an issue where pages with forms or content connected to Marketo failed to render when the Marketo API rate limit was exceeded. The Marketo connector now retries transient errors and returns an empty result instead of stopping page rendering when retries are exhausted.
Optimizely Salesforce Connector
September 1—EPiServer.MarketingAutomationIntegration.Salesforce.5.2.1
Bug fix
- MAI-2250 – Fixed an issue where saving a Salesforce connector submitted fields from both authentication flows, including hidden fields and duplicate keys. The connector now submits only the fields relevant to the selected authentication flow.
Optimizely Salesforce Connector
EPiServer.MarketingAutomationIntegration.Salesforce.5.2.0
May 26—5.2.0
Enhancement
- Added support for Salesforce External Client Apps using the OAuth 2.0 Client Credentials flow for the CMS 12 Salesforce connectorCMS 12 Salesforce connector. Customers whose Salesforce orgs do not support creating Connected Apps can now authenticate the connector using a Client ID, Client Secret, and My Domain URL. Existing Connected App configurations continue to work without changes.
TinyMCE
EPiServer.Cms.TinyMce
July 20—5.0.4
Bug fixes
- CMS-46672 – Fixed an issue where the TinyMCE editor did not receive focus the first time you clicked it in On-Page Editing mode. You previously had to click away from the editor and click it again before it gained focus.
- CMS-52767 – Fixed an issue on .NET 10 where the TinyMCE editor failed to load and XHTML string properties rendered as a plain text field. This occurred when EPiServer.CMS.UI.Core, EPiServer.CMS.UI.Admin, and EPiServer.CMS.UI.Settings were referenced as explicit package references.
DXP
August 31
Enhancement
- Added support for the Astro frontend framework – Optimizely now supports Astro in addition to NextJS. Pick the framework that fits your site. Astro supports static site generation (SSG) and server-side rendering (SSR). An Astro site uses the same code package and deployment workflow as a NextJS site. For SSR sites, add Incremental Static Regeneration (ISR) with a Redis cache and Optimizely Graph webhooksIncremental Static Regeneration (ISR) with a Redis cache and Optimizely Graph webhooks. Pages then refresh within seconds of publishing, without a redeploy. Astro requires Node.js 22.12.0 or later, and odd-numbered Node.js releases are not supported.
July 29
Enhancement
- Added the ability to apply app settings without a code deployment – You can now apply app settings and connection string changesapply app settings and connection string changes to a specific environment from the App Settings tab in the PaaS portal, without running a full code deployment. Optimizely reads the settings from Key Vault and pushes them to the web app, which restarts automatically to load the new values. This applies configuration changes in minutes instead of requiring a full deployment. Code deployments to the environment are blocked while the operation runs, and you cannot start the operation if another deployment to the same environment is already in progress. The portal shows the operation status and a link to the Apply Settings job.
April 28
Enhancement
- Added support for Incremental Static Regeneration (ISR), which lets you update individual pages without rebuilding your entire site. ISR reduces build times, improves performance for large or frequently updated sites, and reduces infrastructure load. See Next.js ISR caching and Optimizely Graph webhooksNext.js ISR caching and Optimizely Graph webhooks.
March 30
Enhancements
- Pageview metric – Updated the pageview reporting metric to align with billing dates instead of calendar dates. Pageview data in DXP now matches the Opti ID Admin Center, ensuring consistency across all reporting surfaces.
- How are my pageviews calculated? Pageview counts are aggregated from Application Insights and include traffic across all of your environments.
- Why do my pageview numbers look different than before? Optimizely transitioned from calendar-based reporting to contract-aligned reporting. This change ensures that what you see on your dashboard matches the usage data leveraged for billing. Previously, data was shown from the first to the end of each month. Now, your dashboard reflects your specific billing cycle (for example, March 6 – April 5).
- Availability metric – Updated the availability metric to use a more granular calculation method. The revised calculation provides more precise reporting.
- How is availability calculated? Availability is now calculated using a high-resolution, daily-weighted average. Optimizely measures uptime down to the second every 24 hours (86,400 seconds per day) to determine your daily percentage. Your monthly availability is then derived from the average of these precise daily snapshots.
- How does this new availability calculation benefit me? Optimizely moved to a granular, second-based calculation. This increased precision eliminates rounding discrepancies and gives you the most accurate view of your service level performance to date.
March 26
Enhancement
- Updated the database export user interface (UI) to improve clarity and usability. The previous Expired database file list has been replaced with a paginated view of database exports from the past 30 days, providing a more intuitive and consistent history of recent exports.
Optimizely Reporting
February 3
Enhancement
- Improved insights into the Crawl-to-Refer RatioCrawl-to-Refer Ratio with new comparison capabilities. You can view the crawl-to-refer ratio comparison between your selected timeframe and the prior period to understand how the ratio changes over time, and your optimizations or market shifts impact it.
January 28
Enhancement
- Expanded AI platform visibility in Crawl-to-Refer RatioCrawl-to-Refer Ratio. The dashboard now displays the top six AI platforms based on AI request volume, matching the top six entries in the AI-Agent Analysis table.