What's New in Arc XP

Release dates

• Sandbox - Tuesday, October 6, 2026
• Production - Thursday, October 8, 2026

Release summary

This release verifies more reader email addresses automatically and adds a guard to the upgrade flow.

• Login emails (forgot-password and magic-link) now verify the reader’s email address.
• Social sign-in now verifies the reader’s email address when the provider has already verified it.
• The upgrade flow now blocks another upgrade until the next billing cycle to prevent incorrect charges.

Verification from login emails

The forgot-password and magic-link login APIs now verify an unverified email address. Each one produces EMAIL_VERIFIED websocket and IFX events.

Verification from social sign-in

Previously, if a reader registered with an email and password and later signed in with a social provider using the same email, the social identity was linked but the account’s email stayed unverified. No EMAIL_VERIFIED event was produced.

Now, an unverified account is verified on social sign-in when all of the following are true:

• The provider reports that the email is verified.
• The account’s email is currently unverified.
• The provider’s email matches the email the reader registered with, ignoring uppercase and lowercase.

When this happens:

• The email the reader registered with becomes the account’s verified email.
• The password identity’s login identifier is updated to match.
• An EMAIL_VERIFIED user event, a broadcast, and a commerce:EMAIL_VERIFIED IFX notification are produced.

This applies to Google, Apple, and BYO-OIDC sign-in, and not to Facebook. Accounts that are already verified are not verified again, so you do not get duplicate events.

Upgrade flow

The GET /sales/public/v1/subscription/{id}/initializePriceUpdate/{pc} API now blocks another upgrade until the next billing cycle to prevent incorrect charges.

Users affected

Subscriptions developers

Action required

None

Release dates

• Sandbox - Wednesday, September 30, 2026
• Production - Wednesday, October 7, 2026

Release summary

PageBuilder Editor is now more reliable when page data can’t fully load. Pages open even when some information, like the published version or clipboard data, is missing or slow to load, and if something truly can’t load, customers now see a clear message with options to retry or go back instead of a spinner that never ends. Publishing is safer too: if the Editor can’t refresh a customer’s draft right after a successful publish, it preserves their work instead of losing it.

Users affected

All PageBuilder Editor users

Action required

None

Release dates

• Sandbox - Tuesday, October 6, 2026
• Production - Tuesday, October 13, 2026

Release summary

This release addresses the following items in Composer including

• We’ve addressed some performance issues in the Circulation Selector in stories
• 2 items in the rating content elements were previously disabled and are now working correctly
• We’ve fixed an issue that was causing “No Title Available” on some stories in Composer
• Notes no longer lose focus when users reply
• Power ups no longer display No Title set when not relevant
• We’ve addressed an issue where some metadata fields were editable in Read only mode
• We’ve addressed an issue where users were getting conflicting successful save and error saving notifications

Users affected

Composer users

Action required

None

Release dates

• Sandbox - Tuesday, October 6, 2026
• Production - Tuesday, October 13, 2026

Release summary

Photo Center now lets editors see and correct more of the metadata that photographers and wire services embed in their images, and keeps that metadata consistent when photos are downloaded for syndication.

New fields you can edit

• SEO Filename is now on the photo edit page (single and multi edit). When you leave the field it’s cleaned up automatically (accents and special characters removed) so it’s ready to use in Resizer V2 URLs.
• Four more IPTC fields are now read from uploaded images and editable in Photo Center: Writer/Editor, Category, Supplemental Categories and Urgency. Photo Center also reads Country Name when an image has no country code.
• Photo Center checks values against IPTC size limits before saving (for example, Category is a short code of up to 3 characters), so downloaded images stay valid.

New fields in photo ANS

Photos uploaded after this release may include up to four new fields in their ANS, filled in automatically from the image’s embedded IPTC data:

• additional_properties.iptc_caption_writer (Writer/Editor)
• additional_properties.iptc_category (Category)
• additional_properties.iptc_supplemental_categories (Supplemental Categories, a list)
• additional_properties.iptc_urgency (Urgency, a number from 1 to 9)

They appear whenever the uploaded image contains those IPTC fields, even if the fields are turned off in your image type settings. Existing photos only get them when a value is saved. address.country_name may also now be filled from the image’s IPTC Country Name when it has no country code. If you process photo ANS in your own systems, make sure they accept these new fields.

Choose what shows where

• Turn each new field on or off, and make it required, per image type in Settings > Image Types. They’re off by default, so nothing changes in the Photo Center UI until you enable them.
• Special Instructions, SEO Filename and the four new IPTC fields can now be shown on photo cards on the Photo Center landing page, through Settings > Image Metadata Card.

Downloads carry your edits

• Downloading a photo with replace=true writes your edits for the new fields into the image’s IPTC metadata. Values you haven’t edited stay as they were in the original file.
• New for API users: add writeXmp=true (with replace=true) to also write the same values into the image’s XMP metadata, so tools that read XMP see your edits too. JPEG only.

Users affected

Photo Center users

Action required

None. To use the new fields in the Photo Center UI, administrators must turn them on per image type in Settings > Image Types. If you process photo ANS in your own systems, make sure they accept the new fields.

Release dates

• Sandbox - Tuesday, October 6, 2026
• Production - Tuesday, October 13, 2026

Release summary

This release fixes an issue with Slack notifications in some Spanish sites where newly published articles were not triggering any Slack notifications in the designated channels. This has now been resolved.

Users affected

WebSked users

Action required

None

Release dates

• Sandbox and Production - Thursday, October 1, 2026

Release summary

This hotfix fixes the Bundle and Publish Activity records and the vertical markers that show them on the charts in the PageBuilder Performance dashboard. Customers can once again see when a bundle or publish activity happened and compare it against changes in their performance trends.

Users affected

PageBuilder users

Action required

None

Release dates

• Sandbox - Tuesday, September 22, 2026
• Production - Tuesday, September 29, 2026

Release summary

This release addresses a number of items in Composer including

• Read only mode no longer has an errant opacity over the story body text improving legibility and contrast of the text displayed
• Arc Automation notifications now have an X button to close the notification alert manually
• We’ve fixed an issue with the AI Assistant Style guide review where it was occasionally not applying the suggestions until running it multiple times
• Cloned templates are now respecting updated Primary Websites
• Stories no longer appear locked in Composer Search when another user is in Read-Only mode

Users affected

Composer users

Action required

None

Release dates

• Sandbox - Tuesday, September 22, 2026
• Production - Tuesday, September 29, 2026

Release summary

This release of the Video Player addresses the following items

• Playthrough defaults to enabled when embedContinuousPlay is absent
• Mux GDPR consent gate has been fixed
• Restore native HLS for Chrome on iOS that was causing an encode error
• Force HLS.js in all Chrome environments
• Theme handling fix that sets style/template defaults after theme is defined
• Scrubber / theme override support now exists in PoWaSettings
• There are no longer errors with PoWa players when loading multiple autoplay videos
• Thumbnails are now loading in Safari before auto play

Users affected

