> For the complete documentation index, see [llms.txt](https://docs.anedot.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.anedot.com/integrations/crm-donor-management/trail-blazer.md).

# Trail Blazer

Connect Anedot to Trail Blazer to send donations from your Action Pages as contributions, then manage the connection, review data relays, and map fields.

**Trail Blazer** is a compliance and reporting platform for political campaigns, political action committees (PACs) and nonprofits. The integration sends each donation from your Action Pages to your Trail Blazer workspace as a contribution. You set it up in **Settings > Integrations**, where you can connect Anedot to Trail Blazer, manage your connection, and review how data relays work, where to find your data, field mapping and payload data.

## Before You Begin

* You need **Integrations: Edit permissions** to add, edit, push or delete a connection. Integrations: Edit permissions also require **Action Pages: View permissions** and **Integrations: View permissions**. The built-in **Super Admin** and **Admin** permission sets include these permissions by default, and the **Standard** permission set doesn't. See [Permission Sets](https://docs.anedot.com/settings/access/permission-sets.md).
* You need your Trail Blazer IQ workspace name. If you don't have it, contact your database admin or Trail Blazer tech support.
* You need a Trail Blazer IQ login for that workspace so you can approve the connection.

## Connect Anedot to Trail Blazer

To connect Anedot to Trail Blazer:

1. Go to **Settings > Integrations**.
2. Click **New integration**.
3. Choose **Trail Blazer**, or enter "Trail Blazer" in the search box.

   <div data-gb-custom-block data-tag="hint" data-style="info" class="hint hint-info"><p>Trail Blazer appears in the Integrations directory under the <strong>Compliance</strong> category, with the card text "Authorize Trail Blazer and send Action Page data."</p></div>
4. Choose the Action Page scope:
   * Keep **All Action Pages** checked to include every Action Page, including pages you add later. (Optional) In **Exclude Pages**, enter a comma-separated list of Action Page IDs with no spaces.
   * Uncheck **All Action Pages** and choose **Selected pages** to pick specific pages.
5. Leave **Team** set to **All teams**.
6. Enter your Trail Blazer IQ workspace name in **Workspace**. The field shows ".oneadvocacy.com" after the box, so enter only the workspace name.
7. Click **Continue to provider**.
8. If Trail Blazer asks you to sign in, enter your Trail Blazer IQ credentials.
9. Click **Accept** to confirm the connection.

Anedot finishes the setup and returns you to **Settings > Integrations**, where the connection is listed.

{% hint style="info" %}
You can limit the connection to one Team afterward by editing it. See [Edit Your Connection](https://docs.anedot.com/integrations/crm-donor-management/trail-blazer.md#edit-your-connection).
{% endhint %}

{% hint style="warning" %}
If the setup is interrupted, Anedot shows "OAuth setup failed" or "OAuth setup is missing information." Start again from **New integration**.
{% endhint %}

## Manage Your Connection

### Edit Your Connection

To edit your connection:

1. Go to **Settings > Integrations**.
2. Click **Edit** on the Trail Blazer connection.
3. Change any of these settings:
   * The Action Page scope.
   * **Team**: limit the connection to one Team's Action Pages, or choose **All teams**. See [Teams](https://docs.anedot.com/settings/access/teams.md).
   * **Name**.
   * **Enabled**: uncheck it to stop sending donations to Trail Blazer.
4. Click **Save integration**.

The new settings apply to donations sent from then on. Editing doesn't resend donations already sent.

{% hint style="info" %}
The Edit form also shows a **Credentials/details JSON** box. Leave it as it is.
{% endhint %}

The workspace can't be changed in the Edit form. To connect a different workspace, delete the connection and connect again. See [Reconnect Or Delete Your Connection](https://docs.anedot.com/integrations/crm-donor-management/trail-blazer.md#reconnect-or-delete-your-connection).

### Push Unsent Records

**Push unsent** resends failed or never-sent donations from submissions and recurring donations for a date range.

* The range can be up to 31 days.
* The start date must be within the last 12 months.
* Wait about five minutes between pushes.
* Only failed or unsent donations are sent. Successful ones aren't sent again.

For the full steps, see [Push Unsent in Webhooks (API)](https://docs.anedot.com/integrations/integration-automation-tools/webhooks.md#push-unsent).

### Reconnect Or Delete Your Connection

To delete your connection:

1. Go to **Settings > Integrations**.
2. Click **Delete** on the Trail Blazer connection.
3. Confirm the prompt "Delete this integration?"

Anedot stops sending donations to Trail Blazer. Contributions already in Trail Blazer aren't changed.

To reconnect, follow the steps in [Connect Anedot to Trail Blazer](https://docs.anedot.com/integrations/crm-donor-management/trail-blazer.md#connect-anedot-to-trail-blazer). Donations already sent successfully to a connection with the same workspace aren't sent again after you reconnect.

## Data Relays

### What Anedot Sends

Trail Blazer receives donations only. Each donation is sent as its own record, so a submission with more than one donation sends one record per donation.

* **Donation Pages and Event Pages**: donations from pages in the connection's scope are sent once the donation is completed. A donation that completes later, such as a bank payment, is sent when it completes.
* **Lead Pages**: Lead Pages have no donations, so nothing is sent for Lead Page submissions.
* **Recurring donations**: each successful recurring donation payment is sent as its own donation. See [Commitments](https://docs.anedot.com/finance/management-and-reporting/commitments.md).
* **Not sent**: commitment changes (such as a cancellation), donation status changes after sending, and refunds.

Each record includes the donor's name and contact details, the donation amount, date, status, payment source, frequency, Fund, custom field answers, and the submission, Action Page and commitment IDs. See [Field Mapping](https://docs.anedot.com/integrations/crm-donor-management/trail-blazer.md#field-mapping).

### Records Anedot Skips

Anedot doesn't send these records, and they don't show a row in **Settings > Integrations > Integration Requests**:

* A donation that was already sent successfully to a Trail Blazer connection with the same workspace, including a connection you deleted and connected again.
* A donation that isn't completed yet. It's sent when it completes.
* Any donation while **Enabled** is unchecked.
* Lead Page submissions.

### Delivery And Retries

Each donation sent shows a row in **Settings > Integrations > Integration Requests** with its status (**Success**, **Failure** or **Error**), the request and the response. See [Integration Requests](https://docs.anedot.com/integrations/relay-data-troubleshooting/integration-requests.md).

* Only an HTTP 200 response from Trail Blazer counts as **Success**.
* If Trail Blazer's authorization has expired (HTTP 401), Anedot renews the authorization and tries again automatically.
* If Trail Blazer rejects a donation with another response, the row shows **Failure** and Anedot doesn't try it again. Fix the cause, then use [Push unsent](https://docs.anedot.com/integrations/crm-donor-management/trail-blazer.md#push-unsent-records).
* If Anedot can't reach Trail Blazer, it tries again automatically.
* Users with the **Integration sync failed** notification turned on get an email when a row shows **Failure**. See [Notifications](https://docs.anedot.com/get-started/security/notifications.md).
* Repeated authorization errors, where Trail Blazer's authorization can't be renewed, turn the connection off. If the connection stops sending, delete it and connect again.

What Trail Blazer does with a contribution after it accepts it is set by Trail Blazer.

## Find Your Data in Trail Blazer

Donations show up in your **Contribution list** in Trail Blazer. A **Source** attribute shows that these records come from Anedot.

To verify the connection, run a donation through an Anedot Action Page covered by the connection and check that it's processed in your Trail Blazer database.

{% hint style="success" %}
After you connect, make a test donation on a covered Action Page and check **Settings > Integrations > Integration Requests** for a **Success** row.
{% endhint %}

## Field Mapping

### Donation Fields

| Anedot Value                                                 | Trail Blazer Field        |
| ------------------------------------------------------------ | ------------------------- |
| Donation ID                                                  | uid                       |
| Postal code                                                  | zip                       |
| City                                                         | city                      |
| Donation date (UTC)                                          | date                      |
| Donor's full name                                            | name                      |
| Email                                                        | email                     |
| Donation items (a list, empty when there are none)           | items                     |
| Phone                                                        | phone                     |
| State                                                        | state                     |
| Title                                                        | title                     |
| Donation origin                                              | origin                    |
| Payment source                                               | source                    |
| Donation status                                              | status                    |
| Address line 1                                               | street                    |
| Suffix                                                       | suffix                    |
| Full address (zip, city, state, street, country, street\_2)  | address                   |
| Country                                                      | country                   |
| Donor comments                                               | comments                  |
| Employer                                                     | employer                  |
| Address line 2                                               | street\_2                 |
| Frequency, such as "Once" for a one-time donation            | frequency                 |
| Last name                                                    | last\_name                |
| Recurring donation (true or false)                           | recurring                 |
| Donor type                                                   | donor\_type               |
| First name                                                   | first\_name               |
| Occupation                                                   | occupation                |
| Source code                                                  | source\_code              |
| Check number                                                 | check\_number             |
| Donation amount, formatted as currency (completed donations) | event\_amount             |
| Custom field answers from the Action Page                    | custom\_fields            |
| Middle initial                                               | middle\_initial           |
| Date the donation was created (UTC)                          | processed\_date           |
| Originating donation ID                                      | originating\_uid          |
| Original donation amount in dollars                          | amount\_in\_dollars       |
| Organization name                                            | organization\_name        |
| Linked to a commitment (true or false)                       | is\_recurring\_commitment |
| Submission ID                                                | submission\_id            |
| Action Page ID                                               | action\_page\_id          |
| Commitment ID                                                | commitment\_id            |
| Fund (see Fund Fields)                                       | fund                      |

### Fund Fields

| Anedot Value             | Trail Blazer Field |
| ------------------------ | ------------------ |
| Fund ID                  | fund.id            |
| Fund internal identifier | fund.identifier    |
| Fund name                | fund.name          |

The fund is the Fund chosen on the Action Page for the donation. It's sent as an empty object when the donation has no Fund. See [Funds](https://docs.anedot.com/settings/finance/funds.md).

## Payload Data

These are the request and response bodies shown in **Settings > Integrations > Integration Requests**.

### Request Body

```json
{
  "uid": "d4d509e9ce2d5cd74c312",
  "zip": "70112",
  "city": "New Orleans",
  "date": "2026-01-11T15:05:23.362Z",
  "name": "Annie Dot",
  "email": "annie@anedot.com",
  "items": [],
  "phone": "2015550123",
  "state": "LA",
  "title": null,
  "origin": "hosted",
  "source": "credit_card",
  "status": "completed",
  "street": "1340 Poydras Street",
  "suffix": null,
  "address": {
    "zip": "70112",
    "city": "New Orleans",
    "state": "LA",
    "street": "1340 Poydras Street",
    "country": "US",
    "street_2": ""
  },
  "country": "US",
  "comments": null,
  "employer": null,
  "street_2": "",
  "frequency": "Once",
  "last_name": "Dot",
  "recurring": false,
  "donor_type": "individual",
  "first_name": "Annie",
  "occupation": null,
  "source_code": null,
  "check_number": null,
  "event_amount": "$12.81",
  "custom_fields": {
    "Question": "yes"
  },
  "middle_initial": null,
  "processed_date": "2026-01-11T15:05:23.284Z",
  "originating_uid": null,
  "amount_in_dollars": 12.0,
  "organization_name": null,
  "is_recurring_commitment": false,
  "submission_id": "bcdbe1ff-1430-47fb-a5fe-7bd0c7f5446d",
  "action_page_id": "e750b91e-5462-4b4b-a8fc-f232c24f2a3c",
  "commitment_id": null,
  "fund": {
    "id": "d4bd7311-3a2e-46ab-95e7-71843083b837",
    "identifier": "gf",
    "name": "General Fund"
  }
}
```

### Success Response (Status 200)

```json
"Create Contribution: Successful, ContributionID: 11470"
```

### Failure Response (Status 400)

A 400 response means Trail Blazer didn't accept the contribution.

```json
"Create Contribution: Failed"
```

## Troubleshooting

### No Row in Integration Requests

If a donation doesn't show a row in **Settings > Integrations > Integration Requests**, check that:

* The Action Page is in the connection's scope, and in the selected Team if you set one.
* **Enabled** is checked.
* The page has donations. Lead Pages send nothing.
* The donation is completed.
* The donation wasn't already sent to a connection with the same workspace.

See [Records Anedot Skips](https://docs.anedot.com/integrations/crm-donor-management/trail-blazer.md#records-anedot-skips).

### Rows Show Failure

Open the row in **Settings > Integrations > Integration Requests** and read Trail Blazer's response. Fix the cause, then use [Push unsent](https://docs.anedot.com/integrations/crm-donor-management/trail-blazer.md#push-unsent-records) to resend the donation.

### Connection Stopped Sending

Check that **Enabled** is checked on the connection. If the connection was turned off after authorization errors, delete it and connect again.

### Setup Didn't Finish

If Anedot shows "OAuth setup failed" or "OAuth setup is missing information," start again from **New integration** and check your workspace name. If you don't have your workspace name, contact your database admin or Trail Blazer tech support.

If the issue continues, contact our Support team at <help@anedot.com>.

## Related Articles

* [Integrations](https://docs.anedot.com/integrations.md)
* [Integration Requests](https://docs.anedot.com/integrations/relay-data-troubleshooting/integration-requests.md)
* [Teams](https://docs.anedot.com/settings/access/teams.md)
* [Funds](https://docs.anedot.com/settings/finance/funds.md)
* [Commitments](https://docs.anedot.com/finance/management-and-reporting/commitments.md)
* [Notifications](https://docs.anedot.com/get-started/security/notifications.md)


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.anedot.com/integrations/crm-donor-management/trail-blazer.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
