Changelog

We have released the Optimization SDK, a new developer toolkit for integrating Contentful Personalization and Analytics across web and server applications from a single foundation.

The Optimization SDK includes:

• @contentful/optimization-web: Browser SDK for personalization, analytics, and consent management.
• @contentful/optimization-node: Server SDK for server-side rendering (SSR).
• @contentful/optimization-react-web: React integration with providers, hooks, and router adapters.
• @contentful/optimization-nextjs: Next.js integration for SSR, hybrid rendering, and client-side tracking.
• @contentful/optimization-core: Core SDK.

The Optimization SDK simplifies implementation and helps you get up and running faster. It provides:

• A unified SDK experience across web and server applications.
• Built-in support for server-side rendering, including Next.js.
• Less implementation code and faster setup.
• Built-in consent management, automatic interaction tracking, and preview support.

We recommend using the Optimization SDK for all new Personalization and Analytics integrations. Existing integrations built with experience.js continue to be supported.

For more information, see the Optimization SDK developer documentation and the open-source Github repository.

• The Contentful Remote MCP server has been moved out of Beta and into general availability.
• The authorization flow for the Remote MCP Server has been slightly changed. Going forward, users must add the MCP Config App to Space Environment pairs that they want to use the MCP server with.
• The MCP server is available to all customers without charge.
• You can find the Contentful Remote MCP app in the Contentful App Marketplace.

Starting July 21, 2026, Enterprise Observability now streams GraphQL API logs to your cloud storage, extending near-real-time log delivery to your GraphQL API traffic.

GraphQL logs are delivered as structured JSON files to your configured AWS S3, Google Cloud Storage, or Azure Blob Storage destination, using the same near-real-time, ~5-minute batching model as Delivery API (CDA) logs. From there, you can ingest them into your existing observability tools (Datadog, Splunk, Grafana, or similar) to debug query errors, monitor latency and response behavior, and correlate GraphQL activity with traffic from other Contentful APIs.

To configure GraphQL log delivery, navigate to Enterprise Observability in your Organisation settings, select GraphQL as a log type, and map it to a destination.

To learn more, see the Enterprise Observability documentation.

Organization admins can now filter CMA tokens by author and configure a maximum expiration limit for PATs, from a cleaner Token Management settings experience.

This makes it easier to review user-owned tokens during offboarding, security checks, and governance reviews, while also giving admins a more consistent way to enforce token lifetime expectations for personal access tokens.

The maximum token expiration policy applies to newly created PATs and does not retroactively change existing ones.

This update is available to all customers.

You can now see audience size estimations while building an audience in Contentful Personalization, making it easier to understand its potential reach before using it in campaigns, personalizations, or experiments.

As you configure your audience, preview metrics are displayed directly in the Rule builder on the Editor tab. These estimates update automatically whenever you modify your audience rules, including changes to traits, filters, or locations.

The available preview metrics include:

• Profiles in audience: An estimate of how many profiles match your audience definition.
• Estimated views: An estimate of the number of views your audience is expected to generate.
• Estimated conversion rate: An estimate of the audience's expected conversion rate.

For more information, see the help center documentation.

We have just released Bulk entry content operations that provide developers and platform teams an efficient way to manage multiple entries simultaneously, reducing the number of API calls required for bulk content management.

You can now perform the following entry operations in bulk through the Content Management API:

• Create, update, delete, and export, with a limit of 10,000 entries per job

Each job processes the entries asynchronously, returns per-entry results so teams can retry only what failed, and surfaces job status that teams can poll or receive via Webhook notifications. There are no custom monitoring layers needed.

For more information, see the Bulk entry operations and the Content Management API page.

Starting May 28, 2026, Enterprise Observability log streaming can now deliver Content Delivery API (CDA) logs to Microsoft Azure Blob Storage, alongside existing support for Amazon S3 and Google Cloud Storage. This enables teams running on Microsoft Azure to route Contentful API activity logs directly into their existing observability stack, with no need to route through a third-party destination.

For details, see the Enterprise Observability: Microsoft Azure Blob Storage setup

The Drive Integration app helps teams keep authoring and collaborating on the content changes in Google Docs, and then import finalized documents into Contentful as structured draft entries. It reduces manual copy-paste work by using AI-assisted field mapping, supported formatting, and image handling to move approved content into an existing Contentful content model.

