Personalisation Tags

20 Feb 2026

Entrants: Personalization Tags Glossary

Personalization tags make it easy to add that personal touch to your emails, pages, and messages—without needing to update each one by hand.

They pull in real supporter or campaign details (like someone’s name, fundraising total, or event date) automatically, so every message feels tailored and relevant.

In this guide, you’ll see where tags can be used across your Funraisin platform, the different types available, and what each one does.

Jump to:

What Are Personalization Tags?

Personalization tags are short pieces of dynamic text that automatically pull information—like a supporter’s name, fundraising total, or campaign details—into your emails, messages, or page content. They help you create more personal, relevant communications without needing to edit each message manually.

For example, adding {member_firstname} to an email greeting will automatically display the fundraiser's first name when the message is sent.

Where Can Personalization Tags Be Used?

Personalization tags can be added across multiple areas of the Funraisin platform to pull in dynamic content automatically.

You can use them in:

  • Messages (Emails)
    • Transactional
    • Engagement
    • Trigger
    • Fundraiser
  • Webform confirmation pages and emails
  • Default social sharing content
  • Donation confirmation pages
  • Donation Reminders
  • Sticky Profile Bars
  • Receipts

When using PURLs, personalization tags can also be added to content and donation pages for an even more customized supporter experience.

Tip! For more on Personalized URLs, see our support article on PURLs.

Personalization Tag Fallbacks

Personalization tag fallbacks allow you to define default text that displays when a tag does not have data available.

Without a fallback, if a tag such as cannot pull data, it will either appear blank or display in tag format. This can result in incomplete messaging, for example:

  • Hi , thank you for your donation.

Fallbacks help prevent this by inserting a default value when the expected data is missing.

How fallbacks work

Fallback text is added directly inside the personalization tag using the following format: {tag_name[fallback=DefaultText]}

For example: {d_fname[fallback=Friend]}

If the donor’s first name is available, the message will display:

  • Hi John, thank you for your donation.

If the donor’s first name is not available, the message will display:

  • Hi Friend, thank you for your donation.

This ensures your communication remains complete and professional, even when certain data fields are missing.

Supported Tags

Fallback functionality is currently available for the following personalization tags:

  • {d_fname}
  • {d_lname}
  • {d_amount}
  • {dh1_amount}
  • {dh2_amount}
  • {dh3_amount}
  • {dh4_amount}
  • {custom_1}
  • {custom_2}

Watch out: Fallbacks are currently supported in Messages and content pages.

Why use fallbacks?

Using fallbacks provides:

  • More consistent and professional communications
  • Reduced risk of blank greetings or incomplete sentences
  • Greater control over how messages appear when supporter data is missing

Types Of Personalization Tags

Personalization tags are grouped into nine main types, each designed to pull data from different areas of your platform:

  • Fundraiser/Entrant — pulls information related to the individual participant
  • Team — pulls data for a team or group fundraiser
  • Organization — pulls information related to an organization and its organization captain
  • Invite — pulls details for both the person sending and receiving an invitation
  • Event — pulls details about the event or campaign they’re part of
  • Donation — pulls information connected to a specific donation
  • Shop — pulls details related to merchandise or purchases made through your shop
  • eCards — pulls details for digital card donations, including sender, recipient, and message information
  • Platform — pulls site-wide details, such as your platform name and URLs

Below is a complete list of available personalization tags by type.

Fundraiser/Entrant Tags

Tag

Description

Example

{member_id}

Unique ID used by the platform to identify a participant. Can also serve as their participant number in communications or reports

2213

{member_hash}

Unique identifier used for secure actions such as PURLs and password resets. Combine your base URL and reset path with this tag to generate a link—for example: https://yoursite.org/login/resetpassword/{member_hash}

14e044bcebd98e9417e94e33b1486288

{member_fullname}

Participant's full name (combines first and last name; excludes any last name prefix)

Jane Beek

{member_firstname}

Participant's first name

