Supporter Tags, Custom Questions, and Custom Fields Training Video

This training covers three powerful tools in WeGive for organizing, segmenting, and personalizing your supporter data: Supporter Tags, Custom Questions, and Custom Fields.

Whether you're looking to improve your donor segmentation, gather richer supporter data, or automate your engagement workflows, this is a great starting point.

Supporter Tags

Tags let you create groups of supporters for segmentation, reporting, and targeted communication. Tags can be applied manually or automatically based on rules you define.

How to Create a Tag

1. Go to the Data tab and select Supporter Tags.

2. Click the + button to create a new tag.

3. Name your tag (this is internal and should reflect its purpose).

4. Add Rule Groups to define entry rules that automatically tag supporters.

Entry Rule Options

You can build rules based on a wide range of supporter attributes:

• Supporter Info — Name, Email, Phone, Existing Tags, Profile Created Date, Last Login

• Payment & Giving — Total Donated, Number of Donations, Campaigns Given To, Designations

• Recurring Donations — Recurring donation status and details

• Fundraising — Fundraiser Name, Goal, Total Raised

• Event Registrations — Event registration details

• Journey & Messaging — Associated Journeys, Communication Lists, Messages Sent

• Transactional Activity — Last Checkout Date, Drop-off Step, Custom Field Data

• Household & Personal Details — Address, Birthday, Anniversary, Marketing Contact status

• Communication Preferences — Subscription status across Communication Lists

Rule groups support AND/OR logic, so you can combine multiple conditions to precisely define who should be tagged.

Tag Settings

• Remove donors when they no longer match the rules — When toggled on, supporters are automatically removed from the tag if they stop matching the entry rules. When off, supporters stay tagged even if their data changes (one-way tagging).

• Static tags — A static tag evaluates its rules once and doesn't re-process after the initial tagging. This is useful for one-time segmentation snapshots.

Manual Tagging

You can also manually add or remove tags from individual supporter records or in bulk from Table Views.

Custom Questions

Custom Questions let you collect specific answers from supporters during checkout, registration, or form submission. Answers can optionally be saved to supporter or transaction records for future use.

Where Custom Questions Can Be Placed

• Donation Checkouts

• Event Registrations

• Pledge Creates

• Forms

Available Question Types

Custom Questions support 11 input types:

Question Settings

• Required — Mark a question as mandatory so supporters must answer before submitting.

• Character Limit — Set a maximum character count for text inputs.

• Answer Options — For Dropdown, Checkbox, and Multiple Select types, define the list of options supporters can choose from.

• Conditional Logic — Show or hide a question based on the answer to a previous question. For example, only show "Which campus?" if the supporter selects "Yes" for "Do you attend in person?"

Where Answers Are Saved

Custom Question answers can be saved to three destinations:

1. Donor Record — The answer is stored on the supporter's profile. You can map it to a standard donor field (like Name, Email, Phone, Birthday, etc.) or to a Custom Field for structured data storage.

2. Transaction Record — The answer is attached to the specific transaction only.

3. Communication List — For checkbox or toggle questions, the answer can subscribe or unsubscribe the supporter from a Communication List.

Answers are viewable on the element itself (checkout, event, form, or pledge) under the Related tab, and on the supporter record when saved to donor.

Donor Field Mapping

When saving to a donor record, you can map answers directly to standard fields including: Full Name, First Name, Last Name, Email (Primary, Work, Alternate), Phone (Mobile, Work, Home, Alternate), Birthday, Anniversary, Gender, Mailing Address, Billing Address, and communication preferences (Do Not Contact, Do Not Email, Do Not Text, Do Not Mail, Marketing Communication, etc.).

Custom Fields

Custom Fields let you store additional structured data on records beyond the standard fields WeGive provides. They are useful for segmentation, reporting, CRM syncing, and message personalization.

Custom Fields can be applied to: Donors, Transactions, Households, Recurring Donations, Event Registrations, Campaigns, Events, Fundraisers, Pledges, Campaign Fundraisers, and Funds.

Two Types of Custom Fields

Static Fields

• Store manually-entered or imported data that doesn't change automatically.

• Good for: donor preferences, membership tiers, volunteer interests, categories.

• Values stay constant until manually updated or overwritten by an import/integration sync.

Computed Fields

• Automatically calculate values based on existing data in WeGive.

• Update in real time as underlying data changes.

• Examples: total donations to a specific campaign, date of last gift, gift count, average gift size.

• Aggregation options include: Sum, Count, Average, Min, Max, Exists, and Does Not Exist.

Custom Field Settings

• Name — The human-readable label for the field.

• Model — What record type the field applies to (Donor, Transaction, Household, Recurring Donation, Event Registration, Campaign, Event, Fundraiser, Pledge, Campaign Fundraiser, or Fund).

• Configuration — Determines the input type for static fields or the aggregation logic for computed fields.

• Default Value — A fallback value when no data is present.

• Formatting — Optional prefix, suffix, and decimal precision for display (e.g., "$" prefix with 2 decimal places for currency).

Where Custom Fields Appear

• Supporter Records — Viewable and editable on the supporter profile.

• Filters & Segmentation — Use custom field values to filter supporters or build tag rules.

• CRM Integrations — Custom fields sync to external CRMs (like Salesforce) using the API name format CF_{id}_{field_name}.

• Message Personalization — Use custom field values as merge tags in emails and messages.

• Exports — Custom field values are included in data exports.

How These Features Work Together

These three tools are designed to complement each other:

1. Custom Questions collect data from supporters at the point of interaction (checkout, event, form).

2. Custom Fields store that data (and more) in a structured way on supporter records — either from question answers, CRM syncs, or computed calculations.

3. Supporter Tags use all of this data — including custom field values — to automatically segment supporters into meaningful groups.

For example, you could add a Custom Question to your checkout asking "Which program are you supporting?" with the answer saved to a Custom Field. Then create a Supporter Tag with a rule that automatically tags anyone whose Custom Field value matches a specific program — and use that tag to send targeted communications via Journeys.

Related Features

• Journeys — Automate actions (like tagging or sending messages) when supporters meet certain criteria.

• Communication Lists — Manage subscriber lists that can be synced with tags.

• Exports — Export custom question answers, custom field data, and tag-based segments for reporting.