2026 Release Notes

March 2026 - 6.1.0

Disclaimer: Release dates, features, and functionality are all subject to change. As development progresses, sometimes priorities shift and we need to adjust our plans and this can impact timelines. We will do our best to update this information when features, functionality, and release dates are officially confirmed.

Coming Soon

Development work continues on Smart Pages – our next major initiative. This exciting addition to the form-building experience in Engaging Networks is planned for release on April 9th. We are busy putting the final touches on the features that will be offered in Phase 1 of Smart Pages and performing thorough testing. If you missed the roadmap session from January, you can check it out here for a sneak-peek at Smart Pages. 

Notable Updates

Event Waitlist

Introducing: event waitlist capability! You can now allow your supporters to join a waitlist once an event reaches capacity and be offered available spots if they open up. This feature helps organizations maximize event attendance, reduce manual list management, and provide a smoother registration experience when events are sold out.

Improvements

Salesforce

• We are adding additional fields to the Salesforce Connector Contact Mapping that will allow you to pull information from Salesforce and place it into Timezone Offset, Most Recent Contribution, Highest Previous Contribution, and Longitude and Latitude fields in Engaging Networks.

Report Builder

• New "Supporter Report" template now available for the custom report builder. With this report, you can quickly and easily get a full picture of your supporters. The report template pulls together all of the relevant fields for you, so you just need to select your Segment (or choose ‘All Supporters) and follow the steps to download the report. You can also customize the report by removing any fields you don’t need or adding additional fields that are not included in the template. 

Page Builder

• A page-level option to record reference data (en_txn) over utm data when both are present in a donation page URL has been added. To enable this feature, navigate to the Page Settings screen and tick the box under Campaign References. 

• We have updated the Conditional Content interface within Page Builder to provide better control over profile-specific content and prevent the "All Supporters" version from unintentionally overwriting your work.

  • Filtered Dropdown Menu: The conditional content dropdown menu within a content block now only displays profiles that have been specifically enabled for that block. This eliminates confusion regarding which profiles are currently active or being edited.

  • New "Manage Profiles" Action: To add a new profile variant to a block, users now click a Pencil/Edit icon. This opens a management interface where you can explicitly select which profiles should have unique content for that specific component.

  • Consistent Experience: This workflow now more closely mirrors how conditional content is handled in the Email Messaging module, providing a more unified experience across the platform.

Gateway

• Stripe: Migrated ACH skip verification payments from Stripe Charges API to Payment Intents API to comply with upcoming deprecation.

• Paysafe: Initial Paysafe ACH/EFT transactions will now be marked as ‘Pending’ until the transaction is confirmed as successful or not. At that point, the status will update to ‘Success’ or ‘Reject’. This ensures that supporters are not issued a receipt for transactions that are ultimately rejected. If you accept ACH/EFT payments via Paysafe and have a data sync in place, please check to make sure you don’t need to make any updates to your sync logic. 

Marketing Automation

• The recurring status filters in profiles will now exclude donors who updated their card, allowing more accurate targeting of actual cancellations in an EMA.

• Added an “All” checkbox option for payment types in the 'Supporter gift to be processed soon' automation, allowing clients to target all payment types at once.

Marketing Tools

• Email Preview Update: You will now have the option to quickly preview email messages right from the Messaging Broadcasts screen where all campaigns are listed. This will save you time and clicks if you are needing to review sent or draft email messages. Please note: there is no quick preview option for SMS only broadcast campaigns. 

Email Service

• Page notification emails now use custom DKIM keys that match the domain of the email’s From address, and have a sender envelope that aligns with the From address, DKIM domain, and return path, avoiding fallback to legacy http://e-activist.com envelopes.

Peer-to-Peer

• Configurable Site-Level Notifications: We have introduced a new notifications management interface for Peer-to-Peer sites. This feature gives administrators the ability to set up system-generated alerts, ensuring that internal teams stay informed without being overwhelmed by irrelevant data. The key features of this update are:

  • Centralized Notification Hub: A new dedicated "Notifications" section (located near Messaging Automations) allows you to view and manage all site-level alerts in one place.

  • Customizable Recipients: You can select specific account emails to receive notifications for different event types.

  • Active/Inactive Toggling: Easily enable or disable specific notifications using an "Active" toggle or the lightning bolt icon.

  • Current available notifications: New fundraiser registered, New team registered, New family team registered.

  • Coming soon: Notifications for goal-based milestones.