The app helps content teams, editors, and admins manage long-form content more easily, without the need to manually copy-paste, format, and clean up content. Teams can select Google Docs they would like to import into Contentful, review suggested field mappings before import, skip content that should not be included, and continue publishing through their standard Contentful workflow.

Key features include:

• Google Docs Import: Browse Google Drive, select a desired Google Doc, and import it into Contentful as a draft entry.
• AI-Assisted Field Mapping: Review and adjust mapping suggestions so document sections can be placed into the right fields matching your existing Contentful content model.
• Supported Formatting And Images: Preserve common document structure, including headings, text formatting, lists, hyperlinks, embedded images, and tables where supported by the target field.
• Permission-Aware Drive Access: Each user connects their own Google account, and the app displays only Google Docs and folders they already have permission to access in Google Drive.

For more information, see Drive Integration app documentation.

We have created and released Contentful Skills, an open-source collection of agent skills designed to integrate Contentful guidance directly into your AI coding agent of choice, with an emphasis on Contentful Personalization.

These skills can teach your coding agent how to build on Contentful. Once installed, your agent starts providing context and codebase-aware guidance about SDK setup, Draft Mode, content migrations, and personalization directly within the workflow you already use.

The collection contains the following skills:

• contentful-guide – Explains the core concepts and routing. This is the entry point that helps the agent decide which skill to use for which question.
• contentful-api – Language-agnostic REST and GraphQL API reference - cURL examples for CMA, CDA, CPA, Images, and GraphQL.
• contentful-nextjs – SDK setup, content fetching, and Draft Mode previews for both App Router and Pages Router.
• contentful-migration – Writes and runs content model migration scripts.
• contentful-personalization – The flagship. Four interactive workflows in one skill: Onboard, Live debug, Doctor, and Develop.

For more information, see our blog post.

To accommodate our customers' needs, we have increased the maximum number of template versions per content model template from 200 to 1000.

For more information about content model templates and template versions, see the Help Center documentation.

Starting May 19, 2026, Enterprise teams can now manage key space setup steps through the Content Management API. With this release, you can list available licenses for an organization, check eligible licenses for a space, create a paid space with a selected license, unarchive a space with a selected license, and view or manage space add-ons for environments, content types, and records.

This removes a key manual step from multi-space provisioning and makes space setup easier to automate at scale.

This release is intended for developers and platform teams with org owner or admin permissions who manage many spaces through automation or internal tooling. It does not cover trial-space management or upgrade and downgrade flows in this release.

For more information, see: Create a space, Unarchive a space, Eligible licenses, Available licenses, Get space add-ons from a space and Allocate or deallocate space add-ons.

Starting May 19, 2026, Enterprise Observability log streaming can now deliver Content Delivery API (CDA) logs to Google Cloud Storage, alongside existing support for AWS S3. This enables teams running on Google Cloud to route Contentful API activity logs directly into their existing observability stack, with no need to route through a third-party destination.

For details, see the Enterprise Observability: Google Cloud Storage setup.

Starting May 19, 2026, AI Actions now support assignment and filtering configurations to help teams control where AI Actions appear and how they run. You can assign actions to specific content types and fields, configure default variable values, and reduce repetitive tasks for editors.

This release applies to AI Actions in Contentful. Existing AI Actions, content models, and editor workflows remain unchanged.

With these new assignment and filtering configurations enhancement, you can:

• Show AI Actions only where they are relevant by assigning them to specific content types and fields.
• Improve localization workflows by limiting translation actions to specific fields, such as translating only body content instead of entire entries, and pre-configuring which languages are available for translation.
• Support brand consistency by applying brand-checking actions only to fields like titles and content where messaging matters most.
• Reduce editor friction by preconfiguring and locking variable values such as locales or brand guidelines rules.

Learn more in our Help Center.

Starting May 19, 2026, AI Actions now supports Azure OpenAI as an additional bring your own model (BYOM) connector.

This allows organizations using Microsoft Azure to connect Azure-hosted OpenAI models directly into Contentful AI Actions. Azure OpenAI joins the existing supported AI provider connectors, including OpenAI, AWS Bedrock, Google Gemini, Google Vertex AI and custom model connectors.

Once configured, Azure models can be used in AI Actions for generation and validation workflows.

Learn more in our Azure connector setup guide.

The Google Analytics 4 app now helps editors view page performance metrics directly inside the Contentful entry sidebar, while keeping analytics connected to the right entry even when pages use complex URL structures or multiple URLs.