Video Player users

Action required

None

Release dates

• Sandbox - Monday, September 21, 2026
• Production - Monday, September 28, 2026

Release summary

Author Service now provides self-service Custom Fields management via a new Fields screen in the UI. You can see every default and custom field, filter by name or type, add a new custom field, and edit or delete. Four field types are supported: text, textarea, dropdown, and boolean (true/false).

See the Managing custom author fields guide for the full walkthrough.

The same functionality is available through a new v3 API: GET, POST, PUT, DELETE /fields endpoints. It returns the same response format as the View API and validates your input before saving it.

Users affected

Editorial admins who manage author profiles.

Action required

None

Release dates

• Sandbox - Wednesday, September 30, 2026
• Production - Wednesday, October 7, 2026

Release summary

PageBuilder Editor is now more reliable when page data can’t fully load. Pages open even when some information, like the published version or clipboard data, is missing or slow to load, and if something truly can’t load, customers now see a clear message with options to retry or go back instead of a spinner that never ends. Publishing is safer too: if the Editor can’t refresh a customer’s draft right after a successful publish, it preserves their work instead of losing it.

Users affected

All PageBuilder Editor users

Action required

None

Release dates

• Sandbox and Production - Thursday, September 24, 2026

Release summary

This release removed a fix for Lightboxes that was causing other unintended issues with lightboxes. We have removed the fix to fully address all issues with Lightboxes that may be occurring.

Users affected

Composer users

Action required

None

Release dates

• Sandbox and Production - Thursday, September 24, 2026

Release summary

PageBuilder Engine 7.2.1 is a hotfix for Engine 7.2.0.

It fixes a regression where a build would fail if a component’s output-type implementations declared the same custom field differently. Custom field conflicts like this are now resolved consistently and reported as a warning instead, matching earlier Engine behavior. No bundle changes are needed.

This release also includes two additional fixes:

• Private class methods compile again.
• Build failures are reported instead of hanging. A failing build could previously run all the way to the deployment timeout without indicating the cause. Failures now stop quickly and name the file, line, and build stage responsible.

Users affected

Customers who are currently on Engine 7.2.0 version.

Action required

If you’re on Engine 7.2.0, redeploy with Engine 7.2.1 (no customer code change needed)

Release dates

• Sandbox and Production - Wednesday, September 23, 2026

Release summary

Structured Content and Data Center 1.1 deliver capabilities we’ve heard most as feature requests from our early adopters: let records point at other content (Arc and your own custom schemas), give editors rich text formatting, and let teams create, manage schemas without API calls right in the UI.

• Reference fields: A record can now point at other records, stories, images, galleries, videos, and authors. The Content API resolves the reference and returns the target’s content inline, so a page pulling in a record gets the linked content in the same call. Editors pick targets from the same Photo Center and Video Center panels used in Composer, plus a story search and an author search built for this, and the record list is redesigned with one-click filters for status, website, and modified, published, and created dates. See Reference fields documentation for how targets, indexing, and validation work.
• Rich text: A new rich-text field type adds a proper editor: bold, italic, lists, and alignment. Content is sanitized against a fixed tag allowlist on save, and each field is capped at 0.5 MB. See Rich-text fields documentation for the full allowlist and the limit.
• Record usage tab: Open any record and see every story or record that references it, in one place, then republish them from there.
• Create and Manage Schema in the UI: Content types are now created and edited directly in Data Manager, with your organization’s searchable-field budget and usage shown in the sidebar as you work. Walk through it in the new Data Manager guide.

Users affected

Developers, Editorial

Action required

None

Release dates

• Sandbox - Monday, September 21 Delayed to Monday, October 5
• Production - Tuesday, September 22 Delayed to Monday, October 12

Release summary

Video Center now lets you schedule a publish for a future date and time, the same way you already schedule stories, photos, and galleries. When you publish a video, choose Later instead of Now, then set the date and time you want it to go live. You can reschedule or cancel a scheduled publish any time before it fires, and a new Scheduled Videos filter shows you everything that’s queued up but not live yet.

This works the same way in both the standard Video Center interface and VOD Edit Beta.

Users affected

Video Center users

Action required

None

Release dates

• Sandbox - Monday, September 14, 2026
• Production - Monday, September 21, 2026

Release summary

Search endpoints now return matching count and data results when using _sourceInclude with distributor. Previously, results could differ depending on whether type was also included. Both configurations now return consistent results.

Users affected

All

Action required

None

Release dates

• Sandbox - Tuesday, September 22, 2026
• Production - Tuesday, September 29, 2026

Release summary

This release addresses a number of items in Composer including

• Read only mode no longer has an errant opacity over the story body text improving legibility and contrast of the text displayed
• Arc Automation notifications now have an X button to close the notification alert manually
• We’ve fixed an issue with the AI Assistant Style guide review where it was occasionally not applying the suggestions until running it multiple times
• Cloned templates are now respecting updated Primary Websites
• Stories no longer appear locked in Composer Search when another user is in Read-Only mode

Users affected

Composer users

Action required

None

Release dates

• Sandbox - Tuesday, September 22, 2026
• Production - Tuesday, September 29, 2026

Release summary

This release of the Video Player addresses the following items

• Playthrough defaults to enabled when embedContinuousPlay is absent
• Mux GDPR consent gate has been fixed
• Restore native HLS for Chrome on iOS that was causing an encode error
• Force HLS.js in all Chrome environments
• Theme handling fix that sets style/template defaults after theme is defined
• Scrubber / theme override support now exists in PoWaSettings
• There are no longer errors with PoWa players when loading multiple autoplay videos
• Thumbnails are now loading in Safari before auto play

Users affected

Video Player users

Action required

None

Release dates

• Sandbox - Monday, September 21, 2026
• Production - Monday, September 28, 2026

Release summary

Author Service now provides self-service Custom Fields management via a new Fields screen in the UI. You can see every default and custom field, filter by name or type, add a new custom field, and edit or delete. Four field types are supported: text, textarea, dropdown, and boolean (true/false).

See the Managing custom author fields guide for the full walkthrough.

The same functionality is available through a new v3 API: GET, POST, PUT, DELETE /fields endpoints. It returns the same response format as the View API and validates your input before saving it.

Users affected

Editorial admins who manage author profiles.

Action required

None

Release dates

• Sandbox and Production - Wednesday, September 23, 2026

Release summary

Structured Content and Data Center 1.1 deliver capabilities we’ve heard most as feature requests from our early adopters: let records point at other content (Arc and your own custom schemas), give editors rich text formatting, and let teams create, manage schemas without API calls right in the UI.

