Queued in Campaign Manager, ready to import.
Compliance, fundraising, and CRM used by consultants on both sides. Every consented visitor arrives as one record, with its receipt.
The scan shows whether your site already runs Aristotle Campaign Manager.
How it works
Inside Aristotle Campaign Manager, where you already work.
As contact records in Campaign Manager with a source code applied, ready for fundraising lists and reporting. Inbound records arrive through the Import Queue, where staff import, skip, or delete each one.
Webhook or API token intake issued by Aristotle support, or CSV import.
Aristotle's intake is designed for contributions; non-financial contact intake is by import.
- 1A visitor says yes on your site.
- 2ReachTheVote.com verifies the record and writes the receipt.
- 3The record lands in the Import Queue in Campaign Manager, under Fundraising, ready to import.
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
- Compliance, fundraising, and CRM used by consultants on both sides.
- Website
- aristotle.com
- How it connects
- Webhook or File · The Import Queue in Campaign Manager, under Fundraising, ready to import
- 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