Jane

{member_lastname}

Participant's last name

Beek

{m_name_prefix}

Participant's last name prefix (if applicable)

van der

{member_password}

Participant's password in plain text. Only available in the initial registration confirmation email. For security reasons, not recommended elsewhere

password123

{member_username}

Fundraiser's unique username or slug within the platform. Can be added to URLs to link directly to their profile page—for example: https://yoursite.org/fundraisers/{member_username}. Can also be used in UTM parameters or campaign tracking

janebeek

{member_email}

Participant's email address

janevanderbeek@email.com

{member_amount_raised}

Total amount raised by the fundraiser, calculated from all donations to their page

523

{member_amount_raised_local}

Total amount raised by the fundraiser in local currency, calculated from all donations to their page

530

{member_amount_to_go}

Remaining amount needed for the fundraiser to reach their goal

477

{member_amount_to_go_local}

Remaining amount needed for the fundraiser to reach their goal, shown in local currency

490

{member_target}

Fundraising target set by the participant, or the default/minimum target if none was set

1000

{member_target_local}

Fundraising target set by the participant, or the default/minimum target if none was set, shown in local currency

1100

{member_url}

Participant's fundraising page URL

https://yoursite.org/fundraisers/janebeek

{member_invite_url}

(Teams only) Invite link to the participant's team (excludes multi-entry invites)

https://yoursite.org/join/janesteam

{member_short_url}

Shortened URL for the fundraiser’s page

https://yoursite.org/s/2213

{member_short_url_sms}

Shortened, trackable URL for the fundraiser’s page—used for SMS shares

https://yoursite.org/s/2213?sms

{member_short_url_twitter}

Shortened, trackable URL for the fundraiser’s page—used for Twitter shares

https://yoursite.org/s/2213?twitter

{member_short_url_email}

Shortened, trackable URL for the fundraiser’s page—used for email shares

https://yoursite.org/s/2213?email

{member_short_url_facebook}

Shortened, trackable URL for the fundraiser’s page—used for Facebook shares

https://yoursite.org/s/2213?facebook

{member_short_url_linkedin}

Shortened, trackable URL for the fundraiser’s page—used for LinkedIn shares

https://yoursite.org/s/2213?linkedin

{member_qrcode}

URL used to generate the participant's QR code for event check-in

https://yoursite.org/fundraisin/generateqrcode/2126

{member_waves}

Participant's assigned event wave, such as their start time

6:00 AM

Team Tags

Tag

Description

Example

{team_id}

Unique ID used by the platform to identify a team. Can also be used as a team number in communications

133

{team_name}

Team name

Jane’s Team

{team_url}

URL of the team fundraising page

https://yoursite.org/fundraisers/janesteam

{team_join_url}

Public join link to the entrant’s team (excludes multi-entry invites)

https://yoursite.org/join/janesteam

{team_amount_raised}

Total amount of donations made to the team

223

{team_amount_raised_local}

Total amount of donations made to the team in local currency

256

{member_invite_url}

Invite link to a team from a member (multi-entry and unique to the invited member)

https://yoursite.org/invite/janesteam

{team_short_url}

Shortened URL for the team fundraising page

https://yoursite.org/s/223

{team_short_url_sms}

Shortened, trackable URL for the team’s fundraising page—used for SMS shares

https://yoursite.org/s/223?sms

{team_short_url_email}

Shortened, trackable URL for the team’s fundraising page—used for email shares

https://yoursite.org/s/223?email

{team_short_url_facebook}

Shortened, trackable URL for the team’s fundraising page—used for Facebook shares

https://yoursite.org/s/223?facebook

{team_short_url_twitter}

Shortened, trackable URL for the team’s fundraising page—used for Twitter shares

https://yoursite.org/s/223?twitter

{team_short_url_linkedin}

Shortened, trackable URL for the team’s fundraising page—used for LinkedIn shares

https://yoursite.org/s/223?linkedin

{invited_members}

