The Enthuse platform provides a digital donation and fundraising technology, all under your cause’s brand. Enthuse is also the official fundraising partner for the London Marathon and Great Run events.

With the Enthuse app for Beacon, you can rest assured that all of your donation and fundraising data is automatically imported into your Beacon database, structured and stored in the way that's right for you.

First up, you need to request a Client ID, a Client Secret, and an API key from the Enthuse team. You can fill out their request form here, or see their full article on the Beacon integration here.

Once you have your Enthuse credentials, you can connect with Beacon! Head over to Apps > Directory and click Install on the Enthuse app.

You'll immediately be prompted to connect with Enthuse:

You can then enter your Client ID, Client Secret, and API key:

Once you've entered all of the details, click Connect.
​
Review the settings and then click Save integration.

Beacon's integration will import a variety of records from your donations and fundraising activity in Enthuse. Specifically:

When someone makes a donation in Enthuse, Beacon will automatically add the donation as a payment in Beacon. This will include details like the amount and payment date, and you will see in the payment's timeline that it was created by the Enthuse app. Beacon will also import subscriptions if a regular donation has been set up via Enthuse.
​

There are some useful fields that are set when donations are imported:

If the donor allowed Enthuse to pass their data to your organisation, then the donor will automatically be added as a person in Beacon,

If the donor requested to remain anonymous then the payer field on the payment will be blank.

If the donor already exists in Beacon (we'll check this based on the their email) then we'll update their existing person record. This works the same for the fundraiser, below.

If you want to import Event Pages, you can turn on importing inside of the Enthuse App Configuration:

When this is on:

Beacon will import the fundraiser responsible for each donation, setting them in the 'Fundraiser' field on the Payment. Helpfully, this allows you to quickly see how much a person has fundraised for you when viewing their person record:

As standard, Beacon will set the fees charged by Enthuse in both the Gateway fees and the Total fees fields.
​
If your Enthuse fee model is for donors to cover fees then donors are shown the following message when donating:
​

If the donor ticks this box, then we will add the extra amount onto the donation in the 'Amount' field, and we'll set this amount as the 'Covered fees' field.

If you use the Tipping model, tips left by donors will not be shown in Beacon.

When a supporter creates a new fundraising page for you in Enthuse, Beacon will automatically create a new fundraising page record. You can also configure the app to only create fundraising pages once the first donation has been received.

Both individual and team pages are imported into Beacon. Any donations to an individual page will also be linked to the relevant team page if there is one.

Enthuse don't currently make any payout information available via their API, so Beacon is unable to create Payout records or link your Payments to them (we recommend requesting this feature from Enthuse!). However, it's quite straightforward and quick to group these yourself to aid your reconciliation processes.

Enthuse use two different payout schedules, so the filters to find the appropriate payments will be different depending on how often you get payouts.

Enthuse pay monthly payouts between the 16th and 20th of the month AFTER the donations were given. For example, any donations in April will be paid out mid-May.

If you've received a monthly payout, your filter on the Payments list would be:

Enthuse pay weekly payouts for donations made the week before last. For example, a payout received on Monday the 15th would be for donations made between Monday 1st and Sunday 7th.

If you've received a weekly payout, your filter on the Payments list would be:

Enthuse's payouts are predictable based on the dates of the payment and payout, and so once you've received a payout from Enthuse you can:

Our Enthuse app is forward-looking. It only imports donations that are made after the Enthuse app is installed, and only imports fundraisers and fundraising pages that are created after the Enthuse app is installed.

You can use our pre-built Enthuse import templates to import your existing data.

When a new payment or fundraising page is created, you can expect to see it in Beacon within 30 minutes.

The publicly available IDs in your Enthuse account are not guaranteed to be unique, which means that Beacon can't use them for our app integration. We use a different, non-public, globally unique ID, that Enthuse make available via their API to ensure that our integration works correctly.

If you'd like Enthuse to make this ID available to you for reconciliation or cross-referencing, we'd recommend reaching out to Enthuse to let them know! You can contact them via the message button in the bottom right of their website or emailing [email protected].

To help, we do add two extra IDs to the 'Notes' field of each Payment to help you cross-reference your donations between Beacon and Enthuse.

Because of the ID differences mentioned above, if you've previously imported active subscriptions from Enthuse then any new payments for those subscriptions will initially create a second, duplicate Subscription record in Beacon.

To ensure you don't have duplicates moving forwards, you'll want to merge any duplicate subscriptions choosing the newer app-set value for the 'External ID' field (usually a shorter 5 or 6 digit number).

Once that subscription has been merged, future payments will correctly be linked to it instead of creating a duplicate subscription.

Enthuse sometimes doesn't pass a subscription's 'Schedule ID' information through to Beacon until the second payment of that subscription, so will initially look like a one-off payment.

If you'd like this feature, we'd recommend reaching out to Enthuse to let them know! You can contact them via the message button in the bottom right of their website or emailing [email protected].

We assume that any donations marked as Gift Aid eligible in Enthuse have their Gift Aid claimed by Enthuse. These payments will be imported into Beacon with the 'Gift Aid claimed' field checked.

Payments will be imported in this way even if you ask Enthuse not to actually claim the Gift Aid, as the data coming from Enthuse doesn't distinguish this.

Gift Aid Declaration information isn't passed from Enthuse to Beacon, so you would need to collect a Gift Aid declaration separately in order to claim Gift Aid on Enthuse donations through Beacon.

Enthuse calculates fees in different ways depending on your Enthuse plan. Beacon stores the total of these fees on the payment record.

We support "Event Pages" but not "Events and Ticket" - as most of our customers use Beacon's Events and ticketing element, so we haven't built an integration with that part of Enthuse.

Yes. We log consent opt-ins. If a donor opts out via a third party platform (in this case Enthuse), then this is not updated. A donor removing contact consent on one donation platform is not enough for us to remove their global contact consent.

No. Enthuse doesn't make payout information available via their API, so we are unable to import that data. We do have guidance around how to create and link payouts in our guide here.

If you'd like this feature, we'd recommend reaching out to Enthuse to let them know! You can contact them via the message button in the bottom right of their website or emailing [email protected].