2026 Release Notes

February 2026 - 6.0.0

Release is scheduled to deployment on Thursday, February 5th, 2026 at 3pm ET.

Technical Upgrade

We are performing a technical upgrade to our platform as part of the release next week. This upgrade modernizes our infrastructure, improves security, and ensures the long-term reliability of your services. To ensure a smooth transition, we will run both the new and current versions of our platform side-by-side starting on Monday, and will slowly over the next few days be rolling out the upgrade. 

This approach allows us to closely monitor performance and quickly address any issues, ensuring there is no disruption to services. No action is required on your part, and you should not notice any changes to your day-to-day operations. If you have any questions or notice anything unusual, please contact our support team.

The other items (below) included in this release will also be gradually rolled out with the technical upgrade. All release items will be available after the upgrade is completed on Thursday.

Coming Soon

Development work continues on three major initiatives – Smart Pages, event waitlist, and SMS inboxing. These exciting additions are planned for release in early 2026. While details about these new features are not included in this release, we’re busy laying important groundwork — building out the backend framework and foundational components that will support their development. Watch this session from ENCC D.C. to get a look at Smart Pages!

Notable items in this release

Segments now available in Marketing Automations

We’ve expanded the Marketing Automations feature to support Segments as automation triggers, giving you a more consistent way to define and target audiences across all Marketing Tools — broadcasts and automations alike.

You can now select any existing segment as the target for an automation. When a segment is used as a trigger, newly qualifying supporters are seamlessly enrolled in the automation after they join the segment.

This release marks the first phase of our plans for deeper integration of Segments within Marketing Automations. In upcoming releases, you’ll see expanded support for Segments, including their use in inclusion and exclusion criteria for even more advanced audience targeting.

Plaid is replaced with Stripe Financial Connections: After listening to feedback from clients, we are deprecating Plaid in favor of Stripe's own bank verification system, known as Financial Connections (FC), for ACH transactions. After this release, all Stripe ACH transactions will be processed directly through Stripe, and not Plaid. There is no additional setup needed, and the existing “ach” payment type will be used. Note that in our last release, we added “ach_stripe” as a temporary payment type, enabling you to test the new bank verification flow before we made this switch. This temporary payment type will be removed with this release.

Improvements

 Import

• We are now limiting import jobs to a maximum of 500 jobs at a time. 

Gateway

• Stripe: Further improved fraud detection while using the Stripe gateway.

Symbolic Pages

• Symbolic giving donation pages now support digital wallets.

VGS

• Updated library to latest version to address autofill issues with Safari 26.

ROI

• Updated authentication method to be based on client ID and secret (OAuth 2.0). Existing clients' credentials have been updated.

Peer-to-Peer

• Added ability to duplicate an existing automation email for coaching, milestone, and registration emails.

Bug Fixes

Segments

• When selecting Symbolic Gift Product as a segment criterion in either the broadcast audience segment creation or segment builder, an error message appeared in the UI: “There was a problem with that action — can’t access property ‘content’, t\[0\] is undefined.” This has been fixed.

• There was an issue with the Advocacy Target Pages data category in Segments, preventing the participating filter from working as expected. This has been resolved.

Fundraising

• In the Transaction Details View of the Gift View Report, the "Next Recurring Payment Date" was shown incorrectly. This was fixed.

Peer-to-Peer

• When registering a main participant with two dependents using a paid participant type and applying a discount code, the checkout page and the registration payments record were showing different discount calculations. This was fixed.

• Previously, if a supporter paid for their Peer-to-Peer registration on a different day than their original registration (PFRP) transaction, their PPAY (registration payment) transaction would be backdated to the date they originally started their registration. This caused these delayed PPAY transactions not to come out of the Bulk Export API. This has been fixed so PPAY transactions correctly reflect the date the payment was made.

• Previously, fundraisers with "BLOCKED" status counted against the registration limit for their participation type. This has been fixed so that blocked fundraisers' registration slot returns to the pool of registrations available.

• Cloning P2P site did not properly copy over event fields. This was fixed.

• When viewing a supporter in Lookup Supporter, the Peer-to-Peer Summary gadget incorrectly shows no activity even though the supporter has confirmed peer-to-peer registration data. This was fixed.