⚠️ Important: Only paid-for event registrations are supported. Free events are not added due to limitations in the data provided by Enthuse.
Understand How Event Registration Data Is Received
Event registration data from Enthuse is received in two distinct parts.
The Registrant, including name, email address, and contact preferences.
The Payment Person, including name, address, and email address.
Because these two records may represent different people, Donorfy creates two separate constituent profiles by default.
See How Constituents Are Created
For paid events, Donorfy creates constituent profiles automatically.
Create one constituent for the Registrant.
Create one constituent for the Payment Person.
Even when both records relate to the same individual, Donorfy cannot assume this automatically.
Understand Transactions and Soft Credits
Transactions and soft credits are handled in a consistent way.
Adds the payment as a Transaction in Donorfy, as described in Enthuse - How Transactions are added
Creates a Soft Credit linking the transaction to the Registrant constituent profile.
This ensures attendance is recognised even when someone else paid for the ticket.
Manage Duplicate Constituent Records
Once event data has been added, manual data management is recommended.
Why Records Need Reviewing
Duplicate profiles can make reporting more difficult.
Payment details, including addresses, are stored on the Payment Person profile.
Names may be formatted unexpectedly due to how “Name on card” data is passed from Enthuse.
Example:
Name on card entered as Mr G Gray, the resulting Donorfy fields will be:
Title: (blank).
First Name: Mr.
Last Name: G Gray.
Get Notified of New Event Registrations
You can automate notifications to review new registrations.
Create a Transaction List
Create a transaction list using the following criteria.
Set List Type to Transaction – All.
Add filters:
Type equals Payment.
Entered By equals Donorfy.Enthuse.
Date Added equals Today.
Product equals the product used for Enthuse event tickets.
Create a Trigger
Create a trigger linked to the transaction list.
Set Trigger Type to Transaction Added.
Link the trigger to the transaction list.
Add the action Email to User.
📌 Note:
Do not activate the trigger until setup is complete.
Configure the Email
Include enough detail to locate the records easily.
Recommended placeholders:
Constituent Number:
{Transaction_ConstituentNumber}.Transaction Number:
{EntityNumber}.Date Added:
{DateAdded}.
Once configured, activate the trigger.
Merge Constituents Where Appropriate
When notified of a new event registration, review whether the two constituents represent the same person.
Open both constituent profiles.
Start the merge process.
Use the following merge roles:
Target Constituent: The Registrant (profile you want to keep).
Source Constituent: The Payment Person (profile with the transaction).
After the merge:
The address and transaction move to the Registrant profile.
Communication preferences, name, and email remain unchanged.
The Registrant timeline shows both the transaction and the soft credit.
Remove the Soft Credit After Merging
Once the merge is complete, the soft credit is no longer required.
Open the transaction.
Click the Delete button next to the soft credit.
Click Save to confirm the change.
Donorfy Academy
The Donorfy Academy features a certification learning course for Enthuse - enrol here.