For the complete documentation index, see llms.txt. This page is also available as Markdown.

Aegis

Integrate Anedot with Aegis Premier Solutions to automatically relay donor and lead data using custom fields for accurate CRM syncing.

Integrate Anedot with Aegis Premier Solutions to automatically relay donor and lead data using custom fields for accurate CRM syncing.

Aegis Premier Solutions is a nonprofit CRM platform designed for donor management, fundraising tools, analytics, and reporting.

Anedot's integration with Aegis enables the automatic relay of supporter data from Donation and Lead Pages, simplifying backend workflows and keeping your CRM up to date with the latest fundraising activity.

Connect Anedot to Aegis

To connect your Anedot fundraising account to Aegis:

  1. Navigate to Settings → Integrations → Directory in your Anedot dashboard.

  2. Click + New Connection in the upper right corner.

  3. Select Aegis from the integrations list.

  4. Choose the Action Pages you want to sync with Aegis.

    • By default, all Action Pages are included.

    • To exclude specific pages, enter a comma-separated list of Action Page IDs.

    • You may also scope the integration by Team if desired.

  5. Enter your Aegis Premier Solutions URL.

  6. Enter your Aegis Username.

  7. Enter your Aegis Password.

  8. Provide your Context Key.

  9. Add your Fund Code.

  10. Click Create integration to complete the setup.

The Action Pages, Team, and credentials can be updated at any time after setup. For assistance locating Aegis credentials, contact Aegis Technical Support directly.

Data Relays

Anedot relays data to Aegis from both Donation Pages and Lead Pages.

For relays to be successful, these pages must include:

  • A field labeled appeal_id, set as a Custom Hidden Field.

  • Fields labeled custom_flag and custom_data_field to pass additional metadata.

These hidden fields ensure the correct data is delivered to Aegis partners.

Custom Flags

To enable flag-based data relays:

  • Add a Custom Hidden Field with the key custom_flag_1 using the Action Page Builder.

  • Additional flags must follow the same pattern: custom_flag_2, custom_flag_3, and so on.

  • Assign a Page-Specific Value to each field in Settings → Sharing → Page-Specific Values.

Field names must match exactly. Typos or mismatches prevent data from relaying correctly.

Custom Data Fields

To send custom product-related data:

  • Add a Custom Hidden Field with the key custom_data_field_1.

For Aegis users tracking product orders, add a product_sku field. This appears in Aegis under the productOrders area as productSKU.

Viewing Data in Aegis

Once relays are successfully processed, locate transactions in Aegis by navigating to Partners → Locate Transactions. Use this tool to search by contact or transaction ID.

Relay Fields

Anedot Field
Aegis Field

fundcode (from Setup); {amount} (×100); TRUE/FALSE

gifts {fundCode} {pledgeID} {giftAmount} {applyToPledge}

"internet"

channel

donation {amount} (×100); {lastDigits}; "Paid"; {payMethod} (Donations)

payment {amount} {number} {status} {paymentType}

[firstName] [lastName]; address {city} {region} {country} {line1} {line2} {postalCode}

shipping {shipto} {shiptoCity} {shiptoState} {shiptoCountry} {shiptoAddress1} {shiptoAddress2} {shiptoPostalCode}

Aegis Field

partnerID

*appeal_id

appealCode

value (from Product Details); "0.0"; fundcode (from Setup); "1"; InternalSKU (from Product Details)

productOrders {price} {discount} {fundCode} {quantity} {productSKU}

(Submission) id

referenceNumber

created_at

transactionDate

"Anedot UID: [Submission id] OnlineContribution (Source:[source_code])"

transactionNote

totalAmount (×100)

totalTransactionAmount

* Custom hidden field that must be added to the Anedot Action Page in order to be relayed.

** The discount is greater than 0 if the donation amount is below the value amount specified in the Product's Details.

Anedot stores the Amount in cents.

Payload Data

Request Headers

Request Body (Success, Create Partner)

Request Body (Success, Create Donation)

Response Body (Success)

Response Body (When productOrders Is Present)

Response Body (Error)

Response Body (Failure)

Response Status (Success)

Response Status (Failure)

Was this helpful?