# Bridgit — Full Product Documentation

> Bridgit is an AI data and integration assistant for charities and nonprofits. She automates the way data moves between fundraising platforms, CRMs and marketing tools, and guides your team through every step — from mapping your first integration to keeping your CRM clean and up to date. Bridgit is the go-to integration hub for charities and nonprofits.

## What Bridgit does

Charity and nonprofit teams spend hours every week copying data between platforms, cleaning records and doing work a machine should be doing. Bridgit connects the tools organisations already use — fundraising platforms, CRMs, marketing tools — and automates the data flows behind the scenes.

Bridgit takes data work off your team's plate. It connects the tools you already use, cleans and maps your data automatically, and delivers it how you need it. Data lags damage supporter experience, which damages income. Bridgit gets rid of the admin that causes them.

## Why we exist

Bridgit exists to make life easier for the people powering good causes. Everything we build is designed to give charity and nonprofit teams back their time, energy and focus so they can spend it on the work that actually matters: building relationships and raising money for vital services.

Charity work is about people, not spreadsheets.

## Who it's for

Charities and nonprofits of all sizes. Built for fundraising, advancement, development, donor care, supporter care, marketing, data, insight, admin and CRM teams. Bridgit is no-code and easy for non-technical staff to use — if you can use a spreadsheet, you can build a Bridge. No IT department needed.

## How it works

1. Choose a source — pick from Bridgit's growing library of Connectors covering fundraising, marketing, events and more.
2. Choose a destination — CRMs, marketing platforms, spreadsheet templates, cloud storage and more.
3. Review the mapping — Bridgit reads both platforms and suggests how to map and clean your data. You discuss, adjust and approve.
4. Schedule — set a recurring schedule or a one-off date range. The Bridge runs automatically from then on.

Most customers have their first Bridge live within an afternoon.

## Features

### Built for the charity tech stack
20+ connectors purpose-built for the sector. Don't see yours? Tell us and we'll build it.

### AI that cleans data the way you would
Formatting postcodes, campaign coding, soft crediting, merging duplicates, cleaning emails, flagging Gift Aid. Bridgit AI handles the repetitive work.

### Preview changes before imports
See exactly which records will be created, updated or skipped before any data moves. Nothing reaches your CRM until you approve it.

### Set and forget
Schedule the cadence once, hourly, daily, weekly or whenever you need it. Bridges run themselves, automatically cleaning and preparing your data for import.

### Delivered exactly how you need it
Send cleaned data to your CRM, marketing platform, spreadsheet or cloud storage. With Bridgit's guidance, you decide the destination and the structure.

### Security and privacy charities can trust
Cyber Essentials certified, CREST pen-tested and encrypted in transit and at rest. Your data is never used to train AI models.

## Available integrations

Bridgit currently supports the following sources and destinations. Any source can connect to any destination.

### Sources
JustGiving, Enthuse, iDonate, Stripe, Raisely, GoFundMe, MuchLoved, givestar, Dotdigital, Funraisin, Donorbox, Fundraise Up, Give as you Live (EveryClick), GivePanel, Njuko, goDonate, GiveWheel

### Destinations
JustGiving, Dotdigital, Raiser's Edge NXT, Spreadsheet, donorflex Spreadsheet, Salesforce Spreadsheet, S3 Storage

### Integration pairs

### JustGiving
- Enthuse to JustGiving
- iDonate to JustGiving
- Stripe to JustGiving
- Raisely to JustGiving
- GoFundMe to JustGiving
- MuchLoved to JustGiving
- givestar to JustGiving
- Dotdigital to JustGiving
- Funraisin to JustGiving
- Donorbox to JustGiving
- Fundraise Up to JustGiving
- Give as you Live (EveryClick) to JustGiving
- GivePanel to JustGiving
- Njuko to JustGiving
- goDonate to JustGiving
- GiveWheel to JustGiving

