FUNDRAISING INTEGRATION

Every Anedot donation and form fill.
A live list you can text.

Create an Anedot list, point a webhook at it, and paste Anedot’s secret token. Donations and form submissions land as contacts in real time, every delivery verified by signature. SMS opt-in enforced by default.

THE GAP

A gift happens at 7:42 PM. When does your list find out?

A copy of your donor file starts aging the moment it lands. The only list that stays true is the one the webhook writes.

THE WEEKLY EXPORT

Days behind

Pull the CSV, clean it, import it, repeat. The supporter who gave on Tuesday hears from you next week, if the file made it through at all.

THE NIGHTLY SYNC

Hours behind

Batch jobs narrow the gap but never close it. Refunds sit on the list until the next run, and the moment of the gift is long gone.

THE SIGNED WEBHOOK

Seconds behind

Anedot fires the event, the signature checks out, and the contact is on the list. You can text them while the gift is still on their mind.

THE SETUP

Three steps. No field mapping.

Anedot’s payload keys are fixed, so there is nothing to configure field by field. Create, point, paste.

  1. Create the list.

    Contact Management, New Anedot List. Political Comms generates a dedicated endpoint URL for the list. That URL is the whole integration surface.

    https://…/webhooks/anedot/…

  2. Point Anedot at it.

    In Anedot, under Integrations, Webhooks, add a webhook to that URL. Subscribe to donation and submission events and keep the default payload template. Nothing to map.

    donation · submission

  3. Paste the secret token.

    Copy the webhook’s secret token from Anedot into the list settings. From then on, every delivery is verified against it before anything touches the list.

    X-Request-Signature: HMAC-SHA256 ✓

Until the token is pasted, deliveries are rejected and the failures show in Anedot’s own delivery log. Nothing fails silently.

LIST CONTROLS

Set the rules once. Every event obeys them.

Each Anedot list carries its own settings panel. The webhook does the rest.

ANEDOT LIST SETTINGS

List nameFall Donors
BrandCivic Action Fund
Signing secret•••• 8f2cConnected
Require SMS opt-inDefault on
Remove on refund

Retention

The list details page shows live delivery stats: events received, contacts added, contacts removed, and the last event time.

  • Opt-in enforced by default

    Only people who consented to phone contact on the Anedot form are added. The gate ships on. Turning it off is a choice you make, not a default you inherit.

  • The whole refund family, one rule

    Refunded, charged back, ACH returned, or voided: with Remove on refund turned on, the contact leaves the list. A reversal or a new gift brings them back. Partial refunds keep the contact, because a partial refund is still a donor.

  • Retention on your terms

    Keep contacts forever, or run a rolling 30, 60, 90, or custom-day window since their last donation or form fill. New activity restarts the clock. A nightly sweep enforces it.

  • Rejected until verified

    Every delivery must carry a valid HMAC-SHA256 signature. A missing or wrong secret is rejected at the edge and the failure shows in Anedot’s delivery log, where your team can actually see it.

THE PIPELINE

From signed event to clean list.

Verification, consent, hygiene, and attribution run on every event. What comes out the other side is a list you can text without a second look.

01 / SIGNED INGESTION

Verified before it counts.

Every delivery arrives with an HMAC-SHA256 signature and is checked against your secret before processing. Contacts are upserted by phone number. A delivery that fails verification never touches the list.

02 / CONSENT

The gate ships on.

Only supporters who consented to phone contact on the Anedot form enter the list. Completed donations mark donors. Form fills and pledges add leads. Neither slips past the gate.

03 / HYGIENE

The list cleans itself.

Refunds, chargebacks, ACH returns, and voids remove contacts by rule. Reversals bring them back. Rolling retention drops anyone whose last activity has aged out, enforced by a nightly sweep.

04 / ATTRIBUTION

Every gift carries its story.

Amount, frequency, source code, the full UTM set, and the action page land as custom fields and work as merge tags. Ask for the next gift with the last one in hand.

No field mapping, ever. Anedot’s payload keys are fixed, so amounts, source codes, UTM parameters, and addresses land in the right place on their own.

QUESTIONS BUYERS ASK

Answered before you have to.

This is the defining platform. See how it's measured.

Every message delivered. At a known cost. On demand. At any scale.