• Exclude requests from DataDome protection when including a x-datadome-skip-detection header with the request ID (see FAQ section)

• Fix the case of the XRealIP in the JSON payload to the Account Protect API

• Add CookiesList to payloads sent to Protection API

• Fix the case of the XRealIp in the JSON payload to the Account Protect API

• Add title attribute to challenge iframe to improve accessibility

• Add responseProvider function to inject the JavaScript Tag dynamically in HTML responses
• Add EW_DD_CLIENT_SIDE_KEY required variable to specify the client-side key
• Add EW_DD_JS_URL and EW_DD_JS_OPTIONS optional variables to respectively customize the URL to fetch the JavaScript Tag and define its configuration
• Remove onClientRequest and onClientResponse functions to rely on responseProvider function

• Remove the Configuration.enableProxy parameter from the Configuration initializer to avoid misconfiguration issues. Use the Info.plist to toggle DataDomeProxy instead.

As of July 1, 2025, DataDome will no longer support the following browsers for CAPTCHA and Device Check:

• Internet Explorer 11 (support ended June 15, 2022)
• Safari 11 and earlier (support ended September 17, 2018)

• Improve thread safety of internal components

• Add challengeLanguage option to force challenges for XMLHttpRequest or Fetch requests to be displayed with a specific language and ignore language settings from the browser