Home → Campaign Manager → Frequently Asked Questions! → ActBlue Automatic Payout Imports (Contributions + Refunds + Fees)
1.12. ActBlue Automatic Payout Imports (Contributions + Refunds + Fees)
Overview
The ActBlue Integration in Campaign Manager enables automatic import of contribution data from ActBlue fundraising pages into your Aristotle dataset. Once configured, contributions, refunds, and processing fees are synced directly from ActBlue’s payout batches to ensure compliance-ready accuracy and reporting consistency.
⚠️ Note: Only traditional ActBlue accounts support this API integration. Raise by ActBlue does not currently provide API access.
Access Requirements
Before beginning setup:
-
You must have Administrator access to your campaign’s ActBlue account.
-
You must have Full Settings Edit permission in Campaign Manager.
-
Your ActBlue instance must include the API Credentials section under settings navigation.
Setup in ActBlue
-
Log in to ActBlue at secure.actblue.com.
-
Go to Settings → API Credentials.
-
Click Create New Credential and name it (e.g., “Aristotle Integration”).
-
Copy the following values (We'll need them later):
-
Client UUID – functions as the Username
-
Client Secret – functions as the Password
These credentials grant secure, backend data access only. They do not allow login to ActBlue.
-
Setup in Aristotle Campaign Manager
-
Navigate to Settings → API Settings.
-
Under Available Integrations, locate ActBlue and select Add Setting.
-
If your organization uses more than one ActBlue account, multiple ActBlue integrations are supported within Campaign Manager.
-
-
In the ActBlue Additional Settings window, complete the following sections:
General
-
-
Nickname: Assign an internal name for this integration (e.g., “Campaign ActBlue”, "JFC ActBlue").
-
Start Importing From (Date): This if the first payout date you'd like to start importing from. AKA: You already have payouts through last week imported, so you want to import only this week's Sunday payout.
-
Backfill (Optional): Define a specific date range if you wish to backload historic ActBlue data.
-
ActBlue Connection
Paste in your backend credentials from ActBlue:
-
-
UUID (Client UUID) – copied from ActBlue’s API Credentials page
-
Client Secret – copied from ActBlue’s API Credentials page
-
Import Coding & Routing
Configure how imported transactions should be categorized in Aristotle:
-
-
Choose whether ActBlue is acting as:
-
Conduit Committee – creates earmarked memos for reporting; or
-
Merchant Account – normal receipts without earmarks.
-
-
Specify how refunds should post:
-
As Expenses (Refund as Disbursement – Code 0101), or
-
As Negative Receipts (refunds as negative contributions).
-
-
Select the Election Period, Deposit Account, Batch Format, and Category/GL options appropriate for your organization’s accounting setup.
-
Matching & Deduplication
Campaign Manager automatically matches imported ActBlue records on: Name + Email + Zip + Phone + ActBlue Donor ID.
Optional: by default we suggest enabling Nickname/Alias Matching to improve recognition of recurring donors.
Notification Recipients
Enter email addresses to receive alerts when new ActBlue batches are imported.
Import Timing & Data Behavior
-
Import trigger: Campaign Manager only imports ActBlue data after a bank payout is triggered.
-
Contributions that have not yet been sent to the bank will not appear until the next ActBlue transfer.
-
This ensures that each import aligns with the payout batch and includes the corresponding Contributions, Refunds, and Credit Card Processing Fees.
-
-
Refresh frequency: Data is imported automatically following each new payout.
-
Record tagging: Imported records are labeled with Created By User = ActBlue Import for audit tracking.
Support
If you experience issues with the ActBlue Integration setup, please contact:
Aristotle Support
📧 support@aristotle.com
📞 1-800-243-4401