Trail Blazer
Connect Anedot to Trail Blazer to sync donation and custom field data for political campaigns and nonprofits. Includes setup steps and relay behavior details.
Connect Anedot to Trail Blazer to sync donation and custom field data for political campaigns and nonprofits. Includes setup steps and relay behavior details.
Trail Blazer is a compliance and reporting platform widely used by political campaigns, PACs, and nonprofits for managing donor data and generating reports. Click here to learn more about Trail Blazer!
Anedot’s integration allows you to automatically relay donation data and custom field information from your fundraising efforts directly into Trail Blazer.
Note: Only financial Action Pages are supported. Lead Pages (non-financial) are not included in relays.
Connecting Anedot to Trail Blazer
To integrate your Anedot fundraising account with Trail Blazer:
Navigate to Settings → Integrations → Directory in your Anedot account.
Click the blue + New Connection button in the upper right corner.
Select Trail Blazer from the integration directory.
Choose the Action Pages you’d like to sync.
The default is All Pages.
To exclude specific pages, enter their Action Page IDs as a comma-separated list.
(Optional) Scope the integration to only include Team-specific data.
Enter your Trail Blazer Workspace Name.
Click the blue Save button to proceed.
You’ll be redirected to Trail Blazer to log in and confirm access.
Data Relays
Financial Action Pages
All donation details and custom field data are relayed.
You can use Push Unsent to resend failed or unsent relays by specifying a date range.
Non-Financial Pages
Relays are not supported for Lead Pages or other non-financial form types.
Where To Find Your Data in Trail Blazer
After a successful relay, donor data will appear in your Contacts section within Trail Blazer IQ.
Field Mapping
The Anedot Fields match the Submission Raw Data (unless specified otherwise in parenthesis); the Trail Blazer Fields match the Request Body relay.
donations {id}
uid
address {postal_code}
zip
address {city}
city
date (utc)
date
- amountAllocations {actionPagesFund {id}} Fund Name (from fund) Internal Identifier (from fund)
fund {multiple fields}: {id} {name} {identifier}
paymentMethod {name}
name
phone
phone
address {region}
state
title
title
donations {origin}
origin
donations {source}
source
donations {status}
status
address {line_1}
street
suffix
suffix
address {postal_code} {city} {region} {line_1} {country} {line_2}
address {zip} {city} {state} {street} {country} {street_2}
address {country}
country
donations {comments}
comments
employerName
employer
address {line_2}
street_2
frequency
frequency
lastName
last_name
"true/false"
recurring
donations {donorType}
donor_type
firstName
first_name
occupation
occupation
sourceCode
source_code
donations {checkNumber}
check_number
(Donation) totalAmount
event_amount (in dollars)
actionPagesCommitment {id}
commitment_id
customFieldResponses {multiple fields}
custom_fields {multiple fields}
submission_id
submission_id
actionPage {id}
action_page_id
middleInitial
middle_initial
created_at (utc)
processed_date
originating_uid
originating_uid
amountAllocations {amount} (x100)
amount_in_dollars
organization
organization_name
"true/false"
is_recurring_commitment
Payload Data
Request Headers
Request Body
Response Body (Success)
Response Body (Failure)
Response Body (Error)
Response Status (Success)
Response Status (Failure)
Response Status (Error)
Was this helpful?