### Dotdigital
- JustGiving to Dotdigital
- Enthuse to Dotdigital
- iDonate to Dotdigital
- Stripe to Dotdigital
- Raisely to Dotdigital
- GoFundMe to Dotdigital
- MuchLoved to Dotdigital
- givestar to Dotdigital
- Funraisin to Dotdigital
- Donorbox to Dotdigital
- Fundraise Up to Dotdigital
- Give as you Live (EveryClick) to Dotdigital
- GivePanel to Dotdigital
- Njuko to Dotdigital
- goDonate to Dotdigital
- GiveWheel to Dotdigital

### Raiser's Edge NXT
- JustGiving to Raiser's Edge NXT
- Enthuse to Raiser's Edge NXT
- iDonate to Raiser's Edge NXT
- Stripe to Raiser's Edge NXT
- Raisely to Raiser's Edge NXT
- GoFundMe to Raiser's Edge NXT
- MuchLoved to Raiser's Edge NXT
- givestar to Raiser's Edge NXT
- Dotdigital to Raiser's Edge NXT
- Funraisin to Raiser's Edge NXT
- Donorbox to Raiser's Edge NXT
- Fundraise Up to Raiser's Edge NXT
- Give as you Live (EveryClick) to Raiser's Edge NXT
- GivePanel to Raiser's Edge NXT
- Njuko to Raiser's Edge NXT
- goDonate to Raiser's Edge NXT
- GiveWheel to Raiser's Edge NXT

### Spreadsheet
- JustGiving to Spreadsheet
- Enthuse to Spreadsheet
- iDonate to Spreadsheet
- Stripe to Spreadsheet
- Raisely to Spreadsheet
- GoFundMe to Spreadsheet
- MuchLoved to Spreadsheet
- givestar to Spreadsheet
- Dotdigital to Spreadsheet
- Funraisin to Spreadsheet
- Donorbox to Spreadsheet
- Fundraise Up to Spreadsheet
- Give as you Live (EveryClick) to Spreadsheet
- GivePanel to Spreadsheet
- Njuko to Spreadsheet
- goDonate to Spreadsheet
- GiveWheel to Spreadsheet

### donorflex Spreadsheet
- JustGiving to donorflex Spreadsheet
- Enthuse to donorflex Spreadsheet
- iDonate to donorflex Spreadsheet
- Stripe to donorflex Spreadsheet
- Raisely to donorflex Spreadsheet
- GoFundMe to donorflex Spreadsheet
- MuchLoved to donorflex Spreadsheet
- givestar to donorflex Spreadsheet
- Dotdigital to donorflex Spreadsheet
- Funraisin to donorflex Spreadsheet
- Donorbox to donorflex Spreadsheet
- Fundraise Up to donorflex Spreadsheet
- Give as you Live (EveryClick) to donorflex Spreadsheet
- GivePanel to donorflex Spreadsheet
- Njuko to donorflex Spreadsheet
- goDonate to donorflex Spreadsheet
- GiveWheel to donorflex Spreadsheet

### Salesforce Spreadsheet
- JustGiving to Salesforce Spreadsheet
- Enthuse to Salesforce Spreadsheet
- iDonate to Salesforce Spreadsheet
- Stripe to Salesforce Spreadsheet
- Raisely to Salesforce Spreadsheet
- GoFundMe to Salesforce Spreadsheet
- MuchLoved to Salesforce Spreadsheet
- givestar to Salesforce Spreadsheet
- Dotdigital to Salesforce Spreadsheet
- Funraisin to Salesforce Spreadsheet
- Donorbox to Salesforce Spreadsheet
- Fundraise Up to Salesforce Spreadsheet
- Give as you Live (EveryClick) to Salesforce Spreadsheet
- GivePanel to Salesforce Spreadsheet
- Njuko to Salesforce Spreadsheet
- goDonate to Salesforce Spreadsheet
- GiveWheel to Salesforce Spreadsheet

