Use Cases
Some concrete examples of Bridgit automations across fundraising, marketing, CRM and finance workflows. These example use cases really only scratch the surface, Bridgit is powerful and versatile and can support many, many more.
Automating event fundraising data into supporter nurture campaigns
Charities running mass participation events need supporter data to move quickly from fundraising platforms into their email and journey tools. This use case shows how Bridgit automates that flow so supporters are added to the right nurture campaigns without manual exports, uploads or delays. Real Life Example: How The Myton Hospices automated event sign-ups into Dotdigital to power timely supporter journeys Before Bridgit At The Myton Hospices, the digital marketing team used Funraisin to manage event fundraising and Dotdigital to run supporter journeys and nurture campaigns. To make this work, event sign-up data needed to be moved from Funraisin into Dotdigital quickly and accurately so supporters could receive timely, event-specific communications. Doing this manually meant regularly exporting data, cleaning it, uploading it into the correct Dotdigital lists and context-switching between platforms while events were live and sign-ups ongoing. This created friction for the team and introduced the risk of delays or human error at critical moments in the supporter journey. Life with Bridgit Using Bridgit, Myton set up automated bridges that flow data directly from Funraisin fundraising campaigns into the appropriate Dotdigital lists. For their Moonlight Walk event, this meant supporter sign-ups were automatically routed into an event-specific list in Dotdigital, triggering the correct nurture and engagement campaigns without manual intervention. With full control over data transformations, the team can format names, standardise date types and combine fields where needed so data arrives in Dotdigital clean, consistent and ready to use. As new events are launched, additional bridges can be configured so supporter data is automatically routed to the correct Dotdigital lists each time. Impact Faster, more reliable delivery of event sign-up data into Dotdigital Reduced manual data handling during live campaigns Lower risk of errors and missed communications Less context switching for the digital and fundraising teams A scalable setup that supports multiple events using unlimited bridges on the Bridgit Connect plan It’s like having a small team of API developers at your fingertips without the very costly agency fees or contractor fees. Bridgit is saving our supporter care team hours already. - Dan Brown, Digital Marketing Manager, The Myton Hospices
Automating MuchLoved income processing for Donorflex CRM
Charities using MuchLoved often spend days each month cleaning, coding and reformatting donation data before it can be imported into Donorflex (or whichever CRM they are using). This use case shows how Bridgit reduces that workload by automating the bulk of income processing and delivering a Donorflex-ready import file. Real Life Example: How Rowans Hospice reduced MuchLoved income processing time by over 75% (with further reductions expected) Before Bridgit At Rowans Hospice, processing income from MuchLoved was one of the most time-consuming admin tasks in the fundraising calendar. Twice a month, following MuchLoved payouts around the 1st and 15th, the Legacy and In-Memory Giving Fundraising Manager would spend 1.5 to 2 full days per payout manually preparing donation data for Donorflex. In total, this added up to 3 to 4 days every month. The work was detailed and unforgiving. It included: Cleaning and standardising first and last name casing Applying salutations Removing email addresses where no communications consent was given Adding mandatory CRM and finance data such as donor type codes, category numbers, audit codes, income stream codes, account IDs and soft credit information Handling Gift Aid income separately, with additional codes applied in different rows All of this had to be done across hundreds of rows for each payout. Once cleaned, the data then needed to be transferred into Donorflex’s import template, a spreadsheet 130 columns wide, before finally being uploaded into the CRM. It was slow, repetitive and carried a constant risk of error. Life with Bridgit Bridgit automated all of the tasks above using custom, charity-specific rules. Rowans Hospice now has a scheduled bridge that runs automatically twice per month, aligned with MuchLoved payouts. The bridge applies almost all of the required data cleaning, transformations and coding, then delivers a Donorflex CRM-ready spreadsheet. The Fundraising Manager receives a Donorflex-ready import file, then completes a short final check and a handful of tweaks that Bridgit cannot yet automate. After that, it’s ready to upload into Donorflex. Impact 22 hours saved every month (reduced from 32 hours to around 10) Further reductions expected, with upcoming automations likely to bring this down to under 5 hours per month Cleaner, more consistent data Lower risk of errors A happier, less overloaded fundraising team So the process used to take me a day and a half to two days to complete… I just did it in a maximum of 5 hours. AMAZING!!! - Alexis Trowbridge, Legacy and In-Memory Giving Fundraising Manager, Rowans Hospice
Keeping supporter communication preferences accurate and up to date
Charities collecting donations through fundraising platforms need to ensure supporter details and communication preferences are accurately reflected in their CRM. This use case shows how Bridgit helps charities keep donor records clean, consistent and GDPR-compliant by automatically mapping consent data from MuchLoved into Donorflex. Real Life Example: How The Myton Hospices keeps supporter communication preferences in sync between MuchLoved and Donorflex Before Bridgit At The Myton Hospices, donations made through MuchLoved captured up-to-date supporter details and communication preferences. However, getting that information into Donorflex accurately required manual handling. Donorflex relies on specific internal codes to represent communication preferences, meaning data exported from MuchLoved had to be carefully transformed before import. This included ensuring consent-related fields were populated correctly, columns were ordered to match Donorflex’s import requirements and values aligned with existing CRM standards. Manually managing this process increased the risk of inconsistencies, outdated preferences and errors, particularly as supporter data changed over time. Life with Bridgit Using Bridgit, Myton set up a bridge that automatically transforms MuchLoved donation data into a Donorflex-ready format with communication preferences correctly applied. Custom rules and transformations map MuchLoved consent data into the appropriate coded fields in Donorflex, ensuring supporter contact permissions are always up to date. The bridge also standardises data to match CRM requirements, including: Applying title case to names Reordering spreadsheet columns to match Donorflex import templates Setting required codes such as country codes (e.g. United Kingdom to GBR) and other consistency fields The result is a clean, compliant import file that aligns with Donorflex CRM's data model and reflects the latest supporter preferences captured at the point of donation. Impact More accurate and up-to-date supporter communication preferences in Donorflex Reduced risk of contacting supporters incorrectly Reduced compliance and GDPR risks Improved data consistency across fundraising and CRM systems Less manual effort required to prepare and validate consent-related data Greater confidence in CRM data as a source of truth It’s like having a small team of API developers at your fingertips without the very costly agency fees or contractor fees. Bridgit is saving our supporter care team hours already. - Dan Brown, Digital Marketing Manager, The Myton Hospices
Standardising fundraising data, campaign attribution and financial reconciliation in Salesforce
Charities using multiple fundraising and payments platforms often struggle to land consistent, reportable data in Salesforce. This use case shows how Bridgit helps charities standardise incoming data, automate campaign attribution and prepare Salesforce-ready uploads that support accurate reporting and reconciliation. Real Life Example: How ARC Cancer Support Centres standardised multi-platform fundraising data for Salesforce reporting and reconciliation Before Bridgit At ARC Cancer Support Centres, fundraising data was coming from multiple platforms, each with different structures, naming conventions and reporting requirements. A key challenge was campaign attribution. Salesforce expects specific campaign codes in order to organise, report on and reconcile income correctly. Assigning these codes manually meant reviewing donation and event data line by line and setting campaign values by eye, one of the heaviest and most error-prone admin tasks for the fundraising and finance teams. Preparing data for upload also required spreadsheets to conform exactly to ARC’s Salesforce uploader tool, adding another layer of manual formatting and validation. This made backdated reconciliation particularly time-consuming, with historic data stretching back up to two years needing careful review before it could be confidently imported. Life with Bridgit Bridgit is being used to standardise and prepare fundraising data before it reaches Salesforce, starting with iDonate and expanding to other platforms including Stripe, Donorbox and Eventmaster. For campaign attribution, Bridgit applies a series of lookup rules that automatically assign Salesforce campaign codes based on keywords found in fundraising page titles or event names. For example: Pages containing the word “swim” are assigned the Dip in the Nip campaign code Pages containing “tennis” are assigned Tennis for Cancer 2025 These rules can be easily updated over time, allowing ARC to add new keywords and campaigns without manual rework. Bridgit also transforms incoming data so it conforms to ARC’s Salesforce uploader requirements, delivering spreadsheets that are ready to import and consistent across platforms. Alongside this, Bridgit is supporting the team with backdated uploads to help bring historic data into Salesforce in a structured and reportable way. In progress Work is currently underway to further support financial reconciliation by capturing and logging payout dates alongside donation dates. This will allow ARC to report accurately on when funds are received in the bank and reconcile platform payouts against Salesforce records. This functionality will be rolled out as part of the ongoing setup. Impact Significant reduction in manual campaign code assignment More consistent, Salesforce-ready data across fundraising platforms Faster and more reliable historic data reconciliation Improved confidence in Salesforce reporting for fundraising and finance teams A scalable setup that can expand to additional platforms over time With thanks to the project team, including: Hannah Hynes, Database & Donor Care Executive Stephanie Nolan, Head of Fundraising & Communications Paul Switzer, Head of Finance & Transformation, & Deputy CEO