The Data Fields Explained
Skip Ahead To
How Raisely captures data
Within Raisely, data fields are collected under the following categories/types:
- Donation/Transaction
Contains all the fields that capture data on the Donation Form, or where payment is captured e.g Ticket Form or Signup Form - User (Personal Information Field)
Contains all the fields related to a Person within the Raisely Supporter Management Tool. This differs from Profile fields as it is the data on the top-level data of the individual. Whenever anyone donates, fundraises, or submits a lead form with email address and name, they are created as a Person record within the Supporter Management Tool - Profile
Contains all the fields related to a fundraiser who signs up for a particular campaign. There are three levels of profile fields - Individual, Team and Organisation. When trying to understand what field to use, you can generate a Profile Report, which shows you the fields that are available to each level. The same fields are available on all levels, but with the addition of "team" or "organisation" added to the start of the field ID (e.g profile.goal / teamProfile.goal / organisationProfile.goal). - Campaign
Contains fields related to the Campaign itself, such as Campaign name and goal - Ticket
Contains all attendee fields that you capture with your ticket orders. These are all custom fields
When using this data, context/relationship is what enables fields to be accessible or not. A good example is receipts, as every receipt has a corresponding donation. If the data field has no relation to the context you are using it in, the field will not appear or will return no data.
Raisely also captures attribution data via UTM's and other unique viewer data. More information on attribution data can be found in our Capturing the Right Data guide.
The Data
Below you will find many of the data fields that Raisely captures, including field name, field ID, values, and description (where necessary).
### accordion
## expand
# Donation Fields
Field | Field ID | Description | Value |
Donation Total | donationTotal | Donation amount | numeric |
Order Total | orderTotal | Ticketing Order amount | numeric |
Transaction Amount refunded | amountRefunded | Donation amount refunded | numeric |
Donation Anonymous | anonymous | If donation is selected as 'anonymous' | true/false |
Donation Campaign amount | campaignAmount | The numerical value of the donation in the campaign currency (E.g. 36 USD = “55.57” AUD) | numeric |
Donation Campaign fee | campaignFee | The numerical value of the payment gateway’s processing fee + tax, in the payment gateway’s configured currency | numeric |
Transaction Created at | createdAt | Time stamp of donation | |
Transaction Currency | currency | Donation currency | currency abbrev. |
Transaction Currency symbol | cuurencySymbol | Donation currency symbol | symbol |
Transaction Date | date | Donation date | YYYY-MM-DD |
Transaction Email | Donation email provided | ||
Transaction Fee | fee | The numerical value of the optional tip in AUD | numeric |
Transaction Fee opt in | feeOptIn | Indicates if the donor opted in/out of the optional tip | true/false |
Transaction First name | firstName | Donors first name | text |
Transaction Full name | fullName | Donors full name | text |
Donation Gst | gst | GST applied to donation | numeric |
Tax Type | taxType | ||
Tax Rate | taxType | ||
Tax Total | taxTotal | ||
Donation Id | id | Unique donation ID | numeric |
Transaction Last name | lastName | Donors last name | text |
Donation Message | message | Optional message given with donation | text |
Transaction Method | method | Payment method used for donation | STRIPE_INTENT/PAYPAL |
Transaction Preferred name | preferredName | Donors preferred name | |
Transaction Processing | processing | Donation processing charge | numeric |
Transaction Status | status | Donation transaction status | OK |
Transaction Total | total | Donation Total (inc. fee and processing) | |
Transaction Updated at | updatedAt | ||
Transaction Phone Number | phoneNumber | Donors contact number | numeric |
Transaction Item Amount | itemAmount | ||
Transaction Item Campaign amount | itemCampaignAmount |
## expand
## expand
# User Fields
Field | Field ID | Description | Value |
User Address 1 | user.address1 | text | |
User Address 2 | user.address2 | text | |
User Country | user.country | text | |
User Created at | user.createdAt | YYYY-MM-DD | |
User Email | user.email | ||
User First name | user.firstName | text | |
User Full name | user.fullName | text | |
User Last name | user.lastName | text | |
User Phone number | user.phoneNumber | numeric | |
User Photo url | user.photoUrl | url | |
User Postcode | user.postcode | numeric | |
User Preferred name | user.preferredName | text | |
User State | user.state | text | |
User Status | user.status | ||
User Suburb | user.suburb | text | |
User Unsubscribed at | user.unsubscribedAt | YYYY-MM-DD | |
User Updated at | user.updatedAt | YYYY-MM-DD |
## expand
## expand
# Profile Fields
Field | Field ID | Description | Value |
Profile Activity total | profile.activityTotal | numeric | |
Profile Campaign total | profile.campaignTotal | numeric | |
Profile Created at | profile.createdAt | YYYY-MM-DD | |
Profile Currency | profile.currency | currency | |
Profile Description | profile.description | text | |
Profile Exercise goal | profile.exerciseGoal | numeric | |
Profile Goal | profile.goal | numeric | |
Profile Grand total | profile.grandTotal | numeric | |
Profile Is campaign profile | profile.isCampaignProfile | true/false | |
Profile Member count | profile.memberCount | numeric | |
Profile Name | profile.name | text | |
Profile Paid | profile.paid | ||
Profile Path | profile.path | text | |
Profile Photo url | profile.photoUrl | url | |
Profile Shared | profile.shared | ||
Profile Total | profile.total | numeric | |
Profile Type | profile.type | ||
Profile Updated at | profile.updatedAt | YYYY-MM-DD | |
Profile reg fee | profile.regFree | ||
Profile Cover Photo | profile.coverPhoto | ||
Profile User Address 1 | profile.user.address1 | text | |
Profile User Address 2 | profile.user.address2 | text | |
Profile User Country | profile.user.country | text | |
Profile User Created at | profile.user.createdAt | YYYY-MM-DD | |
Profile User Email | profile.user.email | ||
Profile User First name | profile.user.firstName | text | |
Profile User Full name | profile.user.fullName | text | |
Profile User Last name | profile.user.lastName | text | |
Profile User Phone number | profile.user.phoneNumber | numeric | |
Profile User Photo url | profile.user.photoUrl | url | |
Profile User Postcode | profile.user.postcode | numeric | |
Profile User Preferred name | profile.user.preferredName | text | |
Profile User State | profile.user.state | text | |
Profile User Status | profile.user.status | ||
Profile User Suburb | profile.user.suburb | text | |
Profile User Unsubscribed at | profile.user.unsubscribedAt | YYYY-MM-DD | |
Profile User Updated at | profile.user.updatedAt | YYYY-MM-DD |
## expand
## expand
# Campaign Fields
Field | Field ID | Description | Value |
Campaign Currency | campaign.currency | currency | |
Campaign Goal | campaign.goal | numeric | |
Campaign Name | campaign.name | text | |
Campaign Total | campaign.total | numeric | |
Campaign URL | campaign.url | url |
## expand
## expand
# Attribution Fields
Field | Field ID | Description |
Campaign | attribution.utmCampaign | Marketing Campaign title associated |
Medium | attribution.utmMedium | The marketing channel used (eg. Social, Email) |
Source | attribution.utmSource | Individual site used in the medium |
Term | attribution.utmTerm | Used to track specific keywords for paid organic campaigns |
Content | attribution.utmContent | Optional value to highlight where on a page the link was placed |
Referrer | attribution.referrer | Source of traffic to your website |
Page Path | attribution.pathname | Page URL for source |
## expand
### accordion
Parent Fields explained
Scenario 1: Individual Profile Linked to a Team, and the Team is Part of an Organisation
- Organisation Profile: This represents the overall company or group
- Team Profile: Each team within the organisation has its own profile
- Individual Profile: Each person (or employee) has their own personal profile
- An Individual Profile is linked to a Team Profile (the group they belong to)
- The Team Profile is part of the Organisation Profile (the company they work for)
- The Team is the parent of the Individual, meaning the team is one step higher in the hierarchy
- The Organisation is the parent of the Team, but since the individual belongs to a team, the team is still considered their "parent" profile
- Think of the Organisation Profile as the "company" that hires people
- The Team Profile is the "department" within that company, like the "Marketing Team" or "Sales Team"
- The Individual Profile is the "employee" who works in that department
Scenario 2: Individual Profile Linked Directly to an Organisation
- The Organisation Profile is the direct "parent" of the Individual Profile
- There is no team involved in this situation, so the individual is directly linked to the organisation, and the organisation is their "parent"
- In this case, imagine someone works for a large company, but they don’t belong to a specific team. They are still part of the organisation itself, just not assigned to a particular group
- So, the Organisation Profile is their main connection, and the Individual Profile is directly tied to it
Scenario 3: Team Profile Linked Directly to an Organisation with No Individual Profiles
In this scenario, a Team Profile exists within an Organisation Profile, but there are no Individual Profiles involved. This is the case where a team exists as part of an organisation, but it doesn't have any specific individuals tied to it at the moment.
How It Works:
- The Organisation Profile is the parent of the Team Profile
- There are no Individual Profiles linked to this team in this case—just the team itself within the organisation
Simple Example:
- Imagine a company has several teams, but some teams are "virtual" or in planning and haven't yet been assigned any members. These teams still exist within the organisation, but they don’t have any employees or individual profiles associated with them yet
- The Organisation Profile is the parent of the Team Profile, but there are no individual profiles tied to the team in this scenario
Generating Profile Reports
The concepts explained above can also be applied to generating a profile report. When running an Individual Profile or a Team Profile report, using the parent fields will display the values of the profile that is one step above.
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 🤯