• Bulk Fundraiser Upload: We have introduced a new Bulk Upload feature for Peer-to-Peer sites, allowing site administrators to efficiently onboard large numbers of fundraisers, teams, and dependents via a single CSV file. This significantly reduces the manual effort required for migrating data from other platforms or launching large-scale campaigns. When accessing this feature, you can download a CSV template to help you get your spreadsheet ready to be imported. The key features of this update are:

  • Mass Onboarding: Import individuals, team members, team captains, and dependents in one go.

  • Automated Team Creation: An "Automatically create teams for Team Captains" toggle allows the system to build team structures simultaneously based on your CSV data.

  • Flexible Roles: Various participant roles are supported, including Individual, Team Member, Team Captain, Family Team Captain, and Dependent.

  • Event Field Support: The importer recognizes and maps to existing Event Fields, ensuring specific data like "qualifying times" or "t-shirt sizes" is captured during the migration.

  • Built-in Validation: The system performs real-time checks for email formatting, role permissions, and goal minimums to ensure data integrity before the import is finalized

• We have updated Family Team registration to include the option for teams to be searchable and public. Previously, Family Teams (consisting of a primary participant and dependents) were private by default to protect member privacy. However, this prevented extended family members (like cousins) from finding and joining the same team or the public from donating directly to the team via site search. Therefore, we decided to allow Family Teams to choose if they want to be private or public. Key Features:

  • Privacy Control at Registration: Family Team captains now see a "Make this team searchable" checkbox during the registration process, consistent with regular team flows.

  • Public vs. Private Logic: If left unchecked (which is the default), the team remains private and "invite-only." It will not appear in search results or leaderboards. When checked, the team becomes public, searchable, and joinable by others on the Peer-to-Peer site.

  • Support for Extended Families: This change allows multiple branches of a family to join a single "Family Team" without requiring the captain to manually send private invite links to every individual.

  • Improved Discoverability: Public Family Teams will now appear in site-level search and leaderboards, making it easier for the general public to find and support them.

• We have enhanced the Peer-to-Peer donation management system to allow administrators to edit how a donor's name appears on public-facing Donor Rolls. This provides greater flexibility for honoring specific naming requests or correcting typos without altering the underlying supporter record. Key Features:

  • Custom Display Names: When editing a transaction in the dashboard, administrators can now enter a specific Display Name. If provided, this name will override the default "First Name" on the public donor roll.

  • Maintained Data Integrity: Changing the public display name does not change the name on the underlying supporter's record, keeping your CRM data clean.

  • Anonymous Toggle Priority: The "Anonymous" checkbox remains the primary control. If a donor is marked as anonymous, they will appear as "Anonymous" on the roll even if a custom display name has been entered.

• We have added back and front-end validation to prevent more than 40 registrations in a single Peer-to-Peer registration transaction.

Peer-to-Peer - Legacy

• In response to a large volume of fraudulent Peer-to-Peer campaign pages being created on the legacy tools, we have released a new setting giving organizations the ability to require admin-level approval of all DIY fundraising pages before they are able to go live. Once this feature is turned on, the publication of a DIY fundraising page is stalled until an Admin at your organization logs in, determines if the page was created by a legitimate fundraiser, and approves it. Video demonstration.

Bug Fixes

Gateway

• Stripe: 

  • Improved integration to ensure transaction amounts are correctly updated in Payment Intents when donors retry with a different amount.

  • Updated implementation for skipping radar rules when processing subsequent recurring payments.

• Blackbaud: 

  • Standardized the format of Campaign Data 13 for BBIP single and recurring card donations to ensure consistency across payment types.

  • Resolved an issue where the Payment Type was showing as 'Unknown' for BBIP card payments.

Page Builder

• If a user adds a profile to the conditional content area of a form and the profile is in a different folder than the already assigned profiles, the existing profiles are removed from the form. This was fixed.

