Version June 11, 2026 - 5.122

Updates on Google Customer Match

AVAILABLE TO ALL CUSTOMERS WITH GOOGLE CUSTOMER MATCH ACTIVATED

Background

Previously, when setting up the Google Customer Match integration, a series of steps had to be executed on the Google client side, making the process elaborate, long and error prone.

Solution

Now, the process has been simplified tremendously, using a Google Authentication app provided by Selligent.

What it looks like in the solution

To gain access to the Google Authentication App, contact support to create a user and password. Once you have access, you can log on with the user and password provided to you.

This app will take you through an easy and quick step-by-step process of creating an Ads CustomerId and Refresh Token, used in the Social Endpoint in Selligent:

Details are available in the article Google Customer Match installation.

 

API updates — follow-up: Key-field index guard for bulk data processing

Background

Following the bulk data-processing improvements communicated in the previous release, we have added an extra validation check to help keep the platform stable when large data volumes are imported or deleted.

The redesigned processing pipeline already enables the platform to handle larger payloads more reliably and process data load and delete operations more efficiently. With that increased capacity, the platform now also checks whether the destination list table has a compatible unique index on the key fields used by the import before allowing large upserts to proceed.

This check helps prevent large imports from running in a way that could slow down the wider environment. If the required index is missing, the import is stopped before it can affect platform stability.

This update applies to the same endpoints covered in the previous release communication:

• POST {list}/data/load
• DELETE {list}/data
• POST {list}/segments/{seg}/data/load
• DELETE {list}/segments/{seg}/data

Solution

Before processing a large bulk import, the platform now checks whether the destination table is set up to support the import efficiently.

The platform checks for a compatible unique index on the key fields used by the import. This helps protect performance and prevents large imports from slowing down the wider environment.

The import behaves as follows:

Scenario	What happens
A compatible unique index exists on the import key fields	The import runs at full performance with no additional limits.
No compatible unique index exists, and the destination table contains about 5 million rows or more (estimated)	The import is rejected before any data is processed.
No compatible unique index exists, the destination table is smaller, and the import contains more than 100,000 records	The import starts, but is stopped when the 100,000-record limit is reached.
A non-unique index exists on the key fields	The import does not pass the validation check. A unique index is required.

What it looks like in the solution

To benefit from the performance improvements and avoid blocked imports, make sure each affected list has a unique index on the key fields used for bulk data loads.

1. The recommended approach is to define the business key using the API endpoint introduced in the previous release notes:

PUT /organizations/{organization}/lists/{api_name}/businesskey

When no matching unique index already exists, the platform creates one automatically. Existing unique indexes managed by your database administrator are not changed.

2. Alternatively, your database administrator can create a unique index directly on the same key fields in the underlying table.

Note: Before creating a unique index, check whether duplicate records already exist for the selected key combination. Duplicate data must be resolved before the unique index can be created.

 

Corrections

• Imports/Exports overview no longer wrongly shows "Last Execution" label in the "Next execution" popup.
• Segments counts are now readable where before new UI changes made these difficult to read.
• Folder rights from parent folder are now applied to new folder when created by user without folder rights.
• Cadence alert priority is now set to HIGH when cadence plan is in error after clashagent restart.
• It is again possible to edit the button link in a Content Block.
• A Single Batch Journey instance is now loading the content editor correctly when created through template
• Invalid sgmc syntax in a Content Block blocks you from opening the emails using that Content Block. This has been resolved.
• Removing a Content Block from a Content Block component in a message now clears the Content Block version input field.

An overview of all planned maintenance is available from the online help; please check out the following topic for a complete overview for 2025. Please note that these maintenance dates apply only to Windows updates and database maintenance and are not related to release updates.

Next upcoming maintenance is:

US - 01:00 -05:00 AM CST	EU - 00:00 - 04:00 AM CET+1
June 11, 2026	June 9, 2026
June 25, 2026	June 30, 2026
July 9, 2026	July 14, 2026

The status page provides you with regular updates regarding the status of the Selligent platform in the event of a major system incident in your region. In this article we’ll explain the information you will see and how to subscribe to the Selligent notification system to receive regular updates on the platform status, which we highly recommend to all users.

Click here for the Platform Status page.

For more information on the Platform Status page, including signing up for notifications, see the Platform Status documentation.