PeopleStage release notes 2026

Q3 2026¶

28 September, 2026

New Trustpilot integration¶

You can now set up the Trustpilot integration from PeopleStage, authenticating with an API key and secret instead of a username and password.

For administrators¶

Designer deployment requires a matching Web Service version¶

From Q3 2026, Designer can only deploy to a Web Service running the same version. We recommend upgrading all your Apteco software together. See full details.

Q2 2026¶

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
Over: Contacts who have been waiting longer than the specified time

Pool wait vs pool journey

Both steps filter contacts based on how long they've been waiting in a pool. 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:

Because 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.
Orbit now includes all intermediate steps when calculating preview counts, improving their accuracy.

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.

You can now authenticate using client secrets as an alternative to OAuth. When you don't enter 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¶

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.
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.