User Documentation
Start typing to search…

October-November-December 2025

Platform

OTP Rate Limiting for New Organizations

We have implemented rate limiting for the OTP validation API for all new organizations created after 15th October 2025. Existing organizations are encouraged to enable this configuration for improved security.
Documentation: https://docs.capillarytech.com/reference/validate-otp#/

Enhanced Event Notification UI

The Event Notification UI now provides visibility into event payloads and delivery statuses. Users can view events and access webhook-level logs, improving troubleshooting and integration processes. This enhancement streamlines event notification management and reduces reliance on external tools for testing. Documentation: https://docs.capillarytech.com/docs/manage-webhook#/
https://docs.capillarytech.com/docs/view-event-feed#/

Correction of SKIP_DOWNSTREAM Parameter

The SKIP_DOWNSTREAM parameter has been updated to skipDownstream. With this change, you can add or update v2 customer and transaction records through the API without notifying downstream systems like EMF. It is especially helpful during data migration or small fixes, where you want to upload or correct data without triggering any loyalty actions. This makes data updates easier and removes the need for extra imports. Documentation: https://docs.capillarytech.com/reference/v2-add-customer#/ https://docs.capillarytech.com/reference/add-customer#/ https://docs.capillarytech.com/reference/update-customer-detail#/
https://docs.capillarytech.com/reference/add-transaction-single#/
https://docs.capillarytech.com/reference/addreturn-transaction-bulk#/
https://docs.capillarytech.com/reference/update-transaction#/
https://docs.capillarytech.com/reference/update-transaction-bulk#/

Bulk User Deletion Added to Self Serve User Management

Users can now delete multiple accounts simultaneously within the Self Serve User Management interface. This enhancement streamlines administrative tasks, saving time and reducing manual effort. The feature improves efficiency for organizations managing large user bases, ensuring smoother user management workflows and greater control over account maintenance.

Documentation: https://docs.capillarytech.com/docs/onboarding-user#deleting-users-in-bulk

Engage

Support for Undelivered Communication Events in Journeys

We have introduced support for undelivered communication events in journey flows, allowing marketers to create fallback paths for users whose messages failed to deliver. This enhancement enables more effective engagement strategies by targeting users based on their delivery status, improving overall communication effectiveness.

Documentation: https://docs.capillarytech.com/docs/overview-journey#engagement-event-conditions

Launch of Issue Loyalty Promotions Block for Journeys

The new Issue Loyalty Promotions block allows Journey builders to seamlessly enrol customers in loyalty promotions and issue benefits directly within workflows. This integration enhances automation and personalization, reducing manual intervention and improving customer experience.

Documentation: https://docs.capillarytech.com/docs/action-building-block#/issue-incentive

Journey Attribution and Conversion Tracking Feature Released

The new Journey Attribution feature allows brands to define conversion goals for their journeys, enhancing performance tracking and optimization. This capability enables better analysis of customer interactions and improves decision-making for marketing strategies, ultimately driving higher ROI.

Documentation:https://docs.capillarytech.com/docs/configure-journey#configuring-the-conversion-goal-optional

Enhanced Date Field Comparisons in Journeys

We have introduced the ability to compare date fields within entry triggers in journeys. This enhancement allows users to set conditions based on transaction dates relative to customer registration dates, improving journey customization and decision-making capabilities.

Documentation:https://docs.capillarytech.com/docs/configure-events-and-conditions#event-profiles-and-attribute

Introducing Random Split Activity in Journey Builder

Marketers can now utilize the Random Split activity to divide contacts for A/B testing and personalization. This feature enhances campaign effectiveness by allowing flexible distribution percentages, ensuring optimized customer journeys through data-driven insights.

Documentation: https://docs.capillarytech.com/docs/flow-control-building-block#/random-split-block

Personalization now available in Webhook Blocks

Introducing personalization tags in the webhook block, enabling journey builders to dynamically access event attributes within the webhook block. This provides flexibility for external system integrations, improving journey personalization and automation using entry events.

Documentation: https://docs.capillarytech.com/docs/supported-labels-for-engagement-channels#/

Expanded Personalization Tags in Journeys and Campaigns

New tags for Registered Concepts and Gap to Upgrade are now available in both Journeys and Campaigns, enabling more precise and personalized customer communication. Additionally, event date tags have been introduced for Journeys. These enhancements bring consistency of tags across campaigns and journeys.

Documentation: https://docs.capillarytech.com/docs/supported-labels-for-engagement-channels#/

Documentation: https://docs.capillarytech.com/docs/configure-events-and-conditions#event-profiles-and-attribute

Incentives

Enhanced Pagination and Query Parameters for Coupons API

The Coupons API now features pagination and advanced query parameters to streamline data retrieval. You can retrieve coupon series more efficiently by managing result sets using offset and limit, and filtering results precisely by coupon status. Refer to the documentation

