Map Raisely fields to NXT custom fields, including payment info (e.g. Stripe Charge ID), profile fields and UTMs.
1:32 · narrated walkthrough
Hi there, I'm Bob, one of the co-founders of Bridgit. In this short video I'll share how Bridgit supports the use of UTMs when integrating data between Raisely and Raiser's Edge NXT.
To begin with, I'm going to navigate to our test Raisely campaign and manually add a UTM string to our URL. For the purposes of this demo I'm going to assume that we are most interested in tracking the UTM source that this supporter has come from. Once that page is refreshed I'll sign up as a fundraiser, and I'll skip the unnecessary information.
Now that that's complete, I'll navigate to our Bridgit portal, select the bridge for the Raisely general appeal to the NXT sandbox, and click Run Bridge. With that triggered I'll pause the video. We'll resume in about a minute when it's complete.
So we're back, and our bridge run has completed. If I navigate to our NXT sandbox I can see that a constituent record has been created as part of the bridge run. Scrolling down to the custom field section, we can see that the bridge run has also successfully added the source UTM tag, showing as Facebook, alongside its date.
That is how supporter journeys can be more effectively tracked using Bridgit when transferring data from Raisely to Raiser's Edge NXT. Thank you for watching.
Gifts, recurring gifts, constituent records, consent preferences and custom fields, moving from Raisely into Raiser’s Edge NXT on a schedule you set.
Explore the integration