Using Custom Fields – Raisely

When looking to capture donor or fundraiser data through donation, signup, ticket, or lead forms, you may need to collect information beyond Raisely’s default fields. This guide explains how to create and use custom fields safely and effectively.

Skip Ahead To

Understanding data fields

Adding new custom fields

Using custom fields in your Campaigns forms

FAQ

⚠️ Never collect payment card details in custom fields

Credit or debit card numbers, expiry dates, CVC/CVV codes, and other payment credentials must only be entered through Raisely’s secure checkout. Do not request or store payment card details in visible, hidden, private, or free-text custom fields.

Raisely blocks credit-card-like numbers submitted through custom fields. If a form contains a card-like value, the submission may be rejected. Values already stored in custom fields that are detected as card-like will also be removed as part of this security control.

Long membership, licence, or clearance numbers may sometimes resemble payment card numbers. Avoid card-like formats where possible and test your form before publishing it.

Understanding data fields

Data in Raisely is structured in categories, allowing you more flexibility to create fields. The five categories that are available for custom fields include:

Donation: data fields based on donors and donations. These fields are available within Donation forms
Person: these data fields are the primary user information found in the Raisely Supporter Management Tool
Profile: data fields that relate to fundraisers profiles, for when they signup to Peer to Peer campaigns
Tickets: data captured within the Ticketing form
Interactions: data fields used when recording interactions in Raisely Supporter Management Tool

Data fields have a range of formatting options or types available, from text to dates and more. Here is a brief description of each:

Field Types

Field Type	Description
Text	This is a standard text-entry field for short responses, usually one or two words. Text fields must not be used to collect payment card details. Credit-card-like numbers may be rejected.
Textarea	Like the Text field, but designed for longer responses. Textarea fields must not be used to collect payment card details. Credit-card-like numbers included in a response may cause the submission to be rejected.
HTML	This is an advanced field that lets your users enter their own HTML code.
Email	A text-entry field that checks the user's submission to make sure it includes an @ symbol and .xxx suffix, and to make sure it doesn't contain any spaces.
Number	This is a numeric-entry field that accepts numbers, periods, and the letter e. It can be used for information such as quantities or numerical identifiers, but it must not be used to collect payment card details. Long numbers that resemble credit card numbers may be rejected.
Phone Number	This is an integer-entry field that lets the user select their country and enter their phone number.
Date	This is an integer-entry field that lets the user enter a date numerically or select a date from a calendar. Dates are formatted DD/MM/YYYY by default.
Checkbox	This field asks the user a yes/no question and returns a value of true (if the user ticked the box) or false (if the user left the box unticked) in your reports.
Select Items	This dropdown field lets users choose one of several options.
Country Select	This dropdown field lets the user select one of 300+ countries.
Currency Select	This dropdown field lets the user select one of 130+ currencies.
Currency	This is an integer-entry field that lets the user enter numbers, periods, and the letter e, and it is prefixed with the currency symbol of the organisation-selected currency.
File Upload	This field asks the user to upload a file.
Image Upload	Image file upload with accepted file types including BMP, JPG, PNG, and TIFF, and the file must be 20MB or smaller.
Exercise Goal	Numeric exercise goal field.
Address Lookup	This dynamic field uses Google to search for a user's address as they type.
Heading	This static field helps visually segment your form and keeps it looking clean.
Description	This static, multi-purpose field is used to provide additional information for form guidance.

See FAQs below for details on specific uses.

Data within Raisely can also be captured in the background using Hidden Fields. These fields allow you to submit information that the user does not see. They are particularly useful when inserting data stored in a URL query string; see the Personalisation guide for more information.

Hidden fields are subject to the same payment-card protection as visible fields. Do not pass card numbers or other payment credentials through hidden fields, URL parameters, pre-filled values, integrations, or custom components.

All fields can be set as Private or Public. Private fields restrict access to their values and are masked in parts of Raisely to provide additional protection. Fields are private by default.

A field’s privacy setting does not make it suitable for storing payment card information. Never collect card numbers, expiry dates, CVC/CVV codes, or other payment credentials in a custom field, even when the field is private or masked.

For more information on how Raisely’s data is structured, check out the Understanding Your Data guide.

Adding new custom fields

Custom fields are global, entered in through your Organisation settings. This enables all your custom fields to then be used across any campaign when needed. To note, it is a good idea to have a clear picture of the data you wish to capture for all your campaigns before you start adding custom fields. Managing your data in a structured way will have great benefits for donor and fundraiser engagement.

Before creating a field, confirm that the information is appropriate to store as custom data. If the information is needed to process a payment, use Raisely’s secure checkout instead of creating a custom field. Do not create fields such as “Credit Card Number,” “Card Expiry,” or “CVC.”

To add a new custom field:

From the sidebar select Organisation > Custom Fields.
Using the Tabs, select the data category you wish to place the field, then scroll down to select Add New.
Enter your Fields Name, which is the label presented on your form.
The Field ID is then generated based on the Name. It is a good idea to have a simple naming convention you use for your Field IDs so that your data is clean and easy to manage and use.

Field IDs are an unseparated value, and you can use - or _ to separate words.