Enhanced Cart Promotions for Points Payment

The cart promotions now support new tender mode conditions and product combo conditions, allowing marketers to create promotions based on payment modes and specific product combinations. This enhancement enables more flexible promotional strategies, improving customer engagement and satisfaction. Eg. "Buy Coke & ChocoBrand biscuit with Points payment mode, and get 50% off on Maggi noodles."
Refer to the documentation

Add SeriesCode Support in Get coupon series API

The Get coupon series API now supports fetching offer details using seriesCode filter, in addition to seriesId. This enhancement simplifies third-party integrations by allowing direct access to offer details, eliminating the need to loop through lists. Refer to the documentation

Edit Restrictions on Expired Rewards

The reward catalog now allows updating restriction settings for expired rewards without duplication. This allows for easy error correction and future reuse by marketers, while ensuring the status remains expired.
Refer to the documentation

Support for Coupon Code Prefixes and Suffixes

Coupons now allow you to add custom prefixes and suffixes to your coupon codes. You can set these for your whole organization or for specific coupon series. This makes it easier to organize and recognize your codes.
Refer to the documentation

Hydra SDK - React Native

Version 1.4.0

  • Added isHydraInitialized function to check if the hydra initialization is completed
  • Usage of HydraConfig.plist and hydra_config.json is deprecated
  • Use only one Github token, using .env for Github credentials is deprecated, reading these credentials from system environment.
  • Notification icons, placeholder icons and notification color should be added to the react native codebase. Adding to android resources and Images.xcassets is deprecated.
  • Fixed Linker issue with iOS when we were using ios frameworks in dynamic linking

Refer to the documentation for details.

Hydra SDK - iOS

Version 1.7.3

  • Added customerId to all logs for improved traceability.
  • Introduced an info log when a notification is received by the extension.
  • Enhanced real-time debugging: when remoteDebugLevel is enabled, INFO logs now bypass batching and are sent immediately for faster visibility into critical events.
  • Added detailed info logs for all HTTP API calls, including request details.
  • Included all DLR events (received, shown, clicked, dismissed, rejected, ignored) in INFO logs for better monitoring and analytics.
  • Fixed issue of unread notification count is not increasing in built-in- Notification center when app is in foreground

Refer to the documentation for details.

Loyalty

Better pagination for the Get customer redemption API

The Get points redemption API now supports limit and offset for easier pagination. This update improves efficiency and flexibility when retrieving customer redemption records.
Refer to the documentation

Idempotency Support for Manual Currency Allocation API

The manual point allocation API now supports a uniqueId parameter for idempotency. This enhancement prevents duplicate point or currency allocations during network retries or partial failures, ensuring customers receive rewards only once per request. The update improves reliability and safeguards against accidental duplicate processing in bulk or repeated API calls.

Documentation: https://docs.capillarytech.com/reference/issue-reward-currency#/

Central Communication System Integration for Loyalty Actions

Loyalty+ now uses the Central Communication System (CCS) for key workflow actions, including Renew Tier, Allocate Points, Upgrade to Tier, and Issue Coupon. This enables seamless, centralized messaging across channels like WhatsApp and LINE, improving reliability and scalability for loyalty program communications. Documentation: https://docs.capillarytech.com/docs/actions

Neo Extension

Code review

The new Code review feature in Neo introduces a structured review and approval process for dataflows. Neo Admins can now review changes through a dedicated Review Changes modal, which provides a clear view of updates across four tabs: Summary, Comments, Description, and Code Diff. The feature supports both AI-generated and admin review comments. Users can also resolve AI comments automatically through Fix with AI.

Refer to documentation

Applications

The Applications feature in Neo introduces a structured way to organize dataflows by grouping them into logical containers based on their purpose or business function. Neo now supports three application types—Default, Middleware, and Custom—each with specific behaviors for how dataflows are classified and managed. Users with Neo Edit permission can create up to 20 custom applications, move dataflows between custom applications, and rename them. Middleware dataflows are system-managed and automatically classified based on pre-matching or post-matching tags. This feature improves visibility, reduces clutter, and makes it easier to locate and maintain dataflows as organizations scale.

Refer to documentation: https://docs.capillarytech.com/docs/using-applications#/

Dev console

App Request Logs and Neo Log Insights

The App Request Logs page in the Dev Console enables you to view all transactions sent by an application to New Relic within a selected time range. This feature allows you to trace requests, filter logs using New Relic and custom headers, and quickly identify specific requests or failures.

For Neo applications, a new Neo Log Insights view is now available. Selecting a Request ID opens detailed execution insights, including raw logs, block execution flow, errors, block I/O, DAO-based inspection, and request metadata. These enhancements improve debugging efficiency and provide deeper visibility into application and dataflow behavior.

Documentation: https://docs.capillarytech.com/docs/view-app-request-logs#/

Updated 3 days ago