Pardot for nonprofits · donor segments
Pardot is paid for.
Nobody on the team can build a donor segment.
I teach your team to build its own donor segments in four working sessions, paid from the 8 hour support plan at €520 a month. Account Engagement (formerly Pardot) segments only on data it can read about each person, and NPSP and Agentforce Nonprofit keep giving history where it does not look by default.
Written for a Director of Fundraising, a CRM manager or a supporter care lead at a charity that already pays for Account Engagement. Support plans run three months minimum. Updated 14 November 2026. By Serhii Skrypnyk, Senior Salesforce Administrator, Marketing Cloud Account Engagement Consultant since September 2024 on Trailblazer.
Written by Serhii from his own Account Engagement and Nonprofit Cloud work; facts checked against Salesforce documentation on 14 November 2026.
The name
Is it Pardot or Account Engagement, and what should a charity check?
The same product: Salesforce renamed Pardot to Account Engagement in 2022, full name Marketing Cloud Account Engagement (MCAE), and has published no end of sale, so a charity that pays for it can build on it now. What that means for timing, and whether to move, is on Pardot in 2026.
- 01
Account Engagement+ needs Data Cloud for its newest features
Agentforce, cross object merge fields and SMS need Data Cloud connected, per Salesforce’s post of 15 July 2025, which does not mention nonprofits; what each edition includes is on Pardot pricing.
- 02
Agentforce Nonprofit holds the gifts, Account Engagement sends the email
Since 2 December 2025 Salesforce sells Nonprofit Cloud as Agentforce Nonprofit, formerly Nonprofit Cloud. Plenty of charities run Account Engagement on NPSP instead, which Salesforce still supports: NPSP or Nonprofit Cloud.
The rename: Salesforce’s post of 6 April 2022. No end of sale: the FAQ on the Account Engagement price page, undated and “subject to change”, read on 14 November 2026.
Donor segments
How do you build donor segments in Account Engagement from NPSP or Nonprofit Cloud data?
One dynamic list per segment, on data Account Engagement reads: prospect fields, and gifts as opportunities. On NPSP a gift reaches a prospect only through a contact role. On Agentforce Nonprofit totals sit on Donor Gift Summary. I have built flows that total gifts onto the person account; copying these fields is the same pattern, one I have not built.
| SegmentCriteria, as fields the prospect can read | Used for |
| Lapsed, 13 to 24 monthsLast gift date between 13 and 24 months ago, and no active recurring gift. NPSP: the contact’s last gift date rollup. Agentforce Nonprofit: Last Gift Date on Donor Gift Summary, copied to the person account. And email consent recorded: as of 14 November 2026 every gift in this window predates 5 February 2026, so the soft opt in does not cover the details collected with them; it covers only details collected from that date | Win back |
| New donorsTotal number of gifts is 1 and the first gift date is in the last 90 days | Welcome |
| Regular giversAn active recurring gift, flagged on the contact or person account by a flow, which works on every edition | Thank, no ask |
| Engaged, not givingAccount Engagement score above the line your team sets, and no gift in 24 months | Call list |
| Do not emailOpted out, a Fundraising Preference Service request, marked deceased, or an address that qualifies for neither consent nor the soft opt in | Suppress |
The windows and thresholds are a starting point, not a standard. Sources, read on 14 November 2026: NPSP’s first gift date, last gift date and total number of gifts in Trailhead’s Enable Customizable Rollups. Three points come from Salesforce Ben, a third party publisher, because the Account Engagement developer pages refused automated requests: dynamic list members are “added/removed automatically whenever they match/unmatch your set criteria” (updated 20 September 2024); an opportunity syncs only with at least one contact role, and its fields work as list criteria (updated 13 September 2024); custom object sync runs on Advanced and Premium, and as a Plus add on, and can mirror standard objects too, except the six the connector already syncs: leads, contacts, person accounts, accounts, opportunities and campaigns (updated 16 September 2024). So Donor Gift Summary may be reachable that way; I have not tested it. The flow route is the one described above. Its field names are as they appear in an Agentforce Nonprofit org I work in.
- 01
Supporters with no email never become prospects
Trailhead’s connector unit, read on 14 November 2026: “records aren’t created when there is no matching email address”, and changes are checked about every 2 minutes. Count contacts with no email first; donors from paper forms and bank files are usually most of them.
- 02
On NPSP, a gift with no contact role is invisible
NPSP can create the contact role for you and gives the Donor role to the person who gave, per Trailhead’s soft credits unit. Gifts loaded by an import or an integration that bypasses NPSP are the ones to count before any segment uses opportunity criteria.
- 03
Person accounts are supported, and still worth one test record
Agentforce Nonprofit keeps individual donors as person accounts, per Trailhead’s stakeholder unit, and the connector supports them. Still, “I have enable person account in Account Engagement and map the custom fields. But I am not getting data into prospect,” a Trailblazer Community member wrote on 7 November 2023. Change one test donor’s field and watch it arrive on the prospect.
- 04
Households are not documented
Salesforce does not document how an NPSP household account appears on the Account Engagement side, and I found no Salesforce page on the connector with Agentforce Nonprofit specifically. Segment on fields of the person, and check three households by hand before any segment depends on household fields.
- 05
The Salesforce report you check against can be wrong too
Compare each list’s count with Salesforce before the first send, and use a direct query rather than trusting a report. On an Agentforce Nonprofit build for a UK charity, still in a sandbox, a lapsed supporters report returned no rows while a query found them: Salesforce had stored a date filter nobody wrote, last gift date in the current fiscal quarter. With the range written out, report and query matched.
Engagement Studio
How do you stop a lapsed donor journey asking someone who has just given?
Put a rule that checks for a new gift ahead of every email, feed the program from the lapsed list, and suppress the do not email list. Engagement Studio has four kinds of step: actions send an email or change a field, triggers wait for what a supporter does, rules check data as it stands, and end closes a branch.
- 01
Recipients and suppression
Recipient list “Lapsed, 13 to 24 months”; suppression list “Do not email”. As of 14 November 2026, every gift in this window predates 5 February 2026, so these supporters need email consent on record; the soft opt in covers only details collected from that date.
- 02
Rule: a gift in the last 30 days?
Yes: end. No: step 03. Nobody gets the story email after giving again.
- 03
Action: what the last gift did
One email about the work their last gift paid for, with no ask.
- 04
Trigger: a click within 7 days
Yes: notify the supporter care lead, who replies personally, then end. No: step 05.
- 05
Rule, 14 days later: a gift since step 02?
Yes: end. No: step 06. This is the check that keeps a supporter from being asked for a gift already made.
- 06
Action: one ask
A single ask with one suggested amount, their last gift.
- 07
Rule, 30 days later: did it work?
A gift: end, and the thank you process takes over. No gift: add to “Lapsed, no response”, next year’s reactivation mailing, and end.
Step types as defined in Trailhead’s Engagement Studio unit, read on 14 November 2026: actions “let you do something, like send prospects an email or change a field value”, triggers “listen for an event to occur within a specified period of time”, rules “check for specified criteria or values”. The waits, the windows and the single amount are my design for this journey, not a Salesforce default.
Campaign members will not match the email list unless you decide which one reports. “It seems apparent that the campaign members should align with the eMail list / recipients, correct? But, they don’t!” a Trailblazer Community member wrote on 15 March 2024. Treat the dynamic list as the audience and the Salesforce campaign as the report the board reads, and reconcile the two counts after the first send.
Scoring and grading
Why do donor scores in Account Engagement point fundraisers at the wrong people?
Because points are asked to show two things they cannot: a gift, which Salesforce records, and lapsing, which rising points never show. Let the score say who is reading and the grade who fits; gifts belong in a segment. Use the score to find engaged supporters who stopped giving, and keep the grade to a few written criteria.
- 01
Points that only go up mislead fundraisers
A supporter who opened every newsletter two years ago still looks warm unless inactivity subtracts: why Pardot lead scoring stops working explains the mechanics, which are the same for donors. Where the same Account Engagement also feeds a sales pipeline, that rebuild is on Pardot lead scoring and grading.
- 02
A paid licence sitting idle is the usual starting point, and a fixable one
A US company paid for Pardot and still sent its campaigns from Salesforce, so nobody knew who opened or clicked. Working in the team that implemented it, I moved the campaigns into Pardot and rebuilt qualification around behaviour, so sales was alerted when a prospect engaged; one of those leads closed as a large deal. That is the Pardot case study. For a charity the alert goes to supporter care, and the list is “Engaged, not giving”.
UK consent
Can a UK charity still email supporters under the new soft opt in?
Yes, for qualifying addresses. Since 5 February 2026 a charity can email supporters without a tick box if it collected their details itself while they showed interest in, or gave support for, its charitable purposes, and the email furthers them. Not for details collected earlier, from a platform or other third party, or bought. Every message needs an opt out.
- 01
What the Fundraising Regulator says
Its guide, published 24 June 2026, updated 7 July 2026 and read on 14 November 2026: the provision “entered into legal force on 5 February 2026” and “may only be used by organisations recognised as charities in law”, and “only by charities directly. This means their staff and on-behalf-of volunteers.” It “cannot be used” for anyone “whose personal data you collected before 5 February 2026”, and “the only purpose” of the email marketing must be “to further your charitable purposes.” Details must come from people “Expressing an interest in one or more of your charitable purposes” or “Offering to or providing support for your charitable purposes”. It “must not use personal data originally collected by” online fundraising platforms “or any other third party organisation”, and needs “a simple means of the person opting out” at collection and in every message. The ICO published its final guidance on 28 April 2026.
- 02
Three fields on every supporter, one list
Collection date. Collection route: your own form, event or phone, or an online fundraising platform, another third party, a bought list. Opt out offered at collection: yes or no. The list “Soft opt in eligible” is then collected on or after 5 February 2026, through your own route, with the opt out offered, and not opted out since. Without these fields every address looks the same, and none can safely use the rule.
- 03
A Fundraising Preference Service request goes to suppression
The same guide says the FPS “also allows individuals to opt-out of email, text, live phone calls and addressed mail fundraising marketing.” In Account Engagement the request has to reach the do not email list, not only a field in Salesforce.
- 04
Opt outs agree in both systems
Compare opted out prospects with contacts marked Email Opt Out in Salesforce; every difference is a supporter you might email against their wish, or one you lose for no reason. A Gift Aid declaration is not consent to email: Gift Aid in Salesforce Nonprofit Cloud.
This explains published guidance, not legal advice. Check your own case with the ICO or your data protection adviser before the first send under the soft opt in.
Training
Why can a fundraising team finish Account Engagement training and still not build a donor segment?
Because generic training teaches the menus; what stops a team is which field holds the last gift and why the list came back empty. Train in your own org, on your own fields, one segment per session, with the person who will own it doing the clicks. Four sessions, each ending with a one page recipe the team keeps.
“We’re new to using SF NPSP; have Account Engagement but not using it yet,” a Trailblazer Community member wrote on 14 November 2023. That is the usual starting point.
- 01
The field map
Which Salesforce field holds the last gift, the total and the recurring gift, and which prospect field reads each one.
- 02
A first dynamic list, built by the team
The lapsed segment from the table, built by the fundraiser who will use it, then checked against a direct query.
- 03
Suppression and consent
The do not email list, the three soft opt in fields, the Fundraising Preference Service. No program goes live without the suppression list.
- 04
An Engagement Studio test run
The lapsed journey, run on test supporters inside your org, one for each branch, before a real supporter enters it.
What this is not. Not a certificate course: Salesforce’s Trailhead modules on Account Engagement are free. Not the €650 Data quality check either: on an NPSP org that day lists installed packages, automation, custom code and integrations before a move, and builds no segments. And above roughly 300 seats, or where procurement requires a Salesforce partner on the invoice, a partner is the better answer. If your org needs a flow built before a session can work, such as copying gift totals onto the person account, that is separate work, scoped in writing first.
The next step
What do working sessions with your fundraising team cost?
No separate price: working sessions are paid from the support plan’s hours. Four sessions of about four hours, each ending with a one page recipe, fill about two months of the 8 hour plan at €520 a month. The third month of the three month minimum goes on your team’s questions and on keeping the recipes true to your org.
The sessions are named in writing before the first hour is used, and the person who will own Account Engagement leads the fourth, so the knowledge stays when the plan ends.
Account Engagement work: Pardot setup for a US nonprofit, delivered through a Canadian Salesforce partner. Nonprofit work: an Agentforce Nonprofit build for a UK charity, still in a sandbox, written up in the charity case study. 25+ Salesforce projects in all; scope and limits on who does the work.
Asked often enough to answer here
Questions
- Q
Does Account Engagement work with NPSP?
Yes. NPSP keeps supporters as standard contacts, and the connector syncs each prospect with one lead, contact or person account; no record is created without a matching email address. What Salesforce does not document is how NPSP household accounts behave on the Account Engagement side, so check three households by hand before any segment depends on household fields.
- Q
Does Account Engagement work with Agentforce Nonprofit?
The connector supports person accounts, which is how Agentforce Nonprofit holds individual donors, but I found no Salesforce page that documents the pairing specifically. Giving totals sit on Donor Gift Summary. Custom object sync reads objects the connector does not already sync, so it may reach them; I have not tested that. I have built flows that total gifts onto the person account; copying Donor Gift Summary fields is the same pattern, and I have not built that one.
- Q
Is there a nonprofit discount on Account Engagement?
Salesforce’s Account Engagement price page, read on 14 November 2026, names none. Ask your account executive in writing, and ask the same email whether your Account Engagement+ permission set licences are enabled and which of Agentforce, SMS and cross object merge fields you would use, because Salesforce says those need Data Cloud, and credits for Agentforce and SMS.
Serhii Skrypnyk · Senior Salesforce Administrator · 7 Salesforce certifications · on the platform since 2018. Updated 14 November 2026.
Read next
The question that usually comes after this one.
- 01
NPSP vs Nonprofit Cloud: Must You Move?
Salesforce still supports NPSP, and its own guide treats the move to Nonprofit Cloud as a reimplementation in a new org. When staying is fine and when moving pays.
- 02
Gift Aid in Salesforce Nonprofit Cloud
Nonprofit Cloud has no Gift Aid built in. What HMRC requires, how a claim reaches HMRC, app or build, and seven checks for your org.
- 03
Is Pardot Being Discontinued? Status in 2026
No announced end of sale and no forced migration. What changed is where the newest capability is built, and what that means for your timing.