Duplication protection

Hi there, I'm Bob, one of the co-founders of Bridgit. In this short video I'll share how Bridgit handles gift transactions when integrating data between Raisely and Raiser's Edge NXT.

To begin with, I'm going to navigate to our test Raisely campaign, select donate, find an existing fundraising profile to give to, and make a single £30 donation. I'll fill in some dummy details and leave the rest of the form blank, then enter some test card details and a test UK postcode.

With that complete, I'll navigate to our Bridgit portal and select the bridge that runs from the Raisely general appeal to the NXT sandbox, which for live campaigns would typically be running on a schedule. I'll select Run Bridge, then pause the video here and return once it's complete.

So we're back, and the bridge run has completed. If I navigate to our NXT sandbox I can see the gift that's been created. We have details of the amount, the type, the donor and the donation date, and we have a strong identifier to make sure that if the bridge run is ever repeated we don't duplicate this gift in NXT.

We have various configurable options around campaign, fund and appeal, acknowledgements and receipts, and gift subtypes, and further down the gift code. We also have a link to the fundraiser here, set up as a soft credit.

That is how Bridgit handles gifts between Raisely and Raiser's Edge NXT. Be sure to check out the other videos showing how Bridgit supports fees, tickets, recurring gifts, custom fields and gift batches. Thanks for watching.