Skip to main content

Release Notes, June 29, 2024

Our newest release includes multiple ATS for Web improvements including data layer capabilities for Snapchat and Pinterest CAPI and support for Google's SSP (supply-side platform).

New

  • We have released a cohort-based targeting function through Google’s SSP (GSSP), LiveRamp pixel serving, and Data Marketplace. This enhancement gives publishers more flexibility and better access to Google SSP workflows while supporting Data Marketplace without third-party cookies.

    Google SSP enables 1P, 2P, and 3P data sourced from Data Marketplace to be matched to Cohort IDs. These Cohort IDs function as segment-based identifiers and will be used by marketers to create Deal IDs, which can be integrated into their participating DSPs.

  • You can now enable Data Layer Detection for Pinterest and SnapchatConversions API events. This feature has previously been enabled for Meta CAPI. The Data Layer Detection allows users who leverage data layer on their properties to push event data to the CAPI. To learn more, see "Implement Pinterest CAPI" and "Implement Snapchat CAPI".

  • The conversionModuleReady event now fires when the conversions API module loads, ensuring timely notifications and improved integration efficiency. To learn more, see "ATS.js Functions and Events".

Improved

  • To easily accommodate websites with dynamic elements (including login forms), “Detect Dynamic Elements” is now enabled by default for all newly created ATS for Web configurations. Previously, you had to manually enable this feature by clicking “Advanced” in the "Obtain Identifiers" section, making it easy to forget or overlook. To learn more, see "Configure Advanced Settings for Detect Mode".

Fixed

  • Instances of duplicate envelope requests to ATS API when using ATS for Web to obtain identifiers from URL have been fixed. Previously, when the identifier from the URL was detected, the envelope request would be sent twice resulting in two sets of envelopes being returned. Now if an identifier is detected, only one request for envelope generation is sent to the backend.