We are very interested in your edge connector with DataDome. But because of their pricing model, and the wide variety of use-cases they support, it would be beneficial to Advance Local to be able to restrict the number of requests the DataDome connector needs to be aware of to those that only apply to article URLs. (Our current preferred use-case is knowing/preventing AI bots and bots in general from consuming our article content.)
In the future we may also have an interest in preventing credit card cracking, for example, which we could then expand our usage of DataDome with another URL pattern, without having to go full throttle to all requests that Akamai fields for our ArcXP hosted properties.
The release is available in sandbox and production.
This functionality will be introduced in Delivery 1.36 release which is slated for the week of 10/20/2025. The release will have an option for including or excluding a file path and will allow for the use of wild cards in the path. Thank you for your idea on how to make the Arc Edge Integration with DataDome better!