Engage

Add Test Customers from the Test and Preview Page

Users can now add new test customers directly from the Test and Preview page, not just the campaign settings. This enhancement streamlines the testing process, offering greater flexibility and efficiency for campaign validation. The update improves user workflow by reducing navigation steps and making test customer management more accessible during campaign setup.

Documentation link - https://docs.capillarytech.com/docs/test-and-preview-across-engagement-channels

Wait for Future Event Context Tags in Journey Engagement Blocks

You can now personalize engagement block messages using context tags derived from the Wait for future event block configured in a journey. When a customer performs the specified event and moves to the next step, both entry event-based tags and Wait for future event context tags become available in the engagement block editor. This allows brands to send highly personalized communications based on the customer's actions at each stage of the journey.

Documentation link: https://docs.capillarytech.com/docs/context-based-tags-in-engagement-block

Ignore Unsubscribed Users in Campaign Delivery

You can now send communications to the complete audience list by enabling the Ignore Unsubscribed Users option during campaign configuration. When enabled, the system checks whether users are reachable on the selected channel at the time of delivery and sends the communication even if they have unsubscribed. This helps brands bypass the unsubscribed user flow when required and ensures important communications can still be delivered.

Documentation link: https://docs.capillarytech.com/docs/configure-communication-channel-settings#send-messages-to-unsubscribed-users

Customer Data Platform

Allow reuse of identifiers held by campaign and victim users (V2 API)

Previously, when a V2 API request tried to assign a mobile number, email, or external ID to a customer, the request failed if that identifier was already held by a campaign user (a non-registered user) or a victim user (a merged-away account). This caused registration and profile-update flows to block unnecessarily when the identifier was held by an inactive account.

A new org-level configuration, CONF_ALLOW_CAMPAIGN_AND_VICTIM_USER_IDENTIFIER_REUSE, allows the API to automatically clear the conflicting identifier from the campaign or victim user and assign it to the requesting customer. This applies to mobile, email, and externalId identifiers for source=INSTORE requests. Contact Capillary Support to enable this configuration.

Documentation link: Add or Remove Customer Identifiers

Transaction Update API: Support for Return and Not-Interested Transactions

The v2 Transaction Update API now supports updating extended fields and custom fields for RETURN, NOT_INTERESTED, and NOT_INTERESTED_RETURN transaction types. Previously, only regular transactions could be updated. Use the new type field in the request body to scope the lookup. Note: MIXED transactions are not yet supported.

Documentation link: Update Transaction

Loyalty+

Remove loyaltyProgramEnrollments from Customer API Documentation

The loyaltyProgramEnrollments object and its sub-fields (programId, tierNumber, loyaltyPoints, tierExpiryDate, pointsExpiryDate) have been removed from the request parameter tables and code examples across customer API pages.