Release Notes, March 27, 2023

New and improved dashboard for Estimated Revenue that shows the incremental revenue numbers. Incremental revenue is the additional revenue that a business generates from having ATS implemented on the page.

ATS.js can now detect multiple hashed identifiers (in SHA1, SHA256, or MD5) in the URL when using Detect Mode.For example:

https://example.com/signup?param_a=#####&param_b=#####&param_c=#####

New column in ATS Placements screen called Linked Configurations (Web / Mobile) is now available. This column shows the number of connected configurations split by web and mobile app.

As we increase the number of envelopes that are returned from the ATS back-end to ATS.js during envelope creation (LiveRamp envelope, Facebook envelope and soon, Google PAIR IDs), the backend now returns more information on the envelope type and envelope-specific error messaging to support debugging purposes.

ATS.js will now refresh multiple envelopes in one request and the failure of one envelope does not prevent other envelopes from being refreshed. Allowing multiple envelopes to be refreshed in the same request will reduce the amount of calls to our back-end and page latency.

When using the filter feature in ATS Analytics, selected filters in the same subject will now be displayed in the same group

Users must select the implementation method between ATS for Web and ATS API when creating a Facebook Conversion API configuration in Console. When selecting ATS API, you don't need to configure the events list in Console and can just pass event data directly to our backend. See the developers' documentation for Facebook CAPI to learn more.

Facebook Conversion API adapter now allows external_id and/or partner_id  to be sent in the payload through the backend. These parameters are mutually inclusive (you can provide both) but at least one must be included in the request.

external_id is kept for backward compatibility, so the partner_id takes priority in case both parameters are sent. The value of external_id or partner_id is stored in the partner_id value when forming a request to Meta.

More types of Action Source can now be added in Console when configuring the Facebook Conversion API Adapter. Action Source is a required field that allows you to specify where your conversions occurred.

We now have description texts underneath the header title in Console that explains the use-case for each product or section.

The settings for Match Pixel (OpenIDL) in Console that used to be located in the Envelope Settings screen have been moved to the Integrations section. To see the Match Pixel settings, go to ATS > Web, click on a configuration, select Integrations tab and click New.

Improved dropdown selector for selecting which identifier types need to be obtained in the Obtain Identifiers screen within an ATS configuration in Console.

Clicking on a Placement within the Placement (ID) column for ATS for Web’s Configurations screen in Console will now open a new tab.

When a Placement is approved in Console, the Submit button will be disabled until the user makes a change to the Placement settings.

Hostname and protocol are removed from the URL upon saving the Placement domain scope in Console.

Improved error messaging when creating new Placements in Console to allow error messages to disappear as soon as users type within the required fields. Validation alerts are implemented for required fields with timeout of 6s.

The Envelope module initialization in ATS.js (ATS for Web) has been improved to allow better RampID envelope fetching for identifiers obtained through URL detection. This enhancement facilitates a scenario where a new user gives consent, ATS.js is triggered, but the Detection module obtains the identifier from the configured URL faster than the Envelope module’s initialization.

We have fixed an issue regarding Incorrect dates displayed in the Performance insights screen for devices outside of the GMT+1 timezone.

You can now remove Custom Data Parameters from a Facebook Conversion API Adapter configuration in Console.

We have fixed an issue that occurred when publishing an ATS for Web configuration in Console caused by AWS Cloudfront invalidation error.

The Privacy Review column in Console for ATS Web Configurations is now sorted correctly.

The search functionality in Console on the ATS for Web Configuration screen now includes the Placement ID column.