How Do CRM Queries and a Segmentation Workspace Work Together?

CRM queries identify donors who meet your criteria. A segmentation workspace brings those query results together so your team can apply campaign priorities, exclusions, and channel rules, then validate the resulting audiences. The CRM remains the system of record.

For teams using Raiser’s Edge NXT, the practical question is how a trusted query becomes a campaign audience that fundraising and data staff can both explain.

What stays in the CRM, and what happens in the workspace?

Keep reusable selection logic close to the donor records. Use the workspace to organize how those selections work together for a particular campaign.

One person may cover several roles. What matters is knowing who can change source criteria and who decides campaign treatment.

How does the handoff work in AmpliPhi?

1. Agree the audience definition. Record the query name, purpose, date range, and owner. Confirm what a returned record means before using the count.
2. Use the connected source query. In AmpliPhi, teams can open the query in its source system to inspect or update its criteria.
3. Organize the campaign. Add audience priorities, inclusions, exclusions, and communication eligibility. Keep the reason for each campaign-specific exception in your agreed planning documentation.
4. Refresh and validate. Check when the source results were calculated, review the affected campaign audiences, and investigate unexpected changes before applying assignments.
5. Apply and verify. Push the campaign segmentation details back to the CRM. Check the resulting assignments and the lists used by your email, mail, or calling team.

Your communication systems still deliver the campaign. For the broader product capabilities, see the AmpliPhi overview.

Why can a correct query produce a smaller campaign audience?

Consider this illustrative reconciliation for a hospital foundation appeal:

• A source query returns 1,000 donors.
• 100 belong to a higher-priority campaign audience.
• A further 50, separate from those 100, meet an agreed campaign exclusion.
• The resulting segment contains 850 donors, before channel eligibility is applied.

The query count and segment count answer different questions. Compare the records removed at each step before changing the query. An email audience may be smaller again because some donors are ineligible for that channel.

For who should approve hospital campaign exceptions, use our hospital foundation campaign approvals article.

What should you check when counts change?

Start with the cause of the change:

• Different source records? Review CRM updates, query criteria, and the calculation time.
• Different campaign membership? Review priority, inclusions, and exclusions.
• Different channel totals? Review communication eligibility and preferences.

A connected query does not mean every campaign count is continuously current. AmpliPhi retrieves query results at specific moments; check the last calculation and refresh the relevant results before validation.

When is a CRM query enough?

A query may be sufficient for a straightforward appeal with a small number of audiences and a clear validation process. A workspace becomes useful when your team repeatedly reconciles overlapping results, campaign exceptions, and channel lists by hand.

Test the workflow with one campaign

Bring an existing source query, your intended audiences, and one example of a count that takes time to explain. Book an AmpliPhi discovery call to review how the query, campaign rules, and final assignments could work together.