Supporter Trails
Every donor, every event, every page — one timeline
Donations from Stripe, event registrations and peer-to-peer pages from your fundraising platform, identified site visits from the tracking snippet — threaded into a single per-supporter view.
Sarah C.
s***@gmail.com
Story · AI written
Sarah's monthly $50 gift has been running smoothly for 11 months. She registered for City2Surf 10km last week and set up a fundraising page that's raised $1,240. Card on file expires next month — worth a personal note.
Donated A$50 — monthly recurring · card on file
Registered City2Surf 10km · solo entry
P2P page "Run for Mum" · A$1,240 raised · 18 donors
Visited /campaigns/end-of-year-appeal · Facebook
One supporter, one timeline
Most charity tech keeps donations, event registrations, and P2P pages in three different systems. Trails stitches them back together by person. Each supporter row shows lifetime giving, recurring status, registration history, P2P fundraising activity, and a Pulse churn-risk score — in chronological order, one screen.
AI-written supporter stories
At the top of every Trail is a 15-second read on who this person is: "Sarah donated A$50 in March, registered for the 10km run, set up a P2P page that raised A$1,240, and visited the campaign page twice this week." Written by Claude from the events on file, refreshed when something material changes.
Identity resolution that survives typos
Email is the primary join key, but supporters change emails and platforms use different field names for the same person. Trails matches by Stripe customer id, platform supporter id, and (as a last resort) Stripe card fingerprint — so a typo on a registration form doesn't fracture one human into two records.
PII handled the right way
Donor email and name from the smart webhook receiver are SHA-256 hashed with a per-organisation pepper before storage. Stripe-side identifiers stay plaintext so flagged transactions can be reviewed; switch to Masked mode and the dashboard hides plaintext from the UI and from AI-generated summaries. Compliance teams get the audit they need without losing the case-work view.
How customers use it
Three scenarios where this lands
Scenario
Before picking up the phone for a major-donor call
Open the supporter's Trail. See the AI story at the top, lifetime giving, recurring status, last event registration, last site visit. You walk into the call knowing who they are without spending twenty minutes in three systems.
Scenario
Investigating a refund request
Pull the Trail. See the donation that triggered the refund, the IP that submitted it, the registration the donor had against an unrelated event, and whether they have an active recurring gift. Decide in seconds whether this is a real customer or a chargeback in progress.
Scenario
Re-engaging a lapsed donor
Filter Trails by "last gift > 90 days ago". The Trail shows their engagement history — which events they've attended, which campaigns they responded to. Tailor the re-engagement message to what they actually cared about, not a generic blast.
Try Supporter Trails on a 14-day free trial.
Included on the Partner plan and above. Full access during your trial.