Currently, online donations via Stripe create a New Profile if the donor enters different data in any of these four fields: First Name, Last Name, Phone, Email. For orgs that receive numerous online gifts, the duplicates can quickly become a nightmare. We suggest the Stripe-CSuite data matching be modified to look for a match on 2 of 3 fields - say, last name, street address or email address, to reduce the number of duplicate profiles.
- add 'date created', and the ability to sort by date created in the duplicates form
-devise a bulk de-deduping process
Valerie Piper commented
I came to idea lab specifically to look for info on this thread...
We are having the same problem of duplicates and creation of individual vs. household profiles. I would love to see "household" added as an option for the donor to choose on the checkout page, instead of just indiv or org. Most of my time has been spent converting indiv profiles to households and merging into existing profiles. Hope we see a solution soon!
Jan Fischer commented
NEW INFO and additional recommendation:
CSuite's Stripe transaction recording process does not recognize Household profiles; it can only match individual profiles. As a result, if your donor data is organized into households, and you don't have individual profiles created for each household member, Stripe will automatically create a duplicate, even if name, email address and phone match. The more concerning issue is that a large number of these duplicates are not detected by Stripe's duplicate finder. The only way to identify and correct the duplicates is to investigate every Stripe-created profile that doesn't have a legacy code. In December, out of 457 Stripe-generated profiles, we found 229 duplicates created because we did not have individual profiles within our households, and most of the duplicates did not appear on the Stripe duplicates list.
Recommend Foundant adopt processes to ensure that, if a user’s data will be organized into households, individual profiles for each member (as well as for both household members, together) are created for each household.
Mary Cummings commented
Another thought: what about creating a "bucket" where online donations arrive from Stripe allowing the user to process them by either matching them to existing profiles in CSuite or creating a new profile. This step would be appreciated for associated tributes as well.
Having worked in various donor databases, I would amend this idea. Every donor database has this issue because of a lack of a unique ID. Make the parameters two strict and it is difficult for donors to complete the trx. We prefer it this way and live with the work coming in the form of regular deduping. I think a good in between would be the ability for each org to set their matching parameters, but that is without knowing how Stripe works.