• Fixed an issue where In Memoriam merge tag fields were not populating in Custom Notifications when using the Stripe gateway.

• Fixed a markup injection vulnerability in e‑card previews and actual e‑cards by validating and sanitizing the e‑card message field. Only letters, numbers, spaces, and basic punctuation are now allowed.

Marketing Tools

• If a block in the template has been deleted from the account, then the Marketing Tools template will fail to save. This was fixed so that the deleted block will be used as a local block in the Marketing Tools template without being linked to the library.

• Users were able to set up a broadcast with a blank segment. This was fixed.

Marketing Automation

• When a Custom Date automation is set up to send an email 1 day before the date in the custom field, it instead pulls the supporter into the journey on the date in the custom field. This was fixed.

• On February 22nd, user error during a routine code clean-up event caused the data in all marketing automations to become stuck. The mistake was discovered and corrected on February 26th. All active marketing automations are back to working as expected. You are able to identify those supporters who had received at least one message in the journey and were stuck, and at which point in the journey they stopped receiving emails. To do this, download the data from each of your automations, look at the Source column, and locate any supporters for whom the data says “journey:failed”. The column right next to that one (Sequence Received) tells you which emails in the journey a supporter received (there is a separate line of data for each message). You can then determine if you’d like to put them back into a new automation or to simply allow them into your regular email stream.

Segments

• Adding an “Is Suppressed” filter in the traditional segment builder caused an error that prevented users from saving the segment or running get count. This was fixed.

Export

• Previously, the API Options > Transaction Types user interface suggested that individual transaction types (e.g., FCS vs. FCR) could be toggled independently for staging to the Bulk API for retrieval. In practice, these are managed at the category level. The updated interface now features category-level toggles to reflect this behavior accurately.

• Supporter data is now available in ETK, ETA, MSP, and MMR transaction types

Profiles

• Fixed a discrepancy in the Export Supporter Data query builder where supporter counts differed between count and export due to supporters in Email Marketing Automations.

Opt-in

• Some questions and opt-ins could not be deleted, even when they were not used on any live pages or shared components. This was fixed.

Peer-to-Peer

• Previously, when a single supporter registered multiple fundraisers in the same transaction, the registering supporter would show "Paid" while the other registrants would show "Unpaid", though their registration was paid for by someone else. This has been fixed so that upon completing registration payment, all included registrants will show a "Paid" status.

• Previously, there was no direct registration link available in the platform for Participation Types. This has been fixed to show a direct registration link under "Additional Participation Options".

• Previously, if you used a 100% discount code for registration on a Peer-to-Peer site, you would still be redirected to the checkout page and encounter an error when you try to submit your registration. This has been fixed so that supporters who enter a 100% off discount code and don't add an additional self donation will not be redirected to the checkout page to finish their registration.

• Previously, payments in "pending" status did not appear in Peer-to-Peer sites under Registration Payments or Donations. This has been fixed. Pending payments will not count towards totals. 

• There was previously an issue where the minimum commitment page did not properly update when a digital wallet was used to charge the minimum commitment. This has been fixed.

• Previously, refunding an offline gift made to a Peer-to-Peer site did not reflect properly in the site under Donation Management, and also did not change site and individual totals to reflect this refund. This has been fixed. As a result, “Refund donation” will now be allowed for all cash and check donations in the single donations gadget (whether made via a Peer-to-Peer site or page-builder) and refunding these transactions will properly create an RFD (or PRFD in the case of Peer-to-Peer offline transactions) row. 

• Previously, the setting "Prevent the Page Builder editor from visually rendering this template" was not respected in Peer-to-Peer site page building. This has been fixed so that the setting is respected in Peer-to-Peer site page building.

February 2026 - 6.0.0

This release was deployed on Thursday, February 5th, 2026 at 3pm ET.

Technical Upgrade

We are performing a technical upgrade to our platform as part of this release. This upgrade modernizes our infrastructure, improves security, and ensures the long-term reliability of your 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 rolled out with the technical upgrade. All release items will be available after the upgrade is completed.

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.