What's New in Delivery

Release dates

Release summary

The Content Search dashboard provides insights into your Content API search usage, including request volumes, rate limiting, and error metrics.

The dashboard is now available to all customers in production. For more information, please check the documentation.

Users affected

Only accessible for Page Builder users.

Action required

None

Release dates

Release summary

The option to self-service provision a site will be removed from the user experience if the organization does not qualify. Although mentioned in documentation, the option to provision was still available in the UI when it was known not to work (that is, the organization has secondary organizations or other custom organization configurations), resulting in user frustration and support tickets to correct. The experience will change for a limited number of customers, and they will continue to submit support tickets to provision new sites (as they do currently).

Users affected

Delivery site managers

Action required

There is no action required, the experience change will be applied automatically.

Release dates

Release summary

Expanding the Arc XP Edge Integration Framework’s functionality for integrations with DataDome’s Advanced Bot Management feature. Two features are being added with this release:

1. Expanded Header Information for adding insight on GPT agents

2. Include / Exclude based on file path

Expanded Header Information for added insight on GPT agents

Extend the DataDome Edge integration to pass all three headers (Signature, Signature-Input, Signature-Agent) so that detection is both complete and reliable for the GPT agents. Currently, only Signature-Agent is passed.

Include / Exclude based on file path

This request originated from the Idea Portal (WG-I-24). Thank you to Advanced Local, Libération Reuters

Customers want more control of what content is sent to DataDome for scanning. Allowing the option to either include or exclude based on file path(s) will give better control to customers. Also, the user experience will now display the key that has been configured to help in debugging any issues related to the key that was entered.

- Use either the include or exclude option but not both

-Specify multiple paths by using the ; between path entries

-Wild cards can be used, we recommend limiting entry to 128 characters to reduce the cases where the matching exceeds the edge integration timeout

-We DO NOT support the use of regex values in the include / exclude paths, but do allow for wildcards.

How wildcards work:

"*" matches zero or more characters in [\\w.%~-] (letters, numbers, underscore, dot, percent sign, tilde, or dash)

"?" matches exactly one character from the same set

What this means for you: URLs with dynamic folder names and even encoded characters will now be matched more reliably, improving compatibility and reducing the need for manual configuration.

For example: /*/*/????/??/*.html could be used to represent /news/world/2025/10/article-name.html or /sports/football/2023/09/match-results.html

This pattern is a flexible way to capture any HTML page stored under a date-based path — two folders, then a 4-digit year, a 2-digit month, and finally the page.

Users affected

Delivery site managers

Action required

The header data expansion will automatically occur on all requests; there is no action needed. The Restrict Traffic is an optional configuration. No action is needed if you do not wish to restrict traffic sent to DataDome for analysis on the site.

Release dates

Release summary

Introducing Arc XP’s Edge Integration Framework, a new way to connect third-party services to your Arc XP environment right at the edge layer. This framework gives you more control over how you manage traffic before it reaches your site, without the need for custom development.

The first integration available through this framework is DataDome’s Advanced Bot Management service.

This integration enables Arc XP customers to leverage DataDome’s bot detection engine to identify and block malicious bots, such as scrapers, credential stuffing tools, and fake traffic, before those requests reach your application. Filtering at the edge layer helps preserve infrastructure resources, protects paywalls or premium content, and ensures that your analytics reflect real user behavior.

To use this feature, you must have an active DataDome subscription and configure protection rules directly through the DataDome platform. Arc XP facilitates the connection and routing of traffic to DataDome but does not manage bot detection policies or enforcement.

To get started, see Managing your DataDome edge integration.

Users affected

Delivery site managers

Action required

To enable edge integrations with DataDome, contact your Technical Account Manager. Your account manager can also help connect you with DataDome if you do not currently subscribe.

Release dates

Release summary

This hotfix expands the Arc XP Edge Integration Framework’s functionality for integrations with DataDome’s Advanced Bot Management feature, to include scanning on Outbound Feeds (OBF). Multiple customers have asked that OBF be included in what can be sent to DataDome for scanning. By default, OBF will be included. If a customer wishes to exclude OBF from what is sent for scanning, the exclude path should be added to the exclude list.

Exclude based on file path

Users affected

Delivery site managers

Action required

Add the exclude path to restrict the traffic if you DO NOT want your OBF sent to DataDome for scanning; otherwise there is no action needed.