• Reference fields: A record can now point at other records, stories, images, galleries, videos, and authors. The Content API resolves the reference and returns the target’s content inline, so a page pulling in a record gets the linked content in the same call. Editors pick targets from the same Photo Center and Video Center panels used in Composer, plus a story search and an author search built for this, and the record list is redesigned with one-click filters for status, website, and modified, published, and created dates. See Reference fields documentation for how targets, indexing, and validation work.
• Rich text: A new rich-text field type adds a proper editor: bold, italic, lists, and alignment. Content is sanitized against a fixed tag allowlist on save, and each field is capped at 0.5 MB. See Rich-text fields documentation for the full allowlist and the limit.
• Record usage tab: Open any record and see every story or record that references it, in one place, then republish them from there.
• Create and Manage Schema in the UI: Content types are now created and edited directly in Data Manager, with your organization’s searchable-field budget and usage shown in the sidebar as you work. Walk through it in the new Data Manager guide.

Users affected

Developers, Editorial

Action required

None

Release dates

• Sandbox - Monday, September 21 Delayed to Monday, October 5
• Production - Tuesday, September 22 Delayed to Monday, October 12

Release summary

Video Center now lets you schedule a publish for a future date and time, the same way you already schedule stories, photos, and galleries. When you publish a video, choose Later instead of Now, then set the date and time you want it to go live. You can reschedule or cancel a scheduled publish any time before it fires, and a new Scheduled Videos filter shows you everything that’s queued up but not live yet.

This works the same way in both the standard Video Center interface and VOD Edit Beta.

Users affected

Video Center users

Action required

None

Release dates

• Sandbox - Friday, September 18, 2026
• Production - Friday, September 18, 2026

Release summary

This release fixes a few items in Composer including

• An issue where lightboxes were not opening for photo tasks
• Tansa spellchecker is now correctly scrolling to the highlighted word/typo in editor viewport
• We’ve fixed issues with inline notes and inline styling so that they are no longer failing on text that sits flush at the top of the editor viewport or other situations where updates were not being applied

Users affected

Composer users

Action required

None

Release dates

• Sandbox - only available in Production
• Production - Tuesday, September 15

Release summary

Arc XP Compass is now available. It’s a personalization engine for home pages and section fronts that composes unique experiences using the newsroom’s editorial guidance and each reader’s own signals.

• Catch Me Up summarizes what a reader missed on the stories they follow since their last visit
• Content Recommendations rank what to read or watch next
• Editorial Priority Controls let editors pin, boost, or bury any story directly

Why it matters: Your home page stops showing the same layout to a daily subscriber and a once-a-month visitor. Each reader sees a page built around what they follow, and Catch Me Up gives returning readers a reason to come back directly instead of getting the story somewhere else. Editorial guidance sits ahead of the algorithm, not layered on top of it.

Learn more about Arc XP Compass here

Users affected

Compass users

Action required

Compass is a separately licensed Arc XP product. Contact your Arc XP account team to discuss packages and eligibility.

Release dates

• Sandbox - Tuesday, September 8, 2026
• Production - Tuesday, September 15, 2026

Release summary

This release now allows users to link Custom AI prompts to Composer free form fields.

• In Global Settings > AI Settings, there is a new Linked Composer Field that lists available Composer fields so users can run Custom Prompts on fields we don’t natively support AI on directly
• From Composer, when a custom prompt has been linked to a field users will now be able to see an AI icon on the field and run the custom prompt to return a result
• Note: This only works on available free form fields and only 1 custom prompt can be linked per valid Composer field

Users affected

Composer AI users

Action required

None

Release dates

• Sandbox - Tuesday, September 8, 2026
• Production - Tuesday, September 15, 2026

Release summary

Searching in Site Service no longer throws an error

Users affected

Admins using Site Service

Action required

None

Release dates

• Sandbox - Monday, September 14, 2026
• Production - Monday, September 21, 2026

Release summary

Search endpoints now return matching count and data results when using _sourceInclude with distributor. Previously, results could differ depending on whether type was also included. Both configurations now return consistent results.

Users affected

All

Action required

None

Release dates

• Sandbox - Thursday, August 27, 2026
• Production - Thursday, September 10, 2026

Release summary

PageBuilder Engine 7.2.0 improves publishing reliability with a fix for deployment version mismatches during publish, and brings performance and memory optimizations that make local development builds faster and lighter on system resources.

Users affected

PageBuilder users

Action required

None

Release dates

• Sandbox - Tuesday, September 1, 2026
• Production - Tuesday, September 8, 2026

Release summary

This release addresses a few items in Video Center including

• Resolved an issue with distributor rules between Video Center and Composer to ensure proper content distribution behavior. This has been removed and delayed so we can ensure proper behavior for downstream implications in Composer
• Removed unsupported fields and sections in Video Center Settings related to Facebook to streamline the configuration experience.
• Removed unused fields from the Utilities > Triad Service screen to improve clarity and reduce confusion

Users affected

Video Center users

Action required

None

Release dates

• Sandbox - Tuesday, September 1, 2026
• Production - Tuesday, September 8, 2026

Release summary

This release fixes an issue with Slack Alerts Configuration that was effecting spanish language sites.

Users affected

WebSked users

Action required

None

Release dates

• Sandbox - Tuesday, September 8, 2026
• Production - Tuesday, September 15, 2026

Release summary

This release now allows users to link Custom AI prompts to Composer free form fields.

• In Global Settings > AI Settings, there is a new Linked Composer Field that lists available Composer fields so users can run Custom Prompts on fields we don’t natively support AI on directly
• From Composer, when a custom prompt has been linked to a field users will now be able to see an AI icon on the field and run the custom prompt to return a result
• Note: This only works on available free form fields and only 1 custom prompt can be linked per valid Composer field

Users affected

Composer AI users

Action required

None

Release dates

• Sandbox - Tuesday, September 8, 2026
• Production - Tuesday, September 15, 2026

Release summary

Searching in Site Service no longer throws an error

Users affected

Admins using Site Service

Action required

None

Release dates

• Sandbox - Tuesday, August 25, 2026
• Production - Tuesday, September 1, 2026

Release summary

This release addresses the following items in Composer including:

• Updates to Read Only Mode

  • Users can now enter read only or suggest modes directly from Composer search results by clicking the overflow icon on the story cards
  • Users Entering read only mode from list or from the story directly will keep those users in read only mode regardless of the lock and regardless of refresh. The user in read only mode will never automatically get the lock until they go to edit or suggest mode.

• We’ve fixed a bug where removing AI metadata doesn’t move the suggestion to Rejected section in the AI Assistant

• Reordering related stories with AI-added stories in the list no longer causes some intermittent buggy behavior

• There’s no longer intermittent flashing when switching to review AI changes and save modals

• Content is no longer prematurely clipped on scroll inside the Editing view on Composer stories