List of all invited members to the team

John, Susan, Steve, Rachel

{paid_invited_members}

List of all invited members paid for by the team captain

John, Rachel

{team_amount_to_go}

Remaining amount required to reach the team’s fundraising goal

540

{team_amount_to_go_local}

Remaining amount required to reach the team’s fundraising goal in local currency

576

{team_target}

Team’s fundraising target or the default/minimum team target

3000

{team_target_local}

Team’s fundraising target or the default/minimum team target in local currency

3500

{captain_firstname}

Team captain’s first name

Jane

{captain_lastname}

Team captain’s last name

Beek

{captain_fullname}

Team captain’s full name (first and last name)

Jane Beek

{captain_email}

Team captain’s email address

janevanderbeek@email.com

{captain_url}

URL of the team captain’s fundraising page

https://yoursite.org/fundraisers/janebeek

Organization Tags

Tag

Description

Example

{org_key}

Unique ID used by the platform to identify an organization

4567

{org_name}

Organization name

Peterson Financial

{org_url}

URL of the organization’s fundraising page

https://yoursite.org/organisations/petersonfinancial

{org_goal}

Fundraising goal or target amount set for the organization

5000

{org_join_url}

URL supporters can use to join the organization

https://yoursite.org/join/petersonfinancial

{org_short_url}

Shortened URL linking directly to the organization’s page

https://yoursite.org/s/4567

{org_short_url_sms}

Shortened, trackable URL for the organization’s page—used for SMS shares

https://yoursite.org/s/4567?sms

{org_short_url_email}

Shortened, trackable URL for the organization’s page—used for email shares

https://yoursite.org/s/4567?email

{org_short_url_twitter}

Shortened, trackable URL for the organization’s page—used for Twitter shares

https://yoursite.org/s/4567?twitter

{org_short_url_facebook}

Shortened, trackable URL for the organization’s page—used for Facebook shares

https://yoursite.org/s/4567?facebook

{org_amount_raised}

Total amount raised by the organization from all donations

3275

{orgcaptain_fullname}

Organization captain’s full name (first and last name)

Sam Lee

{orgcaptain_name}

Same as {orgcaptain_fullname}—shows the organization captain’s full name

Sam Lee

{orgcaptain_email}

Email address of the organization captain

sam.lee@email.com

{orgcaptain_firstname}

Organization captain’s first name

Sam

{orgcaptain_lastname}

Organization captain’s last name

Lee

{orgcaptain_username}

Organization captain’s username (slug), which can be used in URLs or for tracking

samlee

{orgcaptain_url}

URL of the organization captain’s profile page

https://yoursite.org/fundraisers/samlee

Invite Tags

Tag

Description

Example

{invitor_m_fname}

First name of the person sending the invite

John

{invitor_m_lname}

Last name of the person sending the invite

Smith

{invitor_m_email}

Email address of the person sending the invite

john@email.com

{invitee_fname}

First name of the person receiving the invite

Jane

{invitee_lname}

Last name of the person receiving the invite

Doe

{invitee_email}

Email address of the person receiving the invite

jane@email.com

{event_name}

Name of the event the invite relates to

Charity Fun Run

Event Tags

Tag

Description

Example

{event_id}

Unique ID used by the platform to identify an event

133

{event_name}

Event name

Charity Fun Run

{event_goal}

Fundraising goal set for the event in the Events module

1,000,000

{event_date}

Date of the event

2025-05-25

{event_raised}

Total amount raised across the entire event

597,232

{event_key}

Unique event key used by the platform for system reference and integrations

Funrun-2025

{event_code}

Code assigned to the event, primarily used for reporting

Funrun-25

{event_contact_number}

Contact phone number set for the event

0412 345 678

{event_contact_email}

Contact email address for the event

Funrun@yoursite.org

{event_contact_name}

Primary contact name for the event

Judy Smith

{event_company_name}

Company or organization associated with the event, primarily used for multi-charity setups

