Customize contact fields to include on donation form
Would it be possible to make the donation function page's contact fields editable, much like the current page that allows people to sign up for the email newsletter?
Right now, it defaults to all required contact information, which makes sense for anyone applying to our organization for membership or registering for an event, but does not make sense for people who only want to donate to us.
We have started development of the feature. It will be published in 5.11 release on 15th May.
I’m glad to announce ability to control which common and donation fields appear on each Donation form. The workflow will be similar as setting up Subscription form gadget.
We’ll keep you updated on progress
Nadya, Product designer @ Payments team
Make the Donations funcion like Events - common field check off list rather than all common fields. So that the public will not be over requested for information and leave the site.
Thanks for comments, Karl
The donation form isn't customizable yet, so it might include some extra fields. While this issue is still in stack, I can only suggest you to rethink strategy about what to keep in common fields and what - in member-only fields.
Besides, you can mark some common fields as admin-only. In this case nobody except admins can access them (if your contacts do see them - please contact our support for assistance).
More details on field management here: https://help.wildapricot.com/display/DOC/Customizing+database+fields
Oleg, Product Designer @ Payments team
Karl Hakkarainen commented
Adding a me, too comment.
We have an annual fund drive underway. We'd like to be able to accept donations from non-members, such as family members and memorial contributions. The intrusiveness of the donation form for non-members is such that we cannot deploy it.
The form includes contact fields that are intended for administrators only, further adding to the confusion.
For Common Fields, I created all the fields I wanted for membership because we hope all our non-member Contacts will become members or be added to member Bundles. But now those same fields automatically become the Donation Fields, even though we would rather only have a few fields for that - perhaps just name and email address so that a donation by a member is recorded in the member profile. For members who would like to make a donation, having to fill out all the other fields again (that are already in their member profile) is a pain and a deterrent. For nonmembers who would like to make a donation, it is also a deterrent and I realize now that some of the required fields (that we want for members) may not even apply to nonmember donors.
For these reasons, I would like to be able to deselect some of the Common Fields when setting the Donation Fields. Or, when creating the Common Fields, I would like to be able to choose - for each field - whether it should be used for a Donation Field. Another alternative would be to not have the Common Fields automatically apply to Donations in the first place (except perhaps Name and Email Address), leaving it to the client to create whatever other fields are wanted for that particular gadget.
We just launched our first donation drive and not having the ability to control which common fields appear to non-members or members who aren't signed in is a problem. We appreciate having that type of fine control over subscription forms and other WA modules. It would be helpful to have this type of control in the donations module as well.
Nancy Scanlan commented
The AHVMA (association) and AHVMF (foundation) originally worked together for years. But recently the foundation has separated so that it can fundraise more effectively. While Wild Apricot is great for a membership-based organization that concentrates on events such as conferences, it has not worked well for our foundation which concentrates on fundraising. The lack of flexibility in donor forms is one example. We have a number of items in donor forms that need much more flexibility than is available through Wild Apricot. The inability to have recurring payments is another. Recurring payments are a big source of income for many small foundations.
Therefore, although the association uses Wild Apricot for many of its functions, the foundation does not.If WA would incorporate items that allow for flexibility in fundraising, including highly customizable forms and recurring donations, the foundation would sign up in a heartbeat.
Current websites that have donation applications are too rudimentary, yet they still allow for these 2 items people are requesting which have been promised since 2010 (next year, next year, next year....) I think you are missing out on a large group by not improiving on your donor forms.
We would really like this as well.
I can't believe this hasn't been done yet. It is a big issue for us. One of the reasons we chose Wild Apricot was to have the combined ease of managing members and donations. We have lots of member-specific data that we don't want people to have to fill in when they donate. I can't seem to figure out how to make fields member-specific--although I am marking them that way, they still show up in the public view.
Please make this a priority.
I would very much like to see this as well. I just completed a Marketing for Nonprofits course and they stressed the importance of having a big, clear "Donate Now" button on your web site and making that process as simple as possible for donors. While it's nice to capture some of the same information we ask of our members, unfortunately this makes the donation process cumbersome for those who simply want to donate and not give a ton of information.
Also, please make it possible to have Admin Only fields for donations.
We would also really appreciate this functionality for donations. The email subscription form works really well and if the donation form had similar functionality we'd be thrilled.
Nancy Scanlan commented
This would be very useful for us also.
Thanks much for the consideration, and quick reply.
Dmitry Buterin commented
Thanks for posting. I renamed the thread - hope I understood you correctly.
This makes total sense and in fact we have been thinking for some time about redesigning current approach with fields to make it more flexible/easier to understand.