Hi Pamela,
I've implemented this a couple of times (not for a few years, so not sure if this is all entirely up to date with where the product is)… but generally speaking, the online sponsorship relies on the following components:
Note: you will need to create the above in reverse order, as to create a Sponsorship Form part, you need a Payment 2.0 part & page, and to create a Sponsorship Search part, you need a Sponsorship Form part & page.
One thing to keep in mind is that the Sponsorship batches do not do any kind of configurable duplicate matching - they either auto-match, or it'll just create new constituent records. If you wish to avoid that, you can use the Payment 2.0 part to enforce user login, redirecting the user through a User Login part (requiring a new user registration or login to existing accounts) - in which case the sponsorship will be linked to the Sign Up transaction (Constituent Update Batch), or mapped to the logged-in record for you.
You will find guides in terms of how to design each of these in the Parts section of the BBIS Help documentation, you'll need the Sponsorship Search, Sponsorship Form, and Payment 2.0 parts.
Best of luck!
Cheers,Chris
How do I get to the Blackbaud Internet Community forums?
Christ, Thank You! this is extremely helpful. Question though, if I understand correctly, the sponsorship comes through the web mapping for the profile process using the Constituent Update Batch. When I look at that template none of the sponsorship information is there. I assume they will display in the batch after the sponsorship is created? Similar to the BIO info?
So there definitely a few batch types in CRM that are for the BBIS transactions that do not show you the full content of the downloaded transaction. Event Reg, Profile Update and Sponsorship are the main ones of these I can recall… You will however find a section under Sponsorship called “Sponsorship Purchases”, which will list out in a data list, all the unresolved online transactions. This should give you an insight into the ones that are waiting to be downloaded, and are yet to be linked the sponsorship commitment and constituent record, once those have been committed from the web batches.
Hi Christ, thanks for sharing this great information about setting up the sponsorship module. Here is a question. Is there a way not to enforce the user login on the Payment 2.0 part? Is payment 2.0 required for this to work?
Chris, the process to add the constituent directly to BBEC, bypassing the batch process, is not using our default Duplicate Checking with the ability to review. Do you know what business rules are used to determine a constituent may be a duplicate? Also, do you know how other CRM users are managing or validating the sponsorship is linking to the correct donor?
I really appreciate all of your input on this. You have been a tremendous help.