• Link validation is no longer rejecting URLs containing hashtags (#!)

Users affected

Composer users

Action required

None

Release dates

• Sandbox - Tuesday, September 1, 2026
• Production - Tuesday, September 8, 2026

Release summary

This release addresses a few items in Video Center including

• Resolved an issue with distributor rules between Video Center and Composer to ensure proper content distribution behavior. This has been removed and delayed so we can ensure proper behavior for downstream implications in Composer
• Removed unsupported fields and sections in Video Center Settings related to Facebook to streamline the configuration experience.
• Removed unused fields from the Utilities > Triad Service screen to improve clarity and reduce confusion

Users affected

Video Center users

Action required

None

Release dates

• Sandbox - Tuesday, September 1, 2026
• Production - Tuesday, September 8, 2026

Release summary

This release fixes an issue with Slack Alerts Configuration that was effecting spanish language sites.

Users affected

WebSked users

Action required

None

Release dates

• Sandbox - Thursday, August 27, 2026
• Production - Thursday, August 27, 2026

Release summary

This release fixes two issues with the AI Assistant tag functionality that was causing an indefinite loading state spinner where nothing was happening and an improvement to the search functionality to suggest AI tags. This also addresses a bug where stories were intermittently getting an error for *Cannot read properties of undefined (reading 'replace')*

Users affected

Composer AI Assistant users

Action required

None

Release dates

• Sandbox and Production - Tuesday, August 25, 2026

Release summary

Two new Subscriptions APIs enable signed-in readers to resubscribe using a card already on file, without going through checkout or re-entering payment details. These APIs can be used to create streamlined resubscribe experiences that make it easier to win back former subscribers.

API updates

• GET /sales/public/v2/subscriptions/cards-on-file returns a signed-in reader’s saved cards, including the internal card ID, card brand, last four digits, and expiration date.
• POST /sales/public/v2/subscriptions/resubscribe starts a new subscription using a saved card and accepts the card ID, SKU, and price code.

For complete API details, see the Subscriptions APIs documentation.

Learn more

Explore how card-on-file resubscribe can support your win-back and upgrade strategy in Build Experiences That Let Your Audience Resubscribe or Upgrade in Seconds. For implementation guidance, see How to Build a One-Click Resubscribe Experience.

Users affected

Subscriptions developers

Action required

None

Release dates

• Sandbox - Thursday, August 27, 2026
• Production - Thursday, September 10, 2026

Release summary

PageBuilder Engine 7.2.0 improves publishing reliability with a fix for deployment version mismatches during publish, and brings performance and memory optimizations that make local development builds faster and lighter on system resources.

Users affected

PageBuilder users

Action required

None

Release dates

• Sandbox - Tuesday, August 25, 2026
• Production - Tuesday, September 1, 2026

Release summary

This release addresses the following items in Composer including:

• Updates to Read Only Mode

  • Users can now enter read only or suggest modes directly from Composer search results by clicking the overflow icon on the story cards
  • Users Entering read only mode from list or from the story directly will keep those users in read only mode regardless of the lock and regardless of refresh. The user in read only mode will never automatically get the lock until they go to edit or suggest mode.

• We’ve fixed a bug where removing AI metadata doesn’t move the suggestion to Rejected section in the AI Assistant

• Reordering related stories with AI-added stories in the list no longer causes some intermittent buggy behavior

• There’s no longer intermittent flashing when switching to review AI changes and save modals

• Content is no longer prematurely clipped on scroll inside the Editing view on Composer stories

• Link validation is no longer rejecting URLs containing hashtags (#!)

Users affected

Composer users

Action required

None

Release dates

• Sandbox and Production - Tuesday, August 25, 2026

Release summary

Two new Subscriptions APIs enable signed-in readers to resubscribe using a card already on file, without going through checkout or re-entering payment details. These APIs can be used to create streamlined resubscribe experiences that make it easier to win back former subscribers.

API updates

• GET /sales/public/v2/subscriptions/cards-on-file returns a signed-in reader’s saved cards, including the internal card ID, card brand, last four digits, and expiration date.
• POST /sales/public/v2/subscriptions/resubscribe starts a new subscription using a saved card and accepts the card ID, SKU, and price code.

For complete API details, see the Subscriptions APIs documentation.

Learn more

Explore how card-on-file resubscribe can support your win-back and upgrade strategy in Build Experiences That Let Your Audience Resubscribe or Upgrade in Seconds. For implementation guidance, see How to Build a One-Click Resubscribe Experience.

Users affected

Subscriptions developers

Action required

None

Release dates

• Sandbox and Production: Thursday August 25, 2026

Release summary

PageBuilder Editor 3.24.7 fixes a bug where publishing an oversized page or template could appear to succeed in the editor, then fail silently before reaching PageBuilder Engine. Publish size is now measured accurately and, an oversized publish now fails with a clear error message in the editor instead of failing silently.

Note: Because size measurement is now accurate, some pages/templates may now show a “too large” error that previously published with no warning.

Users affected

Editor users publishing large pages/templates (customers near/over size limit)

Action required

None

Release dates

• Sandbox - Tuesday, August 11, 2026
• Production - Tuesday, August 18, 2026

Release summary

This release addresses a number of items in Composer including:

• The AI Assistant now allows free form prompt entry, matching functionality that was previously in the Chrome Extension. Users can now enter free form prompts directly in the AI Assistant and will log the prompt you asked in the AI Assistant pane during your session.
• We’ve fixed an issue where article urls were displaying php-2
• Workflow status notes now save the same way that statuses do when you click out of the modal
• An issue where Composer failed to open articles with high content volume is resolved
• Composer “Schedule Publish” time is no longer intermittently locked to 06:00
• URLs are no longer intermittently automatically regenerating on changing primary website
• Lightboxes are again opening for photo tasks
• AI Suggested featured media is no longer intermittently crashing the Composer story

Users affected

Composer users

Action required

None

Release dates

• Sandbox - Tuesday, August 4, 2026
• Production - Tuesday, August 11, 2026

Release summary

This release fixes a few issues in Video Center including:

• First_publish_date getting overwritten on video re-publish with current time whenever it was edited/re-published. Now, first_publish_date remains unchanged.
• An issue where users were prompted for a YouTube ID when bypassing YouTube on a live event. Now, users can bypass YouTube without providing a YouTube ID.

Users affected

Editorial

Action required

None

Release dates

• Sandbox - Tuesday, August 4, 2026
• Production - Tuesday, August 11, 2026

Release summary

Freelance author names are now displayed in search and publication views

The author of the story is now displayed on the story card within the story search and publication views of WebSked when the distributor category is freelance, in addition to the existing staff distributor category.

Users affected

Websked users

Action required

None

Release dates

• Sandbox - Tuesday, August 3, 2026
• Production - Tuesday, August 11, 2026

Release summary

• Authors are now consistently and correctly categorized as type author when created or updated, preventing downstream rendering issues caused by a missing or incorrect type.
• Fixed a bug where certain author profiles created with a non-string image value could cause the UI to fail to render. The UI now ignores the invalid image and continues rendering normally.

Users affected

Authors users

Action required

None

Release dates

• Sandbox - Tuesday, August 11, 2026
• Production - Tuesday, August 18, 2026

Release summary

This release addresses a number of items in Composer including:

• The AI Assistant now allows free form prompt entry, matching functionality that was previously in the Chrome Extension. Users can now enter free form prompts directly in the AI Assistant and will log the prompt you asked in the AI Assistant pane during your session.
• We’ve fixed an issue where article urls were displaying php-2
• Workflow status notes now save the same way that statuses do when you click out of the modal
• An issue where Composer failed to open articles with high content volume is resolved
• Composer “Schedule Publish” time is no longer intermittently locked to 06:00
• URLs are no longer intermittently automatically regenerating on changing primary website
• Lightboxes are again opening for photo tasks
• AI Suggested featured media is no longer intermittently crashing the Composer story

Users affected

Composer users

Action required

None

Release dates

• Sandbox - Tuesday, July 28, 2026
• Production - Tuesday, August 4, 2026

Release summary

This release fixes the following items in Composer:

• We’ve resolved some intermittent crashing of certain articles in Composer
• We’ve fixed an issue where the autolink feature will not work if Pull/Block quote are present
• Removed annotations no longer leave a ghost element
• A bug within bulleted lists causing misorganization has been resolved
• An issue where content elements were disappearing occasionally on publish has been resolved
• We’ve fixed an issue with suggestions and comments being rearranged

Users affected

Composer users

Action required

None

Release dates

• Sandbox and Production - Monday, August 3, 2026

Release summary

Introducing Structured Content Types. Brings custom content support to Arc XP Content Platform. With Structure Content Types, you can define your own structured, custom content (i.e: recipes, events, business directories) with a schema definition. Your editorial teams use the new Arc Admin tool Data Center, to manage custom content with Arc XP Content platform capabilities.

See Structured Content Types documentation to learn more.

Users affected

Developers, Editorial

Action required

None

Release dates

• Sandbox & Production - Monday Aug 3, 2026

Release summary

PageBuilder Engine 7.1.1 is hot fix patch for a build step bug fix on Engine 7.1 Webpack upgrade.

Users affected

Developers

Action required

None

Release dates

• Sandbox and Production - Monday, August 3, 2026

Release summary

Themes 4.2.0 introduces two new content sources for Structured Content Types - a schema item and schema feed content source.

Users affected

Developers

Action required

None

Release dates

• Sandbox - Tuesday, August 4, 2026
• Production - Tuesday, August 11, 2026

Release summary

This release fixes a few issues in Video Center including:

• First_publish_date getting overwritten on video re-publish with current time whenever it was edited/re-published. Now, first_publish_date remains unchanged.
• An issue where users were prompted for a YouTube ID when bypassing YouTube on a live event. Now, users can bypass YouTube without providing a YouTube ID.

Users affected

Editorial

Action required

None

Release dates

• Sandbox - Tuesday, August 4, 2026
• Production - Tuesday, August 11, 2026

Release summary

Freelance author names are now displayed in search and publication views

The author of the story is now displayed on the story card within the story search and publication views of WebSked when the distributor category is freelance, in addition to the existing staff distributor category.

Users affected

Websked users

Action required

None

Release dates

• Sandbox - Tuesday, August 3, 2026
• Production - Tuesday, August 11, 2026

Release summary

• Authors are now consistently and correctly categorized as type author when created or updated, preventing downstream rendering issues caused by a missing or incorrect type.
• Fixed a bug where certain author profiles created with a non-string image value could cause the UI to fail to render. The UI now ignores the invalid image and continues rendering normally.

Users affected

Authors users

Action required

None

Release dates

• Sandbox and Production - Monday, August 3, 2026

Release summary

Introducing Structured Content Types. Brings custom content support to Arc XP Content Platform. With Structure Content Types, you can define your own structured, custom content (i.e: recipes, events, business directories) with a schema definition. Your editorial teams use the new Arc Admin tool Data Center, to manage custom content with Arc XP Content platform capabilities.

See Structured Content Types documentation to learn more.

Users affected

Developers, Editorial

Action required

None

Release dates

• Sandbox & Production - Monday Aug 3, 2026

Release summary

PageBuilder Engine 7.1.1 is hot fix patch for a build step bug fix on Engine 7.1 Webpack upgrade.

Users affected

Developers

Action required

None

Release dates

• Sandbox and Production - Monday, August 3, 2026

Release summary

Themes 4.2.0 introduces two new content sources for Structured Content Types - a schema item and schema feed content source.

Users affected

Developers

Action required

None

Release dates

• Sandbox and Production - Wednesday, July 29, 2026

Release summary Behavior for concurrent deployments has been changed.

Previously, when deployments were triggered at the same time in PageBuilder Deployer, through either the UI or API, they could be shown as successful. However, the later deployments could be corrupted, even though their status was marked as successful.

A lock mechanism has now been added by the underlying infrastructure service. The first deployment will be allowed to continue. Any later deployments triggered in the same time frame will be failed.

Those later deployments will now be marked as failed with this error message:

Request failed with status code 409

These later deployments were already being corrupted before this change. The difference is that Deployer UI and API will now report them as failed instead of successful.

Users affected Developers using Deployer UI and API.

Action required None

Release dates

• Sandbox - Tuesday, July 28, 2026
• Production - Tuesday, August 4, 2026

Release summary

This release fixes the following items in Composer:

• We’ve resolved some intermittent crashing of certain articles in Composer
• We’ve fixed an issue where the autolink feature will not work if Pull/Block quote are present
• Removed annotations no longer leave a ghost element
• A bug within bulleted lists causing misorganization has been resolved
• An issue where content elements were disappearing occasionally on publish has been resolved
• We’ve fixed an issue with suggestions and comments being rearranged

Users affected

Composer users

Action required

None

Release dates

• Sandbox and Production - Wednesday, July 29, 2026

Release summary Behavior for concurrent deployments has been changed.

Previously, when deployments were triggered at the same time in PageBuilder Deployer, through either the UI or API, they could be shown as successful. However, the later deployments could be corrupted, even though their status was marked as successful.

A lock mechanism has now been added by the underlying infrastructure service. The first deployment will be allowed to continue. Any later deployments triggered in the same time frame will be failed.

Those later deployments will now be marked as failed with this error message:

Request failed with status code 409

These later deployments were already being corrupted before this change. The difference is that Deployer UI and API will now report them as failed instead of successful.

Users affected Developers using Deployer UI and API.

Action required None

Release dates

• Sandbox - Tuesday, July 21, 2026
• Production - Thursday, July 23, 2026

Release summary

This release addresses the following items including:

• We’ve fixed an issue where by default, every AI request was sending English language regardless of the story’s actual language
• Any accepted AI suggestions will now show up in Revision History
• We’ve fixed an issue where AI suggested related items were not being displayed by specific score order
• Comments no longer save when users press cancel
• We’ve moved the character count on the headline field so that it no longer bounces when users click into the field

Users affected

Composer users

Action required

None

Release dates

• Sandbox and Production - Monday, July 20, 2026

Release summary

Web SDK

Potential beta customers frequently reported that they either didn’t have a CDP or didn’t have a means of instrumenting the relevant events server-side.

We have responded to that feedback by introducing a web SDK that enables you to send user events from the client side securely and without a CDP.

The SDK sits downstream of your Consent Management Platform and Identity Platform, if you have one, and offers a streamlined install path to sending user events.

Learn more about the SDK and how to integrate it into your site here.

Popular and Trending Endpoints

Content Recommendations API now has two standalone, non-personalized recommendation endpoints — Most Popular and Trending — backed by first-party engagement data.

• GET /recommend/v1/popular — Most Popular: Content ranked by total reader engagement over the last 24 hours
• GET /recommend/v1/trending — Trending: Content ranked by engagement velocity — the rate of increase over a short window (three hours) relative to a baseline (24 hours)

Neither takes a user_id. Both are identical for every reader of a given tenant and site, so they are cacheable at the edge and carry no personalization.

When engagement data is too thin, such as for a new or quiet tenant or site, results fall back to the most recently published content so the response is never empty.

PageBuilder reference block

We also heard repeatedly during our conversations with potential Content Recommendations API customers that they would appreciate assistance streamlining the experience development required to onboard. We are happy to announce that we now have a PageBuilder reference block which you can clone into your repo and start serving content recommendations.

Users affected

Content Recommendations API beta customers

Action required

None

Release dates

• Sandbox - Tuesday Jul 14, 2026
• Production - Monday Jul 20, 2026 (Superseded by Engine 7.1.1 patch)

Release summary

PageBuilder Engine 7.1.0 upgrades Webpack from 4.47.0 to 5.107.2, bringing faster builds, less system resources and better long-term support for your development stack.

Our benchmarks shows good local development improvement, up to 2x build times, 20-30% less memory usage with Webpack5 update. At the same time we observed longer build times at Deployer in Arc environments. If your bundle currently runs close to Deployer timeout limit, Engine 7.1 release may result timeouts in Deployer.

This dependency upgrade is backwards compatible and should not require any code change on customers bundle code. But the customers own dependencies may have breaking behaviors between Webpack4 and Webpack5. Please test your bundle output (pages and templates) locally before deploying and promoting a deployment with Engine 7.1 in production.

With Webpack5 upgrade we also made stats.json file generation as opt-in behavior, not taking time in every build. To generate stats.json to analyze your client-side bundle content, set COMPILER_EMIT_STATS=true on your .env file and run a build.

This release also lays groundwork for smarter caching. There is no impact to your cached pages.

We created a small adoption guide to walk through key points to leverage webpack 5 to optimize your builds, both speed and final output size: Adopting Webpack 5 in Your Bundle

Users affected

Developers

Action required

None

Release dates

• Sandbox - Tuesday, July 21, 2026
• Production - Thursday, July 23, 2026

Release summary

This release addresses the following items including:

• We’ve fixed an issue where by default, every AI request was sending English language regardless of the story’s actual language
• Any accepted AI suggestions will now show up in Revision History
• We’ve fixed an issue where AI suggested related items were not being displayed by specific score order
• Comments no longer save when users press cancel
• We’ve moved the character count on the headline field so that it no longer bounces when users click into the field

Users affected

Composer users

Action required

None

Release dates

• Sandbox and Production - Monday, July 20, 2026

Release summary

Web SDK

Potential beta customers frequently reported that they either didn’t have a CDP or didn’t have a means of instrumenting the relevant events server-side.

We have responded to that feedback by introducing a web SDK that enables you to send user events from the client side securely and without a CDP.

The SDK sits downstream of your Consent Management Platform and Identity Platform, if you have one, and offers a streamlined install path to sending user events.

Learn more about the SDK and how to integrate it into your site here.

Popular and Trending Endpoints

Content Recommendations API now has two standalone, non-personalized recommendation endpoints — Most Popular and Trending — backed by first-party engagement data.

• GET /recommend/v1/popular — Most Popular: Content ranked by total reader engagement over the last 24 hours
• GET /recommend/v1/trending — Trending: Content ranked by engagement velocity — the rate of increase over a short window (three hours) relative to a baseline (24 hours)

Neither takes a user_id. Both are identical for every reader of a given tenant and site, so they are cacheable at the edge and carry no personalization.

When engagement data is too thin, such as for a new or quiet tenant or site, results fall back to the most recently published content so the response is never empty.

PageBuilder reference block

We also heard repeatedly during our conversations with potential Content Recommendations API customers that they would appreciate assistance streamlining the experience development required to onboard. We are happy to announce that we now have a PageBuilder reference block which you can clone into your repo and start serving content recommendations.

Users affected

Content Recommendations API beta customers

Action required

None

Release dates

• Sandbox and Production - Monday, July 20, 2026

Subscriptions 1.105.1 - Migration API Validation

Release summary

The Migration API now validates profile name, email, and legacy ID fields during migration requests. Invalid records are skipped and returned with field-specific error codes, while all other records in the batch continue processing successfully.

API updates

Endpoint: POST /identity/api/v1/migrate

The Migration API now enforces the same validation rules used by the Registration API for supported profile fields. Validation is performed on a per-record basis. Records that fail validation are excluded from migration and returned in the response with the applicable error code(s) in the errors array. Other records in the batch continue processing normally.

The following optional fields are validated only when a value is provided:

Allowed characters

• firstName, lastName, and secondLastName support letters from any language, spaces, apostrophes ('), hyphens (-), and periods (.). Values must end with a letter.
• displayName supports letters from any language, digits, spaces, apostrophes, hyphens, and underscores.
• email must be a valid email address. The same validation also applies to a profile’s verification email.

For request and response details, see the Developer Identity section of the Subscriptions APIs documentation.

Users affected

Identity migration API users

Action required

Recommended: Validate or normalize profile name, display name, email, and legacy ID fields before submitting migration batches. Review the errors array returned for skipped records, correct any invalid values, and resubmit those records.

Release dates

• Sandbox - Tuesday, July 7, 2026 Wednesday, July 15, 2026 (delayed)
• Production - Wednesday, July 8, 2026 Thursday, July 16, 2026 (delayed)

Release summary

Customers can see granular Page vs API vs OBF traffic patterns as breakdown of Edge Requests and Render Requests charts in Traffic Patterns section. Previously we were showing single chart for Edge Requests, and another chart for Render requests all together.

Customers can now see page and template size warnings in a new chart in Bundle & Publish Activity section.

For more information about PageBuilder Performance dashboard, please check the documentation.

Users affected

PageBuilder users

Action required

None

Release dates

• Sandbox and Production - Wednesday, July 15, 2026

Release summary

We’re excited to announce the initial release of Ask the News, a new AI-powered Q&A experience that helps users quickly find answers cited in your journalism, while capturing first-party reader intent.

This initial launch delivers the core Ask the News experience, including AI-generated answers based on eligible news content, source attribution to supporting articles, and a conversational interface for exploring news topics more efficiently.

Highlights include:

• Natural language Q&A – Ask questions about the news in plain language.
• Grounded responses – AI-generated answers are based on published news content with links to supporting articles.
• Conversational exploration – Ask follow-up questions to dive deeper into topics.
• Fast discovery – Find relevant information without manually searching across multiple stories.

This is the initial public release of Ask the News. Additional enhancements and feature updates will be delivered in future releases as we continue to refine the experience based on user feedback. See Ask the News on ALC for more information.

Users affected

Current Arc XP Platform customers

Action required

Interested in adding Ask the News to your Arc XP platform? Reach out to your Technical Account Manager to learn more about licensing, availability, and the steps to get started.

Release dates

• Sandbox and Production - Monday, July 13, 2026

Release summary

Signals API

Editorial Signals are a layer of human-controlled ranking rules that sit on top the Content Recommendation API’s machine-learned recommendations.

They let your newsroom override, nudge, or filter the model’s output without retraining anything: the changes take effect on the very next recommendation request.

In short: AI decides what is likely to engage a given reader; signals decide what is editorially encouraged, discouraged, or required for that reader to see (or not see).

Signals are exposed through a dedicated service: the Signals API (/signals/v1).

The four signal types

There are four distinct signal types. Each one answers a different editorial question.

Boost

”I want this to do better than the model thinks it will.”

Multiplies the item’s AI score by a weight between 1.0 and 10.0. Item rises naturally in the ranking.

Bury

”I want this to do worse than the model thinks it will.”

Multiplies the item’s AI score by a weight between 0.0 and 0.9. Item falls in the ranking but isn’t removed.

Pin

”This item must appear at position N.”

Forces the item into a specific 1-indexed slot, even if the content was not included in the preliminary candidate set. An absolute position override.

Exclude

”This item must not appear at all, regardless of relevance.”

Removes the item from the candidate set entirely. Takes precedence over every other signal, including Pin.

Boost and Bury are soft — they bias the ranking. Pin and Exclude are hard — they override it. The reranker applies them in a deterministic order (exclude → boost/bury → sort → pin → truncate), so the outcome is predictable no matter how many signals stack up on the same response.

Learn more in this Signals API guide.

Recommendations API: remove content anchor

The Recommendations API previously had the ability to anchor a recommendation based on the content ID. The initial implementation did not provide the expected results, and we are re-visiting the approach. For now, the suggested approach is to leverage anchoring by applying a section filter to the Recommendations API to achieve some measure of relatedness.

Recommendations API: Recency preview before ingestion

Before your catalog has been ingested and the model has trained, GET /recommend/v1/recommendations still returns a usable response so you can build and validate your rendering ahead of go-live.

In this state the API returns the five most recent active catalog items as a recency preview. The API returns up to five items in the free subscription tier. It is possible to request fewer items, but not more.

Preview items are fully enriched and carry the same attribution as personalized results, so your card-rendering code exercises the real response shape. What they do not carry is a relevance score — every preview item is scored 0.0. A response whose items are all scored 0.0 is the signal clients use to distinguish a preview from personalized results: no reranker is run, and no editorial signals (boosts, buries, pins) are applied to a preview.

If the catalog has no content yet (nothing has been ingested at all) there is nothing to preview, and the request falls through to the existing 403 response.

CDP Integration Guide

The Developer Portal now includes a new Connect Your CDP to the Recommender API guide that covers how to connect your customer data platform, analytics tool, or homegrown source into the Content Recommendations API.

This article outlines ingestion requirements and best practices along with common integration patterns covering:

• BlueConic
• HTTP-based connectors like Amplitude, Adobe Real-Time CDP, and Tealium
• S3-transport connectors like Permutive and ActionIQ
• Analytics-only stacks like GA4 and Sophi

Users affected

Beta customers

Action required

None

Release dates

• Sandbox - Tuesday Jul 14, 2026
• Production - Monday Jul 20, 2026 (Superseded by Engine 7.1.1 patch)

Release summary

PageBuilder Engine 7.1.0 upgrades Webpack from 4.47.0 to 5.107.2, bringing faster builds, less system resources and better long-term support for your development stack.

Our benchmarks shows good local development improvement, up to 2x build times, 20-30% less memory usage with Webpack5 update. At the same time we observed longer build times at Deployer in Arc environments. If your bundle currently runs close to Deployer timeout limit, Engine 7.1 release may result timeouts in Deployer.

This dependency upgrade is backwards compatible and should not require any code change on customers bundle code. But the customers own dependencies may have breaking behaviors between Webpack4 and Webpack5. Please test your bundle output (pages and templates) locally before deploying and promoting a deployment with Engine 7.1 in production.

With Webpack5 upgrade we also made stats.json file generation as opt-in behavior, not taking time in every build. To generate stats.json to analyze your client-side bundle content, set COMPILER_EMIT_STATS=true on your .env file and run a build.

This release also lays groundwork for smarter caching. There is no impact to your cached pages.

We created a small adoption guide to walk through key points to leverage webpack 5 to optimize your builds, both speed and final output size: Adopting Webpack 5 in Your Bundle

Users affected

Developers

Action required

None

Release dates

• Sandbox - Tuesday, July 7, 2026 Wednesday, July 15, 2026 (delayed)
• Production - Wednesday, July 8, 2026 Thursday, July 16, 2026 (delayed)

Release summary

Customers can see granular Page vs API vs OBF traffic patterns as breakdown of Edge Requests and Render Requests charts in Traffic Patterns section. Previously we were showing single chart for Edge Requests, and another chart for Render requests all together.

Customers can now see page and template size warnings in a new chart in Bundle & Publish Activity section.

For more information about PageBuilder Performance dashboard, please check the documentation.

Users affected

PageBuilder users

Action required

None

Release dates

• Sandbox and Production - Wednesday, July 15, 2026

Release summary

We’re excited to announce the initial release of Ask the News, a new AI-powered Q&A experience that helps users quickly find answers cited in your journalism, while capturing first-party reader intent.

This initial launch delivers the core Ask the News experience, including AI-generated answers based on eligible news content, source attribution to supporting articles, and a conversational interface for exploring news topics more efficiently.

Highlights include:

• Natural language Q&A – Ask questions about the news in plain language.
• Grounded responses – AI-generated answers are based on published news content with links to supporting articles.
• Conversational exploration – Ask follow-up questions to dive deeper into topics.
• Fast discovery – Find relevant information without manually searching across multiple stories.

This is the initial public release of Ask the News. Additional enhancements and feature updates will be delivered in future releases as we continue to refine the experience based on user feedback. See Ask the News on ALC for more information.

Users affected

Current Arc XP Platform customers

Action required

Interested in adding Ask the News to your Arc XP platform? Reach out to your Technical Account Manager to learn more about licensing, availability, and the steps to get started.

Release dates

• Sandbox and Production - Monday, July 13, 2026

Release summary

Signals API

Editorial Signals are a layer of human-controlled ranking rules that sit on top the Content Recommendation API’s machine-learned recommendations.

They let your newsroom override, nudge, or filter the model’s output without retraining anything: the changes take effect on the very next recommendation request.

In short: AI decides what is likely to engage a given reader; signals decide what is editorially encouraged, discouraged, or required for that reader to see (or not see).

Signals are exposed through a dedicated service: the Signals API (/signals/v1).

The four signal types

There are four distinct signal types. Each one answers a different editorial question.

Boost

”I want this to do better than the model thinks it will.”

Multiplies the item’s AI score by a weight between 1.0 and 10.0. Item rises naturally in the ranking.

Bury

”I want this to do worse than the model thinks it will.”

Multiplies the item’s AI score by a weight between 0.0 and 0.9. Item falls in the ranking but isn’t removed.

Pin

”This item must appear at position N.”

Forces the item into a specific 1-indexed slot, even if the content was not included in the preliminary candidate set. An absolute position override.

Exclude

”This item must not appear at all, regardless of relevance.”

Removes the item from the candidate set entirely. Takes precedence over every other signal, including Pin.

Boost and Bury are soft — they bias the ranking. Pin and Exclude are hard — they override it. The reranker applies them in a deterministic order (exclude → boost/bury → sort → pin → truncate), so the outcome is predictable no matter how many signals stack up on the same response.

Learn more in this Signals API guide.

Recommendations API: remove content anchor

The Recommendations API previously had the ability to anchor a recommendation based on the content ID. The initial implementation did not provide the expected results, and we are re-visiting the approach. For now, the suggested approach is to leverage anchoring by applying a section filter to the Recommendations API to achieve some measure of relatedness.

Recommendations API: Recency preview before ingestion

Before your catalog has been ingested and the model has trained, GET /recommend/v1/recommendations still returns a usable response so you can build and validate your rendering ahead of go-live.

In this state the API returns the five most recent active catalog items as a recency preview. The API returns up to five items in the free subscription tier. It is possible to request fewer items, but not more.

Preview items are fully enriched and carry the same attribution as personalized results, so your card-rendering code exercises the real response shape. What they do not carry is a relevance score — every preview item is scored 0.0. A response whose items are all scored 0.0 is the signal clients use to distinguish a preview from personalized results: no reranker is run, and no editorial signals (boosts, buries, pins) are applied to a preview.

If the catalog has no content yet (nothing has been ingested at all) there is nothing to preview, and the request falls through to the existing 403 response.

CDP Integration Guide

The Developer Portal now includes a new Connect Your CDP to the Recommender API guide that covers how to connect your customer data platform, analytics tool, or homegrown source into the Content Recommendations API.

This article outlines ingestion requirements and best practices along with common integration patterns covering:

• BlueConic
• HTTP-based connectors like Amplitude, Adobe Real-Time CDP, and Tealium
• S3-transport connectors like Permutive and ActionIQ
• Analytics-only stacks like GA4 and Sophi

Users affected

Beta customers

Action required

None

Release dates

• Sandbox - Tuesday, July 7, 2026 Wednesday, July 15, 2026 (delayed)
• Production - Wednesday, July 8, 2026 Thursday, July 16, 2026 (delayed)

Release summary

Customers can see granular Page vs API vs OBF traffic patterns as breakdown of Edge Requests and Render Requests charts in Traffic Patterns section. Previously we were showing single chart for Edge Requests, and another chart for Render requests all together.

Customers can now see page and template size warnings in a new chart in Bundle & Publish Activity section.

For more information about PageBuilder Performance dashboard, please check the documentation.

Users affected

PageBuilder users

Action required

None

Release dates

• Sandbox - Tuesday, June 30, 2026
• Production - Tuesday, July 7, 2026

Release summary

This release addresses a few issues in Composer including:

• We’ve resolved some intermittent timestamp and timezone display issues with revision history
• Stories scheduled to publish later are no longer being published with missing content
• We’ve fixed an issue with keyboard date entry on the date field for scheduling stories
• An issue has been resolved where stories kept incorrectly intermittently saving after taking over an idle story

Users affected

Composer users

Action required

None

Release dates

• Sandbox - Tuesday, July 7, 2026 Wednesday, July 15, 2026 (delayed)
• Production - Wednesday, July 8, 2026 Thursday, July 16, 2026 (delayed)

Release summary

Customers can see granular Page vs API vs OBF traffic patterns as breakdown of Edge Requests and Render Requests charts in Traffic Patterns section. Previously we were showing single chart for Edge Requests, and another chart for Render requests all together.

Customers can now see page and template size warnings in a new chart in Bundle & Publish Activity section.

For more information about PageBuilder Performance dashboard, please check the documentation.

Users affected

PageBuilder users

Action required

None

Release dates

• Sandbox - Tuesday, June 30, 2026
• Production - Tuesday, July 7, 2026

Release summary

This release addresses a few issues in Composer including:

• We’ve resolved some intermittent timestamp and timezone display issues with revision history
• Stories scheduled to publish later are no longer being published with missing content
• We’ve fixed an issue with keyboard date entry on the date field for scheduling stories
• An issue has been resolved where stories kept incorrectly intermittently saving after taking over an idle story

Users affected

Composer users

Action required

None

Release dates

• Sandbox - Tuesday, June 16, 2026
• Production - Tuesday, June 23, 2026

Release summary

This release updates a few small issues in Composer including:

• Updates to the save button that were intermittently causing flickering
• Fixed an issue where Composer was failing when empty values were placed in the pre-selected planned ready times publish / update workflow in settings
• The keyboard shortcut for removing text (CMD+X) is now being logged as a suggestion in Suggest Mode
• We’ve fixed an issue where CMD+F no longer freezes on longer articles

Users affected

Composer users

Action required

None

Release dates

• Sandbox - Tuesday, June 16, 2026
• Production - Tuesday, June 23, 2026

Release summary

This release updates a few small issues in Composer including:

• Updates to the save button that were intermittently causing flickering
• Fixed an issue where Composer was failing when empty values were placed in the pre-selected planned ready times publish / update workflow in settings
• The keyboard shortcut for removing text (CMD+X) is now being logged as a suggestion in Suggest Mode
• We’ve fixed an issue where CMD+F no longer freezes on longer articles

Users affected

Composer users

Action required

None

Release dates

• Sandbox - Tuesday, June 2, 2026
• Production - Tuesday, June 9, 2026

Release summary

This release resolves a few issues in Composer including:

• Searching for story templates no longer incorrectly shows [Object object] in the search field
• An issue has been resolved where users could not input “00” hours in Composer ‘Publish Later’ field
• We’ve fixed as issue where after stories were cloned, circulations were not showing up until you refreshed

Users affected

Composer users

Action required

None

Release dates

• Sandbox: Wednesday May 20, 2026
• Production: Thursday June 9, 2026

Release summary

Internal improvements on logging and performance around linking and page publishing process.

Users affected

Editors

Action required

None

Release dates

• Sandbox - Tuesday, June 2, 2026
• Production - Tuesday, June 9, 2026

Release summary

This release resolves a few issues in Composer including:

• Searching for story templates no longer incorrectly shows [Object object] in the search field
• An issue has been resolved where users could not input “00” hours in Composer ‘Publish Later’ field
• We’ve fixed as issue where after stories were cloned, circulations were not showing up until you refreshed

Users affected

Composer users

Action required

None