Contacts and Campaign Members, in real time.
Salesforce for PACs, c4s, party committees, and agencies. Every consented visitor arrives as one record, with its receipt.
The scan shows whether your site already runs Salesforce Nonprofit Cloud.
How it works
Inside Salesforce Nonprofit Cloud, where you already work.
As a Contact with an NPSP Household Account, added as a Campaign Member on the Salesforce Campaign you choose, with Lead Source and custom fields set. Optionally created as a Lead if your organization qualifies first.
Native Salesforce REST API in real time. Bulk API for backfills. Zapier and Make also supported.
- 1A visitor says yes on your site.
- 2ReachTheVote.com verifies the record and writes the receipt.
- 3The record lands in a Contact with a Household Account, added as a Campaign Member on your Salesforce Campaign.
What we send, and how.
Consent receipts travel as a tag, source code, or field. No destination has a receipt object of its own, and every field is one the visitor agreed to.
- What it is
- Salesforce for PACs, c4s, party committees, and agencies.
- Website
- salesforce.com/nonprofit
- How it connects
- API · A Contact with a Household Account, added as a Campaign Member on your Salesforce Campaign
- What we send
- Enriched Voter Contact, with its consent receipt
Late bulletin
Every day you wait, visitors leave as strangers. Scan your site today.
Ten seconds. Your Supporter Reach Score, what fires before anyone says yes, and what your privacy policy leaves out. Nothing installed, nobody contacted.
- A real browser load of your homepage, screenshot included
- Every tag that fires before a visitor can answer
- Your privacy policy, lined up against what the site does
- Modeled traffic and what an ask-first step would return