These updates help content teams understand how each entry is performing without leaving Contentful or manually checking Google Analytics 4. Teams can map entries using standard slug and prefix settings, and configure advanced URL patterns for localized segments, query strings, wildcard segments, and multiple rules per content type.

Key features include:

• Entry Performance Insights: View total or unique page views, trends over time, and deep links into Google Analytics 4 directly from the entry sidebar.
• Accurate URL Mapping: Connect entries to page paths using standard slug and prefix settings or advanced patterns built from short text, short text list, and integer fields.
• Holistic Page Analytics: Combine metrics across all matching Google Analytics 4 page paths and view included paths in the sidebar, so variants, locales, and multiple URLs contribute to a clear entry-level performance view.

For more information, see Google Analytics 4 documentation.

The Live Events dashboard is now available to all Contentful Personalization customers in the Optimization tab of the web app.

Live Events is a real-time event streaming dashboard that allows you to monitor the following incoming SDK events as they happen:

• Track events
• Component events
• Identify events
• Page events

It helps you quickly confirm that your setup is correct, tracking is working, and you can troubleshoot potential issues, as they occur. This helps you move faster and build confidence that your data is accurate from the start.

For more information about the dashboard, see the Live Events page in the Help Center.

Starting April 21st, 2026, Content semantics is available on all paid plans. This helps you work more confidently with your content by understanding what your entries are about beyond just the words they contain. This includes duplicate detection, contextual suggestions, improved AI-assisted workflows and access to a semantic (vector-based) representation of your content via APIs.

Content semantics is managed at the space-level and must be enabled via Organization settings before features are available.

This release applies to selected spaces where Content semantics is enabled. Features are available in Contentful and Content Management API (CMA). Existing content models, entries, and workflows remain unchanged.

With Content semantics, you can:

• Avoid duplicate content by identifying entries that cover the same topics or ideas.
• Reuse the right content by suggesting relevant entries when you add references and suggested links in rich text to other entries.
• Improve content quality and consistency to scale by using Smart context in your AI Actions.

Learn more with our Help Center and Developer documentation.

Contentful now streams in near real-time API activity logs directly into your cloud storage, starting with Content Delivery API (CDA) logs delivered to AWS S3.

Enterprise Observability is built for engineering and platform teams who need visibility into how Contentful performs as part of their broader stack. Teams can now bring Contentful into the same dashboards, alerting workflows, and incident processes they already rely on.

With Enterprise Observability, you can:

• Stream CDA logs to your AWS S3 bucket every few minutes, without any manual export or polling.
• Ingest logs into the observability tools you are already using.
• Monitor delivery health programmatically via a dedicated status API, or receive email alerts when delivery fails.

To learn more, read our Enterprise Observability documentation.

Taxonomy data (concepts and concept schemes) is now available on the Content Preview API (CPA) at preview.contentful.com.

Previously, taxonomy endpoints were only accessible via the Content Delivery API (CDA) and Content Management API (CMA), requiring customers working with preview environments to combine multiple APIs. With this update, you can now retrieve taxonomy data using your CPA access token.

Why this matters

If you use taxonomy to organize content (for example, generating slugs or filtering by category) in preview environments, you no longer need to mix APIs. You can now use a single CPA token to access both draft content and taxonomy data, simplifying your setup and aligning with best practices.

To learn more, read our documentation.

The Operating Hours app helps teams manage weekly business hours through a purpose-built visual editor inside Contentful, while storing the final schedule as clean, structured JSON for flexible frontend use.

This app helps content editors, admins, and frontend teams manage schedules without relying on raw JSON, awkward field sprawl, or brittle content modeling workarounds. Teams can configure where the app appears, choose a 12-hour or 24-hour editing experience, and optionally prefill default hours to match their operating model.

Key features include:

• Visual Weekly Schedule Editing: Editors can manage hours for each day of the week with a clear, guided UI.
• Flexible Day-Level Controls: Supports multiple time slots per day, closed days, and 24-hour operation so teams can model real-world schedules like split shifts, lunch breaks, and weekend variations.
• Structured JSON Output: Stores hours in a predictable JSON shape that is easier for frontend teams to render consistently across store locators, business pages, and other customer-facing experiences.
• Configurable Setup: Admins have control over which content types use the app, whether editors see a 12-hour or 24-hour clock, and what default hours should appear for new entries.