HubSpot Deal Properties Used by Shalom Media: Complete Field Reference Guide
1. Overview
This internal reference guide outlines all standard and custom HubSpot Deal properties used at Shalom Media USA Inc. These fields are crucial for donor tracking, donation frequency analysis, integration with FundraiseUp and Stripe, reporting, and reconciliation. Intended for Support, CRM Ops, Data, Fundraising, and Finance teams.
2. How to Use This Guide
-
Use Ctrl+F or search the property label inside HubSpot’s deal editor.
-
Reference this guide when creating, reviewing, or debugging deal data.
-
Contact your CRM administrator for field modifications or onboarding new properties.
3. Field Definitions (Grouped by Function)
3.1 Deal Identity & Lifecycle
Property Name | Description |
---|---|
dealname |
Name/title assigned to the deal. Often includes donor name or source. |
dealstage |
Current stage in the pipeline (e.g., Pledged, Paid, Lost). |
pipeline |
The pipeline this deal belongs to. |
dealtype |
Categorizes deals (e.g., New, Existing, Manual). |
description |
Free-text description for contextual information. |
hs_object_id |
Unique HubSpot system ID for this deal (used in all ingestion workflows). |
hs_lastmodifieddate |
Timestamp of the most recent update to any deal field. |
createdate |
Date the deal was created in HubSpot. |
closedate |
Date the deal was marked as closed (won or lost). |
hs_created_by_user_id |
Internal ID of the user who created the deal. |
hs_is_closed |
Boolean: true if the deal is closed (won or lost). |
hs_is_closed_won |
Boolean: true if the deal was won. |
closed_lost_reason |
Reason provided if the deal was lost. |
days_to_close |
Calculated: days between create and close dates. |
3.2 Donation Details
Property Name | Description |
---|---|
donation_amount |
Actual donation amount as recorded in myShalom. |
donation_date / date_of_donation |
Date the donation occurred (used for timeline and reporting). |
converted_to_usd_donation_amount |
Donation amount converted to USD (FundraiseUp). |
converted_to_usd_payout_amount_per_fundraiseup |
Actual USD payout after processing fees. |
currency_per_fundraiseup |
Original donation currency per FundraiseUp. |
deal_currency_code |
Currency of the deal (e.g., USD, INR). |
amount |
HubSpot’s native deal amount. May be duplicated in custom fields. |
amount_in_home_currency |
Value converted to company currency using exchange rates. |
weighted_amount_in_company_currency |
Weighted value based on probability of closing. |
myshalom_currency |
myShalom currency format. |
payment_status |
Status of payment (e.g., Completed, Pending, Failed). |
payment_method |
Method used (e.g., Credit Card, Check, ACH, Stripe). |
manual_payment_methods |
Manual entry of payment method for offline donations. |
check_date |
Date on a physical check donation. |
check_number |
Check number for offline/manual payments. |
3.3 Recurring & Subscription
Property Name | Description |
---|---|
deal_frequency |
Frequency of giving (Monthly, Yearly, One-time, etc.). |
myshalom_donation_frequency |
Frequency per myShalom platform. |
recurringstartdate |
Start date of the recurring plan. |
recurring_date |
Numerical field indicating recurring billing day. |
next_payment_date |
Upcoming payment date in the plan. |
start_date / subscription_start_date |
First date of the current plan cycle. |
end_date / subscription_end_date |
End date of the current or final cycle. |
cancel_date |
Date the subscription was canceled (if any). |
number_of_billing_cycles |
Total number of recurring billing cycles (if defined). |
gateway_subscription_id |
ID from payment gateway (e.g., Stripe Subscription ID). |
gateway_transaction_id |
ID of the actual payment transaction. |
3.4 Donor & Member Info
Property Name | Description |
---|---|
shalom_member_uid |
Internal UID used across myShalom systems. |
swf_id / spf_id |
Shalom World Fellowship ID, and are only for contacts with recurring plans. |
myshalom_member_email |
Email ID of the donor/member linked with this deal. |
member_mobile_number / mobile_number |
Contact number for verification. |
primary_country / country |
Country of the donor (often matches contact record). |
event_name |
If the deal is linked to an event, this captures its name. |
event_location |
Location for the associated event (if applicable). |
event_registration_id |
Internal tracking ID for event registration. |
3.5 Source & Attribution
Property Name | Description |
---|---|
hs_analytics_source |
Original traffic source (e.g., Organic Search, Paid Ad). |
shalom_world_source_application |
Source application in the Shalom ecosystem (e.g., Web, App, CRM). |
fru_sub_account_code |
Sub-account code from FundraiseUp for attribution. |
don_id |
Internal donation ID used for myShalom ingestion and reconciliation. |
3.6 Journal & Reporting
Property Name | Description |
---|---|
this_is_a_journal |
Boolean or enum: Marks whether this is a journal-type deal. |
journal_comment |
Optional field to note journal-related entries. |
transaction_type |
Type of transaction (e.g., Journal, Payout, Manual Entry). |
mwb_fp_last_transaction_id |
Last transaction ID used for sync and update checks. |
mwb_fp_subscription_billing_frequency |
Custom billing frequency used in legacy subscriptions. |
3.7 HubSpot System Fields
Property Name | Description |
---|---|
num_associated_contacts |
Auto-generated count of contacts linked to this deal. |
hs_num_of_associated_line_items |
Auto-generated count of line items. |
hubspot_owner_id |
HubSpot user assigned to the deal (deal owner). |
hs_priority |
Priority level set for the deal (e.g., High, Normal). |
hs_manual_forecast_category |
Manually assigned forecast status (e.g., Pipeline, Commit). |
4. Important Notes
-
hs_object_id
is used as the primary unique identifier in integrations and ingestion. -
Fields like
donation_amount
,don_id
, andgateway_transaction_id
are critical for syncing with FundraiseUp, Stripe, and internal dashboards. -
Do not edit
shalom_member_uid
,swf_id
, orgateway_*
fields manually unless instructed by the data team. -
Deals with
deal_frequency
orrecurringstartdate
are often part of recurring plans. -