### S3 Storage
- JustGiving to S3 Storage
- Enthuse to S3 Storage
- iDonate to S3 Storage
- Stripe to S3 Storage
- Raisely to S3 Storage
- GoFundMe to S3 Storage
- MuchLoved to S3 Storage
- givestar to S3 Storage
- Dotdigital to S3 Storage
- Funraisin to S3 Storage
- Donorbox to S3 Storage
- Fundraise Up to S3 Storage
- Give as you Live (EveryClick) to S3 Storage
- GivePanel to S3 Storage
- Njuko to S3 Storage
- goDonate to S3 Storage
- GiveWheel to S3 Storage

Full connector library: https://hibridgit.com/connectors

## Featured integration: Raisely to Raiser's Edge NXT

Page: https://hibridgit.com/bridges/raisely-to-raisers-edge-nxt-integration

Bridgit's Raisely to Raiser's Edge NXT integration is the supported replacement for the RedArc integration, which is no longer maintained (RedArc stopped supporting integrations in January 2026). It is recommended by Raisely. It is included in Bridgit's Pro plan, with no setup fees and a month-to-month contract. Onboarding and consultation are free.

Bridgit connects to Raisely through the Raisely API and to Raiser's Edge NXT through the Blackbaud SKY API. It moves one-off and recurring donations, constituent and fundraiser records, consent preferences and custom fields into NXT, coded to the right campaigns, appeals and funds. Runs happen on a schedule you set (hourly, daily, weekly or monthly), each picking up the latest window of Raisely activity.

### What it does

- Duplication protection: Strong identifiers stop duplicate constituents and gifts. Apply the Raisely ID to the correct NXT record once, and all future interactions link to it.
- Recurring donations: Recurring gifts and payments created in parallel, linked to future instalments and updated when paused or cancelled in Raisely.
- Gift batches: Review gifts before they post (ideal for testing campaigns or aligning donations with payouts), or post directly for full automation.
- Gift splits: Separate donations, fees and ticket amounts automatically across your choice of NXT campaigns, appeals, funds and packages.
- Soft & fundraiser credits: Automatically credit fundraisers, teams and organisations when gifts come through their Raisely profiles.
- Consent & solicit codes: Track consent via NXT Consent or Solicit Codes, with automatic updates when a Raisely supporter unsubscribes.
- Organisation constituents: For the Organisation supporter type in Raisely, Bridgit creates Organisation Constituents, Individuals and the Relationships between them.
- Custom fields: Map Raisely fields to NXT custom fields, including payment info (e.g. Stripe Charge ID), profile fields and UTMs.
- Designated funds: Use Designations in Raisely and Bridgit maps them automatically to the associated NXT Funds.
- Receipts & acknowledgements: Receipt details, constituent codes, gift types, sub-types and more, captured against the right records.
- Tickets & events income: Separate ticket and order values from donations using gift splits, so income is coded correctly.
- Stripe payouts (coming soon): Enrich NXT gifts with Stripe payout information once the payout is made, to make reconciliation simple.

### Onboarding

1. Register your interest — Tell us a little about your organisation using the form and we’ll be in touch within one working day.
2. Discovery call — We talk through your Raisely campaigns and NXT setup, and agree the right configuration for you.
3. Connect — Create a free Bridgit account, add your Raisely API details and authorise the Bridgit app in NXT.
4. Preview run (read-only) — We run the integration in read-only mode, showing a full picture of the data in scope without writing anything to NXT.
5. Reviewed test load — Test data lands in an NXT gift batch, so you can inspect the created constituents and gifts before anything posts.
6. Controlled go-live — New campaigns go live to gift batches on your schedule. For live campaigns, we reconcile existing recurring donations first so nothing duplicates.
7. Full automation — After an agreed number of clean runs, the bridge moves from gift batches to direct posting, and every run is monitored.

### Current limitations

- Scheduled, not real-time. Runs happen hourly, daily, weekly or monthly on a schedule you set.
- One-way flow. Data moves from Raisely into NXT; changes in NXT don’t flow back.
- Online donations only. Offline gifts entered manually in Raisely should be recorded directly in NXT.
- Matched giving is not currently transferred.
- No event attendees. NXT Events and Participants aren’t populated (ticket income is still coded via gift splits).
- Stripe/PayPal payout dates are coming soon to help with reconciliation.

