The improved Contacts and Transactions table experiences are now available in Keela, with a rebuilt foundation that makes it easier to find the right records, build precise audiences, and work with complex data logic in one place.

This upgrade introduces a more powerful filtering model, improves how transaction-related filters are organized, and supports more scalable workflows for segmentation, auditing, and exporting.

What you’ll notice

• A new, more powerful way to filter records using Filter Groups and AND/OR logic (without needing workarounds).
• A smoother “single workflow” experience for building complex audiences and refining lists in real time.
• Clearer organization for transaction-based filtering, often starting with All Transactions (COUNT) or All Transactions (SUM) before adding transaction attributes.
• More flexible date filtering with relative date options (such as “in the last 30 days”) to keep filters and segments evergreen.
• Updates to how transactions display in the Transactions table (to make auditing easier).
• Export improvements, including removed export limits and a new exports download workflow via notifications.

What changed in Contacts and Transactions

1) Filtering has a new mental model: Filter Groups + AND/OR logic

The biggest change in this release is how filtering works.

Filters now live in a side panel, and you build logic using Filter Groups. Filter Groups make it easier to:

• Organize related conditions together
• Nest conditions for more complex logic
• Control where AND and OR apply in your filter logic

Why this matters: Previously, complex audience building often required creating multiple Segments and then merging them to simulate OR logic. Now, you can build complex, multi-layer logic directly in one workflow.

Example:

If you want to find:

• Company contacts who have given $500+, OR
• Individual contacts who have given $100+

You can now build that in one filter flow using OR logic, instead of creating multiple segments and merging them.

2) Results update as you build (faster iteration and “sanity checks”)

As you add or remove conditions, you can quickly see how your results change, including the Contact Count, so you can validate that your logic is producing the audience you expect.

This is especially helpful when you are building:

• Fundraising outreach audiences
• Event invitation lists
• Donor reporting cohorts
• Any audience that needs multiple layers of logic

3) Transaction-related filters may look “moved” at first (COUNT/SUM is often the starting point)

You may notice that some transaction-related filters do not appear immediately in the upgraded tables.

This is intentional. In the upgraded experience, many transaction attributes now follow a COUNT or SUM “starting point.”

What this means in practice:

• If you are in the Contacts table and you want to filter contacts by something about their transactions, you will often start with:
  • All Transactions (COUNT), or
  • All Transactions (SUM)
• After adding COUNT or SUM, Keela reveals additional transaction attributes you can filter by, such as:
  • Campaign
  • Impact Areas
  • Date Received

This structure keeps the filter list cleaner and makes it easier to build more precise, cumulative logic in one place.

4) Relative date filtering makes segments and filters more evergreen

This release also includes more flexible date filtering.

Instead of manually updating date ranges month after month, you can often use relative dates, like:

• “in the last 14 days”
• “in the last 30 days”

This helps keep recurring lists and saved logic current without constant maintenance.

5) Transactions table auditing is easier (one row per transaction total)

If you spend time auditing transactions, here is an important workflow change:

In the upgraded tables, the Transactions table typically shows:

• One row per transaction total, instead of multiple rows for individual line items.

To review the items that make up a transaction total, click into the transaction record to see the underlying details.

This is a small change, but it can make the transactions list easier to scan at a glance.

6) Large-list navigation is smoother

When working in very large lists, navigation is smoother, including the ability to quickly move to a specific page number within the table.

Segments: what’s changing and what you need to do

As part of this upgrade, Keela is retiring the legacy Segments builder.

That means:

• Your existing saved Segments will not automatically move into the new Segments experience.
• If there are Segments you want to keep using, you will need to rebuild them using the new filtering system. Learn about the Segments Migration.

Why the rebuild is worth it: the new experience is designed to make rebuilding faster, and it is a good opportunity to clean up older Segments you no longer use.

Important date

• August 18, 2026: the legacy Segments feature will be fully removed, so you should rebuild key Segments before this date.

Exports: limits removed + where to find your downloads now

Exports have been updated in several ways. The most important workflow change is where export downloads and export history now live.

Export limits removed

Keela removed the previous export limits.

• You are no longer capped at 50,000 rows.
• Large exports (for example, 90,000+ rows or your full database) are now supported.

Where your exports appear now (important workflow change)

When you run an export from the upgraded tables experience, the export download is now delivered through Notifications.

• New exports show up in your notification bell with a Download file link.
• If you need to download the same export again later, you will return to Notifications. Exports generated from the new tables can be re-accessed from there.
• The Download file link may regenerate from time to time, so it is okay if you come back later to download again.

What changed: Previously, users could go to Personal Settings to view Export history. With the upgraded tables experience, export downloads and your export “history” are accessed through Notifications instead of an Export History page.

Export templates: where to build and edit them

Export template behavior is also changing.

• For exports using the upgraded tables experience, you will manage templates within the export modal (instead of going to Personal Settings).
• Templates created for the previous tables experience may not match the new table structure. You may need to create new templates in the updated workflow.

Accessing older templates and older export history

If you need access to older export templates or older export history from before this upgrade, you can still find those through Personal Settings (during the current beta phase).