Skip to content

PeopleStage release notes 2026

Q2 2026 Latest release

5 June, 2026

Improved Pool journey time-frame options

The pool journey audience step has updated time-frame options when filtering contacts by how long they have been waiting in a connected pool. You can now select Over or Within a specified timeframe.

The Selected for control now supports:

  • Within: Contacts waiting less than or equal to the specified time period
  • Over: Contacts who have been waiting longer than the specified time period

Pool wait vs pool journey

Both steps filter contacts based on how long they have been waiting in a pool, but they differ in which pool they evaluate:

  • Pool wait: Evaluates how long a contact has been waiting in the immediately preceding pool
  • Pool journey: Lets you choose any pool that appears above the current audience step in the diagram

Improved Orbit campaigns

The following updates apply to users viewing Orbit Campaigns through PeopleStage:

  • As a result of the expanding functionality in Orbit campaigns, when viewing Orbit campaigns in PeopleStage, you may see examples of an audience being directly connected to another audience. For example, where the campaign is using an audience split flowing into a time delay.
  • We've made improvements to the way Orbit returns preview counts, with all intermediate steps included when calculating the counts.

Q1 2026

25 March, 2026

Improved Microsoft Dynamics 365 integration

The Microsoft Dynamics 365 integration with PeopleStage now includes improved diagnostic logging and support for client secret authentication. The system now outputs all warnings returned from Dynamics to help you troubleshoot integration issues more effectively.

You can now authenticate using client secrets as an alternative to OAuth. When you don't specify an AppId in the channel configuration, the integration automatically uses client secret authentication instead. In this mode, use your ClientId as the username and the Secret as the password.

Bug fixes

  • We’ve fixed an issue where orphaned records in transactional campaigns displayed the maximum integer value in the AgentURN field instead of NULL when the parent table used a numeric reference field.
  • We’ve fixed an issue where percentage calculations were incorrect in campaign previews when you applied a filter constraint alongside include or exclude groups with volume constraints.
  • Voucher code queries now run more efficiently in the Orbit API and voucher code admin panel.