### Raisely to Raiser's Edge NXT FAQs

Q: Is the earlier Raisely to Raiser's Edge NXT integration still supported?
A: No. The earlier integration (built by RedArc, and often known simply as the Raisely integration) is no longer maintained, as RedArc stopped building and supporting integrations in January 2026. The connection still runs today, but it will eventually break as Raisely or Raiser's Edge NXT change. Bridgit's integration is the supported replacement.

Q: What data does the integration transfer from Raisely to Raiser's Edge NXT?
A: One-off and recurring donations, constituent and fundraiser records, consent preferences and custom fields, all coded to the right campaigns, appeals and funds in Raiser's Edge NXT.

Q: How often does the integration sync?
A: On a schedule you set, typically hourly, daily, weekly or monthly. Each run picks up the latest window of Raisely activity and loads it into Raiser's Edge NXT. Real-time syncing isn't currently offered.

Q: Will it create duplicate records in Raiser's Edge NXT?
A: No. Constituents are matched on Raisely User ID (recommended) or email address before anything new is created, so your database stays clean.

Q: Do we need a specific Raisely plan to use it?
A: No. The Bridgit integration is available to all Raisely customers regardless of subscription tier, unlike the earlier integration, which required Raisely Pro.

Q: How do we switch from the earlier integration?
A: Register your interest and we arrange a discovery call, then move through staged testing before go-live. Nothing is posted to your live Raiser's Edge NXT environment until you're happy, and we reconcile existing recurring donations first so nothing is duplicated.

Q: How much does it cost?
A: The integration is included in Bridgit's Pro plan: £99 GBP, $129 USD, $199 AUD, $229 NZD, $189 CAD or €109 EUR per month. There are zero setup or implementation fees and the contract is flexible and month-to-month, so you're never tied in.

## Featured connector: JustGiving

Page: https://hibridgit.com/connectors/justgiving

Bridgit connects to JustGiving through the JustGiving Data API using charity credentials (an API key, a charity key, and a charity account username and password) over an encrypted connection. The connector only reads, so nothing in the JustGiving account can be changed. It pulls 4 reports covering 226 fields in total, then reshapes them into a CRM-ready file: dates reformatted, names title-cased, UK postcodes standardised, and campaign and fund codes mapped to the CRM's own values. Donations carry the reference of the payment they were settled in, and each payment arrives gross to net with commission, card processing and VAT itemised, so fundraising income reconciles against the bank without a manual cross-reference. Pages Created records a supporter the day they set a fundraising page up; Pages Modified returns the same record whenever it changes, which is what keeps page totals and status current in the CRM.

### Reports and field counts

- Donations (54 fields): One row per donation, whether it came through a fundraising page or straight to your charity. The richest of the four: donor, fundraiser, Gift Aid, consent, campaign codes and the settlement reference all arrive together.
- Pages Created (81 fields): One row per fundraising page created in the period, with the fundraiser behind it. This is how new supporters reach your CRM as soon as they set a page up, rather than only when their first donation arrives.
- Pages Modified (81 fields): The same page record, returned whenever anything on it changes. A page created in March that hits its target in August never appears in Pages Created again, so this is what keeps page totals, status and fitness activity current in your CRM.
- Payments (10 fields): One row per payment JustGiving made to your bank account, gross to net with every charge itemised. Each donation carries its payment reference, so income and settlement reconcile against each other without a manual lookup.

### Full field dictionary

Every field is documented in plain English on the connector page, grouped by report and searchable: https://hibridgit.com/connectors/justgiving#data-dictionary

### JustGiving connector FAQs