Your Charity

{event_company_abn}

Business registration number (ABN) for the event

123-456-789

{number_tickets}

Offline events only: The total number of tickets a user has purchased

5

Donation Tags

Tag

Description

Example

{donation_id}

Unique ID used by the platform to identify a specific donation

98765

{donation_hash}

Unique hash identifier for the donation, used for secure links or verification

a84f92bc67e1452f

{sponsor_amount}

Donation amount made by the sponsor (excluding currency symbol)

50

{sponsor_name}

Name entered by the donor during the donation process (may include nickname or display name)

Nan and Pop Smith

{sponsor_name_actual}

Actual name of the donor as recorded in the platform

John Smith

{sponsor_email}

Email address of the donor

johnsmith@email.com

{sponsor_phone}

Phone number of the donor (if collected)

0421 345 543

{captain_fullname}

Full name of the team or organization captain connected to the donation

Jane Beek

{captain_firstname}

First name of the team or organization captain

Jane

{captain_lastname}

Last name of the team or organization captain

Beek

{captain_email}

Email address of the team or organization captain

jane.beek@email.com

{captain_username}

Username (slug) of the team or organization captain

janebeek

{captain_url}

URL of the team or organization captain’s fundraising page

https://yoursite.org/fundraisers/janebeek

{d_amount}

Donation amount

55

{donated_to_name}

Name of the fundraiser, team, or organization that received the donation

Run for Change

{donated_to_url}

URL of the fundraiser, team, or organization donation page

https://yoursite.org/fundraisers/runforchange

{donation_frequency}

Frequency of the donation (e.g., once, monthly, annual)

Monthly

{d_amount_local}

Donation amount shown in local currency

75

{d_currency}

Currency of the donation

AUD

{date_paid}

Date the donation was processed

2025-05-22

{donation_type}

Indicates how the donation was made (e.g., online, offline, matched, recurring)

Online

Shop Tags

Tag

Description

Example

{first_name}

First name of the purchaser

John

{last_name}

Last name of the purchaser

Smith

{email}

Email address of the purchaser

john@email.com

{shipped_tracking}

Tracking code added from an external source when shipping products

abc-1234567

{tax_ref}

Gateway reference number for the transaction

py_1EoatnHsQNJrSk7y5123D56E43

{po_number}

Purchase order number for the transaction

SHP-123456

{total}

Total price of the purchase

25.59

eCard (Shop) Tags

Tag

Description

Example

{first_name}

Sender or purchaser’s first name

John

{last_name}

Sender or purchaser’s last name

Smith

{email}

Sender or purchaser’s email address

john@email.com

{download_link}

Link to download the purchased eCard

https://yoursite.org/download/ecard123

{product_price}

Donation amount or Price of the purchased eCard

10

{recipient_first_name}

Recipient’s first name

Jane

{recipient_last_name}

Recipient’s last name

Doe

{recipient_email}

Recipient’s email address

jane@email.com

{recipient_comments}

Message written on the eCard by the sender

Happy Birthday! Hope you have a great day!

eCard (Donation form) Tags

Tag

Description

Example

{donor_first_name}

Donors first name

John

{donor_last_name}

Donor’s last name

Smith

{honouree_name}

First name of the person whom the gift is in memory/celebration of.

Cooper

{recipient_first_name}

Recipient’s first name

Jane

{recipient_last_name}

Recipient’s last name

Doe

{recipient_message}

Message written on the eCard by the sender

Happy Birthday! Hope you have a great day!

Platform Tags

Tag

Description

Example

{siteurl}

Base URL of your platform

https://yoursite.org

{secureurl}

Secure (SSL) version of your site URL, used for checkout or login pages

https://secure.yoursite.org

{charity_name}

Name of the charity or organization set in platform settings

Your Charity

Still need help? Check out our other Supporter Care articles or reach out to the Funraisin Support team by logging a ticket through the Support Module in your platform.

Last updated: 20 Feb 2026