In addition to the contribution received email to your supporters, Givecloud can send a customized email for a specific item placed in the contribution.

Item-specific emails are great for items like an event registration product. In this case, perhaps you would like Givecloud to send an email with the event's details, including a QR code for check-in.


Set up a Product Purchase Email

From the left menu, select Communicate > + New Automated Email.

The General Panel helps set up and identify this email internally. None of the information you provide in these fields will be seen by the supporter. Be sure to select the item you want this email to be associated with.

Image of the general panel in Custom Email settings

In the Trigger panel, select Product Purchase as the email trigger, then add the product(s) in the Product field. If you wish to disable the contribution Received email, toggle on, Disable confirmation email.

Image of the Trigger panel in Custom Email settings

The Email Panel is where you create your custom email responder. It would be best to keep the value of the To: field as [[bill_email]]. This ensures the billing address is used when sending this email notification. Alternatively, you could have this email sent to a specific individual on your team or to an email address entered by the supporter into a custom field (perhaps a friend's email).

Image of the email panel in the custom email settings

In the email body, you can use Merge Tags to refer to the custom fields. Use the Merge Tag Cheat Sheet to help you identify which Merge Tags are available to you. Because this is a product-specific email, you have access to the Merge Tags under the 'Specific Product is Purchased' section.


How do I know what Merge Tag to use for custom fields?

Pay close attention to the SEQUENCE of your custom fields. This is how you will identify which Merge Tag to use in your email. Custom field merge tags are referenced as [[custom_field_xx]] where xx represents the sequence of your custom field.

If the first custom field in your product setup is 'Registrant Name,' then you'd refer to that custom field by using [[custom_field_01]].

The sequence must be referenced as two digits. If the sequence is less than 10, you need the preceding 0.

[[custom_field_01]] - Right
[[custom_field_12]] - Right
[[custom_field1]] - Wrong (missing the _ and the preceding 0)
[[custom_field_8]] - Wrong (missing the preceding 0)

Did this answer your question?