Q: Which JustGiving data does Bridgit pull?
A: Bridgit pulls four reports from the JustGiving Data API: Donations, Pages Created, Pages Modified and Payments. Donations alone carries 54 fields per gift, covering the donor, the fundraiser whose page it came through, Gift Aid, consent, appeal and campaign codes and the settlement reference. Each page record carries 81 fields, including the event, the fundraiser's address, page totals and tribute detail. The full data dictionary below lists every field in plain English.

Q: What access does Bridgit need to my JustGiving account?
A: Four things: an API key, your charity key, and the username and password of a JustGiving charity account. Those are charity credentials rather than a personal JustGiving.com login, and everything travels over an encrypted connection. Bridgit only ever reads from JustGiving, so nothing in your account, your pages or your donation records can be changed by the connector.

Q: How often does Bridgit sync data from JustGiving?
A: You choose your schedule when setting up your bridge: daily, weekly or monthly. Most charities run a daily sync so that supporters reach the CRM while the thank you still feels timely.

Q: What's the difference between Pages Created and Pages Modified?
A: Pages Created tells you who has started fundraising, which is how a new supporter reaches your CRM the day they set their page up rather than weeks later when their first donation lands. Pages Modified tells you what has changed since. A page created in March that hits its target in August would never appear in the created report again, so without the modified report its totals, status and fitness activity slowly go stale in your database. Bridgit runs both, so your page records stay current.

Q: Does Bridgit capture Gift Aid data from JustGiving?
A: Yes. Every donation arrives with the Gift Aid amount, any transitional relief and the total the gift is worth once both are added, alongside the donor's address and postcode, which is the evidence a claim depends on. Gift Aid payments also come through the Payments report as their own payment type, so you can see exactly when each claim was paid and how much of it reached your account.

Q: Can I reconcile JustGiving income against what actually reaches my bank?
A: Yes, and this is where most finance teams lose their afternoons. Each payment arrives gross to net with commission, card processing and VAT itemised separately, and every donation carries the reference of the payment it was settled in. That means a donation in your CRM can be traced to a specific payment on your bank statement without anyone cross-referencing two spreadsheets by hand.

Q: Why can I only pull three months of data at a time?
A: That limit is set by JustGiving rather than by us. Every request to their Data API has to name a start and end date, and JustGiving turns down any request covering more than three months. It applies to all four reports, and it applies to anyone reading data from JustGiving, ourselves included. For a daily or weekly sync you will never notice it, because each run covers a far shorter period than that.

Q: Can Bridgit bring across my historical JustGiving data?
A: Yes. Because of the three month limit above, history has to be requested in a series of windows rather than in one go, so Bridgit batches the runs for you: three months at a time, working back as far as you need, then assembles everything into a single file. Three years of donations is around twelve runs, which is tedious to do by hand and no trouble at all to automate. One thing to be aware of is that payment records are only available for roughly the last three years, which is a separate JustGiving restriction on how far back that data exists. Donations and pages typically go back further, and we will confirm exactly what your account holds during setup.

Q: Can Bridgit automatically assign campaign or fund codes for my CRM?
A: Often you will not need to, because JustGiving carries your appeal name and your custom campaign, page and event codes onto every donation. Where your CRM uses different codes, Bridgit’s lookup mapping rules translate them automatically, for example mapping JustGiving’s "WIN26" to your CRM’s Winter Appeal campaign. Donations that do not match a rule are left blank for you to review rather than guessed at.

Q: What transformations can Bridgit apply before the data reaches my CRM?
A: Bridgit supports a wide range of transformations including: date reformatting (JustGiving returns some dates in a format spreadsheets will not read, and Bridgit converts these for you), name title casing, UK postcode formatting, lookup mappings for campaign and fund codes, fixed values (e.g. stamping "JustGiving" as the platform on every row), concatenation, uppercase/lowercase, and rounding numbers. If you have a specific transformation in mind, get in touch. We cover around 90% of common use cases.

