A newsletter sign-up looks like the simplest form on your website: a name, an email address, a submit button. In Altru it gets more complicated, because Altru’s web forms are built mostly around transactions like buying tickets, joining, renewing, and giving. A visitor who only wants your monthly email doesn’t fit that mold neatly.
So the useful question isn’t how to build the form. It’s where the sign-up should live, and how the address ends up on a constituent record in Altru with the right opt-in. You have three realistic choices.
Before you choose: decide what “signed up” means in Altru
Settle this first, whichever route you take. Otherwise you’ll collect addresses that nobody can find later.
- Where the consent is stored. Pick one place on the constituent record that means “wants the newsletter.” That might be a communication preference, a constituent attribute, or a solicit code, depending on how your organization already handles opt-ins. Use it the same way everywhere.
- How you’ll find new sign-ups. Build a constituent query that returns everyone with that flag and a valid email. That query is what your email tool or export will run on, so it’s worth getting right before launch.
- What happens with existing people. Many sign-ups will come from members and past ticket buyers who are already in Altru. Plan for matching, or you’ll end up with a second record for the same person.
Option 1: An Altru web form, if your setup supports it
Check the list of web form types available in your Altru instance. Some organizations have a form that can capture contact details without a payment. Others only have transactional forms. This varies by configuration and by what Blackbaud has enabled over time, so don’t assume either way. Look in your web forms area, try it in a test environment if you have one, or ask Blackbaud support directly whether a no-payment contact or sign-up form is available to you.
If you can use one, the main benefit is that sign-ups land in Altru without an import step. The tradeoffs to look at:
- How much control you have over the fields and layout, and whether it looks like it belongs on your site.
- How new submissions are matched to existing constituents, and whether you have to review them before they become records.
- Whether you can set the opt-in flag you chose above automatically, or whether staff have to set it by hand.
One workaround some teams try is a zero-dollar donation form with “newsletter” in the title. It tends to cause more trouble than it saves: it creates revenue-type records with no money attached, it can confuse your gift reporting, and the form still looks like a giving page. Before you go that way, ask your finance and development staff how they would feel about those records showing up in their reports.
Option 2: Your email platform’s sign-up form
If you send newsletters from Mailchimp, ActiveCampaign, or something similar, its own embedded sign-up form is usually the easiest thing to put on your website. It handles double opt-in, unsubscribes, and spam protection, and it looks fine on a phone.
The catch is that the sign-up never reaches Altru on its own. Without a regular step to bring those contacts in, your email list and your constituent database drift apart. Then a member unsubscribes in one place and keeps getting mail from the other. If you go this route, set a schedule, such as monthly, for importing new subscribers into Altru. Match them against existing constituents during the import, and apply your opt-in flag. Also decide which system wins when someone unsubscribes, and write that down.
Option 3: A website form plus a periodic import
A form from your website platform (a WordPress form plugin, for example) gives you full control over design and fields. It also means one more place where data sits. Submissions usually come out as an email notification or a CSV export, and someone has to clean that file and import it into Altru. This works for low volume. At higher volume, the manual import becomes the job nobody wants, and sign-ups sit untouched for weeks.
Which one fits
- If Altru offers a usable no-payment form, start there, since data lands in Altru directly.
- If your newsletter already runs on a separate email platform and you have someone who can own a monthly import, use that platform’s form.
- Use a standalone website form only if neither of the above works, and assign a named person to the import.
Whichever you pick, run the same check every quarter. Compare your Altru opt-in query count with your email platform’s subscriber count. If the gap keeps growing, your sync step is slipping.
Don’t overlook sign-ups that come with a purchase
A standalone sign-up form is often not where most new email addresses come from. Ticket buyers, new members, and donors give you their email at checkout, and they already have a relationship with you. It’s worth making sure those transactions capture contact details cleanly and land on the right constituent record. Then your newsletter query picks them up along with everyone who used the sign-up form.
For that purchase path, Social Good’s Checkouts replaces Altru web forms for tickets, memberships, and donations with a branded, mobile-friendly checkout that writes the data back to Altru. It isn’t a standalone newsletter form, but it covers the transactions where many of your contacts first share their email.
Quick answers
Can I put a sign-up form on my site without asking for a mailing address?
Yes. For a newsletter, name and email are usually enough. More fields mean fewer sign-ups. Keep the form short and add more details to the record later.
How do I avoid duplicates from sign-ups?
Match on email address (and name, if you have it) during import or review, and periodically search for constituents who share an email. Clean up duplicates before they spread into your mailing lists.
