In Big River emails, merge fields can be referenced using braces or braces preceded with a pound sign (i.e. {DATE} or #{DATE}). The following is a list of merge fields available for use in emails and their purpose.


Transaction Merge Fields


#{DATE}

The date merge field can be used for any email related to a transaction - typically a receipt email. This field will be replaced with the current date formatted as [Full month name] [Two digit date], [4 digit year] [2 digit hour]:[2 digit minute]:[2 digit second] [AM/PM] [Timezone]. For example, August 08, 2015 08:45:24 AM EDT.


#{CONTACT}

The contact field can be used for any email related to a transaction. This field is replaced with a table (formatted in HTML) containing information for the transaction's contact as entered into the form: Full name, Full address, Country (if provided), and phone number.


#{ORDER}

(Deprecated - use ORDERTABLE) The order field can be used for any email related to a transaction. This field is replaced with a table (formatted in HTML) containing information about items in the transaction. This works well as a receipt list of items purchased in the order (such as donation items, tickets, etc.)


#{ORDERTABLE}

The order table field can be used for any email related to a transaction. This field is replaced with a more consistently formatted table (formatted in HTML) containing information about items in the transaction. The order table includes the items purchased, quantities of items purchased, amount spent on each item, subtotal of transaction, any fees on the transaction, and total of the transaction.


#{PAYMENT}

The payment field can be used for any email related to a transaction. This field is replaced with a table (formatted in HTML) containing information about the payment method used on the transaction. This typically is a confirmation message from a payment method or information about how the payment will be processed (i.e. Your card will be charged by "BIG RIVER")


#{UPDATEFORMTAG}

The update form tag can be used for any email related to a transaction. The field is replaced with an HTML anchor link that takes the user to a form for updating their transaction.


#{SOCIAL}

The social tag is used to insert social media sharing tags for email, Facebook, Twitter, and Google+. These are formatted as icons using HTML and share the page the transaction is linked to.


Page Merge Fields


#{REFERRALURL}

The referral url is replaced by the url for the donation form of any page. It also includes the contact ID of the current user to track referrals.


#{CAMPAIGNFORM}

The Campaign Form tag is replaced by the url for the campaign's donation form, just as referral URL. However, this tag only works for Pages and not Team Fundraisers or Communities.


Team Fundraising / Community / Board Merge Fields


#{COMMUNITYDONATIONREFERRALURL}

This tag is the same as the #{REFERRALURL} tag, but will not work for normal Pages.


#{COMMUNITYTINYURL}

The tiny URL of the public community page in the form brurl.co/[code]


#{COMMUNITYLABEL}

This tag replaces the semantic label of your Community page (i.e. "Community", "Board", "Fundraiser", etc.) This semantic label is configurable for top tier users.


#{COMMUNITYTEAMSNUMBER}

This tag is replaced by the number of teams (or boards or individual initiatives) on a team fundraiser (or board page or Community page).


#{COMMUNITYDEADLINE}

This merge field is replaced by the date that is set as the Community's deadline (from the Community edit page.)


#{COMMUNITYNAME}

This merge field is replaced by the Community's name that is set by administrators on the the community edit page.


#{COMMUNITYGOAL}

This merge field is replaced by the monetary goal of the Community, as specified on the community edit page.


#{COMMUNITYINVITENEWLEADERSURL}

This merge field is replaced by the URL for inviting new team leaders (or initiative leaders or board members) to the Community. This includes the necessary parameter codes for users to join even an invite only campaign. This is typically included in the Community Participant Invitation email.


#{COMMUNITYINVITEPARTICIPANTSURL}

This merge field is similar to the one just above, but the URL includes the ability for participants to choose whether they would like to create a new team or join an existing team if team fundraising is enabled.


#{INVITEJOINURL}

This merge field is replaced with a URL for invitees to specifically join teams, not create them.


#{COMMUNITYTOTALRAISED}

This merge field is replaced with the current amount of money raised by the community.


#{TEAMLABEL}

This merge field is replaced by the semantic label for teams (i.e. "Initiative", "Team", "Board Member", etc.) The semantic label is configurable for top tier users.


#{TEAMNAME}

When an email is sent in the context of a team (or initiative or board member), this merge field is replaced with the team's name (as provided in the team edit/creation form.)


#{TEAMGOAL}

When an email is sent in the context of a team (or initiative or board member), this merge field is replaced with the team's monetary goal, as provided in the team creation/edit form.


#{TEAMTOTALRAISED}

When an email is sent in the context of a team (or initiative or board member), this merge field is replaced with the team's current amount of money raised.


#{TEAMREFERRALURL}

When an email is sent in the context of a team (or initiative or board member), this merge field is replaced with the public team page's URL. It also includes the current contact's id to capture referral information.


#{TEAMURL}

When an email is sent in the context of a team (or initiative or board member), this merge field is replaced with the public team page's URL.


#{TEAMTINYURL}

When an email is sent in the context of a team (or initiative or board member), this merge field is replaced with the public team page's tiny URL in the form brurl.co/[code].



User Merge Fields


#{USER}

When a logged in user sends an email, the merge field is replaced with the user's first + last name.


#{USERFIRSTNAME}

When a logged in user sends an email, the merge field is replaced with the user's first name.


#{USERLASTNAME}

When a logged in user sends an email, the merge field is replaced with the user's last name.


#{USEREMAIL}

When a logged in user sends an email, the merge field is replaced with the user's email address.


Account Merge Fields


#{ACCOUNTNAME}

The merge field is replaced with the Big River account's name from which the email is being sent.


Contact Merge Fields


#{CONTACT}

When available, this merge field is replaced with the first + last name of the contact to whom the email is being sent.


#{CONTACTFIRSTNAME}

When available, this merge field is replaced with the first name of the contact to whom the email is being sent.


#{CONTACTLASTNAME}

When available, this merge field is replaced with the last name of the contact to whom the email is being sent.