From visitor to supporter: website, newsletter and CRM

Few people donate on their first visit. They hear about you somewhere, read a bit, sign up, and give months later. This pattern maps that path so every channel asks for the next step only, and so you can tell afterwards where your supporters came from.
Who does this? Whoever leads communications, with the person who owns the CRM. An afternoon to map the path, then a monthly look.

The path

  1. Discovery. Someone meets you for the first time: a social post, a search, press, a partner's recommendation, a friend.
  2. Website. Within seconds they understand what you do and see one clear next step.
  3. Newsletter. For most visitors this is the conversion that matters: free, low effort, and it gives you permission to come back. Keep bots out of the signup form⁠ so the list stays real.
  4. Support. A donation, volunteering, an application, an event. Most of it comes from people who already read your newsletter.
  5. Relationship. A few supporters become people you know by name: major donors, funders, partners. They get a CRM record and a team member who owns the relationship.
Each step asks only for the next one. A donation request in a social post costs you engagement and buys little; ask for the newsletter signup instead.

Know where each supporter came from

Privacy-friendly website analytics⁠ shows which channels bring visitors and donations in total. To know where a specific donor or subscriber came from, the record itself has to hold the source:
  • Tag your links following Tracking links: UTMs, short links and QR codes⁠.
  • Let the form store the source. Hidden fields read the UTM tags and the referring site from the page address and save them with the donation or signup. Donorbox, for example, records the tags with each donation, and a custom Stripe form can do the same; ask whoever builds your form. The source then travels with the form the donor submits, so no tracking cookie is involved. If people land on one page and donate on another, carry the tags along in your links to the donate page or put the form on the landing page. Keeping them in a cookie or browser storage instead counts as tracking under EU rules and needs consent.
  • Ask. An optional "How did you hear about us?" question, with your main partners among the answers, catches the people who read about you somewhere and then searched for your name. Put it after the payment if you don't want to slow the donation down.
  • For large gifts, ask in person and note the answer on the CRM record.

When someone gets a CRM record

Your newsletter tool holds everyone; your CRM holds relationships. Someone moves into the CRM when a person on your team will talk to them directly: a gift above a threshold you set, a funder, a partner organisation, a journalist. Everyone else stays in the newsletter tool with labels, and you don't copy the newsletter list into the CRM. Your CRM in Asana⁠ shows our setup. The Community page⁠ in the Moral Fabric app brings donors, subscribers and event attendees from your tools together in one view, and can email you when a donation above your threshold comes in, so a large gift gets a personal thank-you the same week.

Look once a month

Fifteen minutes: visitors per source, newsletter signups per source, donations per source, and new CRM records. Community's insights in the Moral Fabric app show where donors and subscribers come from and how your community grows and churns, so most of this sits on one screen; visitors per source come from your analytics. Then ask one question: which channel brought supporters, and does it get the time it deserves?

Your variation

Record your steps, your main conversion, your threshold for a CRM record and who does the monthly look.

See also

16 Nov 2026 by Ruben