Boost recurring donations this giving season with the new upsell prompt!Learn How >>

Admin donation confirmation email merge fields

updated

In Soapbox Donations, you have the ability to create and automatically send a confirmation email to administrators and staff. This email is distinct from that sent to the donor, though staff can be cc'd or bcc'd on that email as well. In this email, you can include a number of variables, or merge fields, related to the payment, including admin-only variables not available for the donor version of the email.

Admin-only Variables:

  • {CreditCardExpMonth}: Expiration month of credit card shown as MM
    Available for payments processed by Authorize.net, Braintree not using hosted fields, CyberSource, iATS, or PayPal Website Payments Pro
    Not available for payments processed by TouchNet, PayPal Standard, or Braintree when hosted fields are enabled
  • {CreditCardExpYear}: Expiration year of credit card shown as YYYY
    Available for payments processed by Authorize.net, Braintree not using hosted fields, CyberSource, iATS, or PayPal Website Payments Pro
    Not available for payments processed by TouchNet, PayPal Standard, or Braintree when hosted fields are enabled
  • {CreditCardLastFourDigits}: Last four digits of credit card shown as XXXX
    Available for payments processed by Authorize.net, Braintree not using hosted fields, CyberSource, iATS, or PayPal Website Payments Pro
    Not available for payments processed by TouchNet, PayPal Standard, or Braintree when hosted fields are enabled
  • {DonationsFormId}: Id of Donation form used to process payment
    Available for all payments
  • {DonationsFormTitle}: Title of Donation form used to process payment
    Available for all payments
  • {DonationsTransactionId}: Soapbox Donation Transaction Id shown in right column of Donations > Transactions
    Available for all payments
  • {SalesforceLeadId}: Salesforce Record Id for Lead created for transaction
    Available for payments processed by Authorize.net, Braintree, CyberSource, iATS, or PayPal Website Payments Pro when Salesforce integration is enabled
    Not available for payments processed by TouchNet or PayPal Standard
  • {SubscriptionId}: Subscription Id for assigned by payment processor monthly donation
    Available for initial monthly payments processed by Authorize.net, Braintree, CyberSource, iATS, or PayPal Website Payments Pro
    Not available for initial monthly payments processed by TouchNet or PayPal Standard and does not apply to one-time payments with any processor
  • {TransactionId}: Transaction Id assigned by payment processor for transaction
    Available for one-time payments processed by Authorize.net, Braintree, CyberSource, iATS, or PayPal Website Payments Pro and initial monthly payments processed by Braintree or iATS
    Not available for one-time payments processed by TouchNet or PayPal Standard or initial monthly payments processed by Authorize.net, CyberSource, or PayPal Websites Payments Pro

Contact Information variables:

  • {name}: Full name from Contact Information section
  • {DonorFirstName}: First name only
  • {DonorLastName}: Last name only
  • {DonorEmailAddress}
  • {DonorPhone}
  • {DonorOrganization}
  • {CustomField1}
  • {CustomField2}
  • {CustomField3}
  • {CustomField4}
  • {AnonymousDonation}: “Yes” or “No”
  • {NewsletterSignUp}: “Yes” or “No”
  • Salesforce fields used as custom fields in the Contact Information section can be used as merge fields. The format for these variables is {$StandardFieldName} or {CustomFieldName__c}. The Salesforce field name can be referenced in the Element column of the Custom Salesforce Fields section of the Contact Information tab of the Donation form.
  • Microsoft fields used as custom fields in the Contact Information section can be used as merge fields. The format for these variables is {$msftprefix_fieldname}. The Microsoft field name can be referenced in the Element column of the Custom Microsoft Fundraising & Engagement Fieldssection of the Contact Information tab of the Donation form.

Payment Amount variables:

  • {amount}: Transaction amount; does not include currency symbol
  • {frequency}: “one-time” or “monthly”

Dedication variables:

  • {TributeType}: “in honor of” or “in memory of”
  • {TributeNotificationType}: “No notification,” “Notify by email,” or “Notify by mail”
  • {TributeName}
  • {TributeNotificationFirstName}
  • {TributeNotificationLastName}
  • {TributeNotificationEmail}
  • {TributeNotificationMailingAddress}
  • {TributeNotificationMailingCity}
  • {TributeNotificationMailingState}
  • {TributeNotificationMailingZipCode}
  • {TributeNotificationMailingCountry}
  • {TributeNotificationMessage}

Billing variables:

  • {BillingFirstName}
  • {BillingLastName}
  • {BillingStreetAddress}
  • {BillingCity}
  • {BillingState}
  • {BillingPostalCode}
  • {BillingCountry}

General variables:

  • {campaign}: The name of the Campaign associated with the donation, either from the Salesforce Campaign being selected by the admin or chosen by the donor OR the Microsoft Campaign selected by the admin
  • {description}: Transaction Description set in form
  • {designation}: The name of the Microsoft Fundraising & Engagement Designation chosen by the donor on a Donation page where Donor Chosen Designation is set to Yes. If the Designation name has been customized in the administrator, the customized name will be displayed rather than the name as it is in Microsoft Fundraising & Engagement.
  • {TODAY}: Must be capitalized; renders in the format MM/DD/YYYY
  • {NOW}: Must be capitalized; renders in the format MM/DD/YYYY
  • {TOMORROW}: Must be capitalized; renders in the format MM/DD/YYYY
  • {YESTERDAY}: Must be capitalized; renders in the format MM/DD/YYYY
Have more questions? Submit a request
Article is closed for comments.