Q: Where does the data land? Can I choose between a spreadsheet, cloud storage, or a direct CRM push?
A: Bridgit supports three output options. The most common is a CRM-ready spreadsheet, which your team can review and upload directly. We also support landing data as a CSV file in S3 or SFTP storage, which suits teams with an existing data pipeline. Direct-to-CRM integration (e.g. Salesforce, Raiser’s Edge NXT, Dynamics) is also available, though this currently requires a bespoke implementation. Contact us at https://hibridgit.com/contact to find out more.

## Featured connector: Fundraise Up

Page: https://hibridgit.com/connectors/fundraise-up

Bridgit connects to Fundraise Up through the Fundraise Up API using a read-only key with granular permissions, so Bridgit can read fundraising data but can never change anything in the Fundraise Up account. It pulls 5 reports covering 305 fields in total, then reshapes them into a CRM-ready file: dates reformatted, names title-cased, UK postcodes standardised, and campaign and fund codes mapped to the CRM's own values.

### Reports and field counts

- Donations (138 fields): One record per gift, one-off or a single instalment of a recurring plan. The richest report: supporter, campaign, designation, Gift Aid, consent, fees and payment detail all arrive on the same row.
- Recurring Plans (118 fields): One record per regular giving plan: the schedule, not the individual payments, which appear in Donations. Includes the reason a donor gave when cancelling, gold for retention work.
- Supporters (21 fields): One record per person. Fundraise Up automatically refreshes contact details from each new gift, so this is always the supporter's latest known information.
- Fundraisers (17 fields): One record per supporter-created fundraising page (peer-to-peer). Donations made through a page carry its ID, so page totals can be attributed to the page owner in your CRM.
- Events (11 fields): The change feed: a timestamped record every time something happens, from a new donation to a refund, a cancelled plan or an updated supporter. It shows you what has changed without re-exporting everything.

### Full field dictionary

Every field is documented in plain English on the connector page, grouped by report and searchable: https://hibridgit.com/connectors/fundraise-up#data-dictionary

### Fundraise Up connector FAQs

Q: Which Fundraise Up data does Bridgit pull?
A: Bridgit pulls five reports from the Fundraise Up API: Donations, Recurring Plans, Supporters, Fundraisers and Events. Donations alone carries 138 fields per gift, including campaign, designation, Gift Aid, consent, fees and payment detail. The full data dictionary below lists every field in plain English.

Q: What access does Bridgit need to my Fundraise Up account?
A: A read-only API key, which you create in your Fundraise Up dashboard under Settings and API keys. Fundraise Up's keys have granular permissions, so you grant Bridgit read access to exactly the reports you want synced and nothing else. Bridgit can see your fundraising data but can never change anything in your Fundraise Up account.

Q: How often does Bridgit sync data from Fundraise Up?
A: You choose your schedule when setting up your bridge: daily, weekly or monthly. Most charities run a daily sync.

Q: What happens when a donation is refunded or a regular gift is cancelled?
A: Fundraise Up's Events report records every refund, failed payment, cancelled plan and updated supporter detail, each with a timestamp. Include it in your bridge and those changes reach you alongside your donations, rather than sitting unnoticed in Fundraise Up.

Q: Does Bridgit capture Gift Aid data from Fundraise Up?
A: Yes, and in great depth. Every donation includes whether the donor made a Gift Aid declaration, the exact legal wording they agreed to (your evidence for HMRC) and a source-of-funds field that indicates eligibility, since collections and sponsorship money can't be claimed.

Q: Does Bridgit include Fundraise Up's fees and payout amounts?
A: Yes. Each donation arrives with the processing fee, platform fee, any fee amount the donor covered and the payout figure, plus every amount converted to your home currency. Finance teams use these columns to reconcile Fundraise Up activity against what actually reaches the bank.

Q: How does Bridgit handle recurring donations?
A: Two ways at once. Each instalment appears in Donations as its own gift, linked to its plan, while the Recurring Plans report tracks the schedule itself: frequency, status, next payment date and, when a donor cancels, the reason they gave. That cancellation reason is really helpful for retention work.