Example: If your donation custom field name is Opt In for Marketing then you could rename your Field ID to donation_optIn.
Select your Field Type from the dropdown. Choose a type appropriate for the information you need to collect, and do not use any field type to request payment card details.
You can Disable your custom field at any time if needed.
You can change your security setting at any stage if needed.
Use default value if this field has a common value used across all campaigns. Otherwise leave blank. You can add default values within specific campaigns.
Add a placeholder if this guidance is needed for the field.
Add info text is this guidance is needed for the field.
If the field needs additional validation, you can use a regular expression to validate its input. This can help enforce a required format or reduce spam. Check out regexr.com to learn more about regular expressions. Custom validation cannot override Raisely’s payment-card protection. A value identified as credit-card-like may still be rejected even if it passes your regular expression.
Select Save to finish.

Your field is now available across all your campaigns to use.

Using custom fields in your campaigns forms

To use custom fields, add them to your Donation, Signup, Ticket, or Lead Form settings. The restriction on payment card details applies across all these forms, including visible, hidden, private, pre-filled, and conditionally displayed fields.

Adding a custom field into your campaigns Donation and Signup form

Within your campaign, from the sidebar select Settings > Donation Form OR Signup Form.
If using the Donation Form, select Fields in the tabs.
Select Add New (either for Visible/Hidden) then click the Field dropdown to present your field options. Here you will find the relevant custom fields you have created.

Note: the Donation Form will only provide you options for custom fields created in the Donation category. The Signup Form will provide you with both the Personal Information (i.e. Person) or Profile categories.
If field is required changes switcher to Yes.
You have the option to change the field label, placeholder, default value, and help text if needed for this specific form. This will override your custom fields global settings just for this campaigns form.
You can then add field conditions if you wish to control when the field is shown. This is a helpful step to simplify the user experience.
Select Save to finish.

Adding a custom field into your campaigns Ticket form

Within your campaign, from the sidebar select Tickets > Setup Tickets then select the Attendee Fields tab.
Select Add New and repeat the same steps as above (from Step 3) to add and customise custom field

Note: Ticketing uses the same Person fields as the Signup Form. To adjust these for Ticketing, simply update the fields within the Signup Form found in your campaign Settings from the sidebar.

Adding a custom field into your Campaigns Lead form

If using the Lead form block within the page builder, you can add new fields within the blocks settings. Since the lead form captures user data, the form uses the same fields as in the Signup Form. Therefore custom fields within the Person category can be used.

To add new fields into Lead form:

Within your Campaigns Pages, Add the Lead Form block to your page and then select the Settings icon.
The Lead Form defaults with basic information, so to change select Add Field within settings.
Continue to add all the fields needed for your Lead form, making sure they are in the right order as you are unable to swap and shift fields.

Note: if Lead Form doesn’t load, simply save your changes and refresh the browser.

FAQ

What HTML tags are available?

Due to security reasons, the following tags are usable in the HTML field type: 'div', 'p', 'img', 'pre', 'br', 'hr', 'b', 'i', 'em', 'strong', 'a', 'code', 'h1', 'h2', 'h3', 'h4', 'h5', 'h6', 'ul', 'ol', 'li', 'font', 'center', 'style', 'table', 'thead', 'tbody', 'tr', 'td'

How can I setup an Agree field, for Terms & Condition or Marketing Opt-In

The checkbox field type is commonly used to ask users to agree to an organisation's terms & conditions, or to ask users for permission to send them newsletters. Note: if this field is marked as Required, the user will be unable to progress in the form unless the box is ticked. This is useful for requiring agreement to T&Cs, for example.

If you want the checkbox to be ticked by default, enter true as the default value, otherwise leave as blank.

For the Select Field Type, what is the "value" & "label"?

Like the Field ID, the value is the information that will be shown on your reports and used to create conditions in your messages and form fields. This is an internal field that will only be seen by your organisation, and it's common to make this an abbreviated form of the public-facing label.

The label is the name of the option that your users will see. It's best to make this relatively short to prevent the dropdown options from looking awkwardly big.

Can I mix currencies in the Currency Field Type?

It is not possible to mix currencies here. Changing the currency on either the amount minimum or amount maximum fields will always change both fields.

How can I apply specific validation conditions to fields, such as character length or limit to specific formats?

Each Custom Field allows the option to apply a custom validation using regex expressions. With Custom Fields settings, simply expand the field you are editing and enter regex statement in custom validation.

For example, if you needed a text field to have a limit between 4-60 characters, you could use the following regex expression to apply this validation - ^[a-zA-Z0-9 ]{4,80}$ To learn more on how to create regex expressions you can use for your Custom Fields, search Google for Regex Generator tools. Do note, Raisely cannot provide support for regex expressions created.

Why was a form submission containing a long number rejected?

Raisely blocks credit-card-like numbers from being submitted through custom and free-text fields. This protects payment card data from being stored outside Raisely’s secure checkout.

A long membership, licence, or clearance number may occasionally resemble a payment card number. If a legitimate identifier is rejected, review whether it can use a clearly non-card-like format, such as including letters or separators. If you still experience an issue, contact Raisely Support with the field name and an explanation of the type of identifier being collected. Do not send the complete value to Support.

Can I collect card details in a private or hidden field?

No. Private and hidden fields must not be used to collect or store credit or debit card numbers, expiry dates, CVC/CVV codes, or other payment credentials. Card details must only be entered through Raisely’s secure checkout.

Making a field private, masked, hidden, or subject to custom validation does not make it appropriate for payment card information.

Cannot find the support guide you are after? Head on over to our YouTube channel 📺 for more creative content to help you go further. You can even leave us comments, suggesting new content ideas 🤯

Skip Ahead To

Understanding data fields

Adding new custom fields

To add a new custom field:

Using custom fields in your campaigns forms

To add new fields into Lead form:

FAQ

Related articles