Version March 19, 2026 - 5.116

Brand update: Zeta rebrand continued

Zeta Global, the AI marketing cloud, recently acquired Marigold's enterprise software business. This brings the Marigold Enterprise products including Cheetah Digital, Selligent, Sailthru, Grow, Loyalty, and Liveclicker into the Zeta family, strengthening Zeta's ability to help brands deliver more relevant, personalized customer experiences at scale.

As part of this transition, we began a phased rebrand to align these products and the help center with the Zeta brand.

In January, we replaced the Marigold name and logo with the Zeta name and logo, along with visual updates.

In this second phase of visual brand transition, we're updating the logos, brand colors, fonts and visual styling to provide a refreshed and consistent Zeta brand experience across products and the help center. You will notice brighter pages and updated blue tones throughout, proudly reflecting Zeta Global.

These updates are branding-only and do not affect product functionality, data, integrations, or existing configurations. You can continue working as usual.

As part of this transition, the Help Center has moved to a new domain.

• The Selligent Help Center is now available at https://products.zetaglobal.com/selligent/EN/Content/LandingPage.htm
• The Help Center home is available at https://products.zetaglobal.com/Content/MarigoldHelpCenter.htm

Update any saved bookmarks to ensure continued access.

If you have questions, please contact your Zeta representative.

What it looks like in the solution

Before:

New:

Note: Screenshots in the Selligent Help Center won't be updated retroactively but will be updated bit by bit while introducing new product features and updates.

 

Publishing and versioning of Content Blocks

ROLLED OUT GRADUALLY OVER THE COMING PERIOD

Background

Marketers rely on reusable Content Blocks—like headers, footers, offers, and legal copy—to keep messages consistent. But until now, updating a block meant hunting down every message that used it and republishing each one—a slow, error-prone process that could leave customers seeing outdated content.

Solution

By introducing publishing and versioning of Content Blocks, we remove that friction. You can update a block once, publish it, and the change automatically flows to all messages that use it. Versioning also gives you clear visibility into what changed and when, so teams can collaborate confidently while keeping brand, legal, and design elements in sync—without the manual rework.

What it looks like in the solution

Whenever a Content Block is updated, you can make the applied changes available for use in messages, by publishing the Content Block. With each publication, a new version of the Content Block is created. These are all accessible from the Publication History overview:

You can view the content of a version or restore a specific version:

Restoring a version will overwrite the most recent published version with the restored version. Messages using the most recent version will automatically be updated with the restored version, after the Content Block has been published.

Thanks to these versions, you can decide which version to use in your messages.

If you do not want the content to change over time, you can select a specific version of the Content Block.
If you always want to use the latest (most recent) version of the Content Block, that is an option as well.

With this release, a Content Block migration guide is provided.
Additionally, a Getting started user guide is added to help users understand better the different uses of a Content Block.

 

Automatic removal of irrelevant journeys from Cadence Plans

Available to all customers

Background

Cadence plans can get cluttered over time because journeys that ended still appear in the Cadence overview, making it harder to focus on what's currently relevant.

Solution

Journeys that ended and have become irrelevant for the Cadence plan—meaning defined rules in the Cadence plan would no longer take the journey into account—are now automatically removed from the Priorities screen. Only relevant journeys are displayed.

What it looks like in the solution

When a journey is linked to a Cadence plan, but it has become irrelevant for the plan, the journey is automatically removed from the Priorities screen. A journey has become irrelevant when it ended sending out messages (e.g. the send end date is in the past) and there is no defined rule in the plan that would still take the journey into account.

Before:

Irrelevant journeys were visible on the Priorities screen.

New:

Irrelevant journeys are hidden from the Priorities screen.

Note: The Priorities screen is updated after an automatic or manual re-calculation.

Example: Journey A is part of Cadence plan X.
Cadence plan X has the following rule defined: 1 email / week.
Journey A sent out its last email 6 days ago and then ended.

- Today and tomorrow, the journey remains visible in the Cadence plan, as the rule says 1 email / week. The Cadence plan considers the journey as still being relevant, as the week has not yet gone by, and more emails can still be sent during this time frame.
- After tomorrow, the Cadence plan considers the journey as no longer relevant, as a week has passed by in which no emails were sent. The journey will be removed from the Cadence plan Priorities screen, as it has already ended and does not send out any more emails.

Note: When a journey is removed from the Cadence plan Priorities screen, it will still display the linked Cadence plan in the journey properties.

The journey can become relevant and active again in the Cadence plan, when editing the journey and re-activate it again to send out new messages and/or when changing the Cadence plan rules that would re-affect the journey.

View this topic for more details on setting up a Cadence plan.

 

Corrections

• [Admin Config] Accessing a Business Unit from the Channel Endpoints Usage screen starts with a blank search field.
• [Dashboards] Data Studio Pro users can create static segments again.
• [Library — Dictionaries and Labels] Labels can be correctly exported.
• [Library — Dictionaries and Labels] Import labels in chunks and cancel import no longer fail with 415 unsupported media type error.
• [Content] Messages with links to inaccessible journeys (because of missing folder rights) open normally; a clear access error appears only when editing such a link.
• [Content] Message containing multiple links that target different journeys show the correct journey destination for each link.

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
March 26, 2026	March 31, 2026
April 9, 2026	April 14, 2026
April 30, 2026	April 28, 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.