Maqetin emails donors between one gift and the next.

A gift arrives and the donor hears nothing until the next appeal. Maqetin reads the gift in your donation events, waits, and sends an update to the donors who have not given again.

Mary Roe
A children’s charity · London · 09:00 BST
Sample
Today · Sunday 18 October
09:00:03
What your gift did in OctoberSent
Impact update
Friday 18 September
09:00:03
donation.completedweb
amount: 25currency: GBPcampaign: School meals
Trigger
Gift made
donation.completed
Wait
Wait 30 days
Condition
Given again?
donation.completedsince entering
Yes
Exit
Exit
No
Send email
Send impact update
Exit
Exit

Sample scene: a children’s charity in London.

The journey starts when your app sends donation.completed. It waits 30 days, then checks whether donation.completed arrived since the person entered. If it did, they leave and no email goes. If not, the email goes.

Report back to supporters.

It reports what the gift paid for and asks for nothing. The journey of this email is the impact update template.

  • One event, used twice. donation.completed starts the journey and ends it early if it arrives again within the 30 days.
  • Name the campaign. Send the campaign with donation.completed, and the email can name it.
  • Receipts take the send API. A receipt sent through the send API reaches donors who opted out of marketing; a journey email skips them.
FromYour app <hello@mail.example.com>SubjectWhat your gift did in OctoberPreviewNo ask in this one. Just what happened.

Hi Mary,

Your gift last month helped fund school meals in the first week of term.

See the update

Events to send.

Your donation system sends each one as it happens. The journey above uses the first.

donation.completed
A gift is made.
monthly_gift.started
A donor starts a monthly gift.
monthly_gift.failed
A monthly gift is declined.
volunteer.signed_up
A person signs up to volunteer.

The non-profit template.

Start with the donors who gave once.

Book a demo and we'll show you Maqetin on donor journeys like yours.