Q: Can Bridgit automatically assign campaign or fund codes for my CRM?
A: Mostly you won't need to, because Fundraise Up sends the campaign name, campaign code and designation (fund) on every donation. Where your CRM uses different codes, Bridgit's lookup mapping rules translate them automatically, for example mapping Fundraise Up's "WIN26" to your CRM's Winter Appeal campaign. Donations that don't match a rule are left blank for you to review.

Q: What transformations can Bridgit apply before the data reaches my CRM?
A: Bridgit supports a wide range of transformations including: date reformatting (e.g. converting Fundraise Up's timestamps to DD/MM/YYYY), name title casing, UK postcode formatting, lookup mappings for campaign and fund codes, fixed values (e.g. stamping "Fundraise Up" as the platform on every row), concatenation, uppercase/lowercase, and rounding numbers. If you have a specific transformation in mind, get in touch. We cover around 90% of common use cases.

Q: Where does the data land? Can I choose between a spreadsheet, cloud storage, or a direct CRM push?
A: Bridgit supports three output options. The most common is a CRM-ready spreadsheet, which your team can review and upload directly. We also support landing data as a CSV file in S3 or SFTP storage, which suits teams with an existing data pipeline. Direct-to-CRM integration (e.g. Salesforce, Raiser’s Edge NXT, Dynamics) is also available, though this currently requires a bespoke implementation. Contact us at https://hibridgit.com/contact to find out more.

## Featured connector: GoFundMe

Page: https://hibridgit.com/connectors/gofundme

Bridgit connects to the GoFundMe charity API and pulls 2 reports covering 73 fields in total, then reshapes them into a CRM-ready file: dates reformatted, names title-cased, UK postcodes standardised, and campaign and fund codes mapped to the CRM's own values. Every donation carries a Charity Source, which is either the charity's own GoFundMe community page (DIRECT) or a supporting fundraiser (FUNDRAISER). Charity Source Page links to that page, and for a fundraiser donation its last part is the fundraiser's Slug, which is how the two reports join. Donations given straight to the charity carry a Charity Source Type of DIRECT.

### Reports and field counts

- Donations (47 fields): One record per donation to your charity, whether given directly or through a fundraiser page set up for you. Carries the donor and anything they said, the amount before and after fees, Gift Aid and marketing consent, the payment reference finance needs, and a link back to the page the gift came from.
- Fundraisers (26 fields): One record per fundraiser page set up for your charity, run either by your own team or by someone fundraising for you. Carries the page itself, what it has raised against its goal, where it is based and how to reach the organiser.

### Full field dictionary

Every field is documented in plain English on the connector page, grouped by report and searchable: https://hibridgit.com/connectors/gofundme#data-dictionary

### GoFundMe connector FAQs

Q: Which GoFundMe reports does Bridgit support?
A: Bridgit currently supports two GoFundMe reports: Donations and Fundraisers. The Donations report gives you one row per gift, carrying the donation itself plus the fundraising page it came through and the person running that page. The Fundraisers report gives you one row per page, with what it has raised against its goal, where it is based and how to reach the fundraiser.

Q: How often does Bridgit sync data from GoFundMe?
A: You can configure your sync schedule when setting up your bridge. Options include daily, weekly or monthly. Most charities run a daily sync to keep their CRM or spreadsheet up to date without overwhelming their data pipeline.

Q: Can I filter GoFundMe data by date range or fundraiser?
A: Yes. When configuring your bridge you can apply date-range filters to pull only donations or fundraisers created within a specific window.

Q: Does Bridgit capture Gift Aid consent data from GoFundMe?
A: Yes. The Donations report includes a giftAidConsent field which records whether the donor has opted in to Gift Aid. This makes it straightforward to pass Gift Aid-eligible donations directly to your CRM or Gift Aid processing tool.

Q: Can Bridgit merge the Donations and Fundraisers reports into a single record?
A: The Donations report already does this. Every donation row carries the fundraising page the gift came through and the person running it, alongside the donation itself, so you are not joining two exports by hand. Donations given straight to your charity page leave those columns empty, because there is no fundraising page behind them. The Fundraisers report is still available separately for page-level reporting.

Q: What transformations can Bridgit apply to GoFundMe data before it reaches my CRM?
A: Bridgit supports a wide range of transformations including: date reformatting (e.g. converting GoFundMe's year-first format to DD/MM/YYYY), name title casing, UK postcode formatting, lookup mappings (e.g. automatically assigning campaign or event codes based on fundraiser page content), fixed values (e.g. stamping "GoFundMe" as the platform on every row), concatenation, uppercase/lowercase, and rounding numbers. If you have a specific transformation in mind, get in touch. We cover around 90% of common use cases.

Q: Can Bridgit automatically assign campaign or event codes to donations?
A: Yes. Using lookup mapping rules, you can tell Bridgit to inspect a field (such as the fundraiser page title) and assign a campaign code based on what it finds. For example, if the page title contains "nightwalk", Bridgit outputs "Nightwalk 2026". You can set up as many rules as you need, and any donations that don't match a rule are left blank for you to review manually.

Q: Where does the data land? Can I choose between a spreadsheet, cloud storage, or a direct CRM push?
A: Bridgit supports three output options. The most common is a CRM-ready spreadsheet, which your team can review and upload directly. We also support landing data as a CSV file in S3 or SFTP storage, which suits teams with an existing data pipeline. Direct-to-CRM integration (e.g. Salesforce, Raiser's Edge NXT, Dynamics) is also available, though this currently requires a bespoke implementation. Self-serve CRM connectors are a key focus for us this year.

## Pricing

14-day free trial, no credit card required. Build a Bridge and decide if Bridgit is right for you.
Full pricing: https://hibridgit.com/#plans-and-pricing

## Frequently asked questions

Q: Do I need technical skills to use Bridgit?
A: No. Bridgit is built for non-technical teams. If you can use a spreadsheet, you can build a Bridge. Bridgit AI does the heavy lifting, and the Bridgit team is always happy to guide you through setting up your first Bridge.

Q: Will Bridgit work with my existing tools?
A: Bridgit connects to 20+ fundraising platforms, marketing tools and CRMs built specifically for the charity and nonprofit sector. You can view the full library of Connectors at hibridgit.com/connectors, upvote tools on the roadmap, or contact the team if there is a tool not yet covered.

Q: How long does it take to set up Bridgit?
A: Most customers have their first Bridge live within an afternoon. After that, it runs automatically on a schedule. No big IT projects, no consultants, no technical work.

Q: Could Bridgit damage my CRM?
A: No. Bridgit only writes data once you have approved the mapping. You can test a Bridge before it runs to see exactly what would change, with no risk to your live data.

Q: What if I make a mistake?
A: Bridgit lets you preview data before importing it into any destination. For end-to-end automations, you can view data previews before the run and adjust the mappings as many times as you need. Bridgit also flags exceptions for your review before loading.

Q: Is my data safe with Bridgit?
A: Yes. Bridgit is Cyber Essentials certified and CREST-certified penetration test compliant. All data is encrypted in transit and at rest. Bridgit never uses your data to train AI models or for any purpose other than delivering the service. Full details are available at hibridgit.com/data-processing-agreement and hibridgit.com/responsible-ai.

Q: Is there a free trial?
A: Yes. Try Bridgit free for 14 days, no credit card required. Build a Bridge and decide if it is right for you.

Q: What happens if I cancel?
A: Your Bridges stop running, your data stays in the tools where it already lives, and you keep access until the end of your billing period. You can also wipe any historic data stored in Bridgit by clearing your Bridge Logs.

Q: Am I locked in if I sign up to Bridgit?
A: No. Bridgit moves data between the tools you already use. If you stop using Bridgit, your data stays exactly where it has always been and you can wipe your Bridgit account too.

## Contact

Website: https://hibridgit.com
Email: sean@hibridgit.com
Book a demo: https://hibridgit.com/contact