The usual reason for wanting registration on Altru web forms is the cleanup. Someone buys tickets online as a guest, then buys a membership a month later, then donates at year end, and you end up with three constituent records for one person. Making everyone log in or create an account first looks like the obvious fix.
Before you change anything, it helps to be clear on what Altru can actually enforce, what forced registration costs you at checkout, and whether you can get the clean data another way.
Can Altru force a login before checkout?
Honestly, it depends on the form type and your configuration, and it’s not something we’d promise from memory. Altru’s online sales and web forms support a guest-style flow where the buyer enters their name, email, and address, and Altru tries to match that to an existing constituent. Some forms also give patrons a way to sign in. Whether a given form can be set so that signing in or registering is mandatory, with no guest path at all, is something to confirm directly:
- Open the form’s settings in a test environment and look for any option controlling guest checkout or required sign-in.
- Run a test purchase in an incognito browser window to see what a brand-new visitor is actually allowed to do.
- If you can’t find a setting, ask Blackbaud support whether mandatory registration is supported for that specific form type (ticketing, membership, and donation forms don’t always behave the same way).
If the answer is no, the workarounds below get you most of the benefit anyway. If the answer is yes, read the next section before you switch it on.
What forced registration costs you
Every extra step between “I want to visit Saturday” and “paid” loses some buyers. Account creation is one of the steepest of those steps, because it asks the visitor to invent and remember a password for a place they may visit once a year. Common problems we see:
- Forgotten passwords. Returning visitors who registered last year often can’t get in, so they create a second account with a different email. That’s the duplicate you were trying to prevent.
- Gift buyers and parents. The person paying is often not the person visiting. Forcing them into an account doesn’t tell you much about who actually walks in.
- Mobile abandonment. Many ticket purchases happen on a phone in the parking lot or the night before. A registration screen on a small screen is where those sales stop.
- More front desk calls. “I can’t log in” becomes a visitor services problem, usually at the worst possible time.
For members, a sign-in step makes more sense, because they have a real reason to come back: renewals, member pricing, and their own status. For a one-time ticket buyer, it rarely pays off.
Getting cleaner records without a forced login
The goal behind registration is usually one constituent per person with an accurate email. You can get close to that without making anyone set a password.
1. Make email required on every form
Email is the most reliable match key you have. Require it on every ticket, membership, and donation form, and add a confirm-email field if the form allows. A typo in the email is one of the most common reasons a returning buyer doesn’t match.
2. Review your matching and duplicate rules
Altru decides whether an online buyer matches an existing constituent based on the fields it compares. Check how your organization has this configured and test it: buy a ticket in a sandbox using a known constituent’s exact name and email, then again with a nickname or a different address, and see what Altru does in each case. That tells you where duplicates are coming from.
3. Give members their own entry point
Instead of making everyone register, give members a clear “member sign-in” path for renewals and member pricing, and leave the general ticket flow open to guests. Members get the convenience, and casual visitors aren’t blocked.
4. Clean up on a schedule
Even with good forms, some duplicates will get through. Build a query for constituents created by online transactions in the last month that share an email, or a last name and postal code, with an older record. Review and merge on a regular cycle so the backlog never gets large enough to dread.
5. Ask only for what you’ll use
Long forms push people toward fake or partial information. If you’re collecting fields nobody reports on, removing them often improves the accuracy of the fields that matter.
Deciding which way to go
Forced registration is worth considering if most of your online revenue comes from members or repeat buyers who already expect to sign in, and your duplicate problem is serious enough that staff spend real time merging records. It’s usually the wrong choice if general admission or event tickets drive most online sales, or if many buyers are tourists and first-time visitors.
A middle path that works for many organizations: optional sign-in that’s easy to find, required email everywhere, and a monthly duplicate review. Measure duplicates for a quarter before and after, and decide from your own numbers.
Where Social Good fits
If the standard Altru forms are the limiting factor, Checkouts replaces them with a branded, mobile-friendly checkout for tickets, memberships, and donations, with Apple Pay and Google Pay, and writes the transaction data back to Altru. A shorter checkout that still collects a consistent name and email can be an alternative to forcing registration on every buyer.
Quick answers
Will requiring registration eliminate duplicates?
No. People who forget their login often register again with a different email, so you trade one kind of duplicate for another. Required email plus regular review usually does more.
Should members and ticket buyers get the same flow?
Not necessarily. Members benefit from signing in; one-time ticket buyers mostly don’t. Separate entry points let you treat them differently.
