Bridgit

USE CASES

Keeping supporter communication preferences accurate and up to date

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.