HubSpot User Interaction Properties Used by Shalom Media: Complete Field Reference Guide
1. Overview
This guide outlines all User Interaction properties maintained in HubSpot and used by Shalom Media for tracking audience engagement, consent preferences, media consumption, and related communication details. These fields support interaction analysis, content performance reporting, and integration with Shalom platforms like myShalom and program archives.
2. How to Use This Guide
-
Use Ctrl + F to search for a field by name or purpose.
-
Do not manually update fields that are mapped from external systems unless authorized.
-
For new property creation or updates, contact the CRM Admin.
3. User Interaction Property Definitions
3.1 Identification & Lifecycle
| Property Name | Description |
|---|---|
| hs_object_id | Unique HubSpot system ID for the user interaction record. Used in ingestion and internal mapping. |
| hs_createdate | Date and time when the interaction record was created in HubSpot. Set automatically. |
| hs_lastmodifieddate | Timestamp of the most recent update to any field in the interaction record. Includes internal HubSpot property changes. |
| hs_merged_object_ids | List of record IDs that have been merged into this record. Set automatically by HubSpot. |
| hs_created_by_user_id | ID of the HubSpot user who created the record. Set automatically. |
| hs_updated_by_user_id | ID of the HubSpot user who last updated the record. Set automatically. |
| hs_object_source_label | High-level label indicating how this record was created (e.g., API, Import, Manual Entry). |
| hs_object_source_detail_1 / 2 / 3 | Additional source detail fields explaining record creation context. |
| hubspot_owner_id | Assigned HubSpot owner of the interaction record. |
| hubspot_owner_assigneddate | Timestamp when the owner was last assigned. |
| hubspot_team_id | Main team of the assigned owner. |
| hs_shared_team_ids | Additional HubSpot teams with access to the record. |
| hs_shared_user_ids | Additional HubSpot users with access to the record. |
3.2 Contact & Location Information
| Property Name | Description |
|---|---|
| Email address of the person involved in the interaction. | |
| first_name | First name of the contact linked to the interaction. |
| last_name | Last name of the contact linked to the interaction. |
| phone_number | Contact’s phone number. |
| country | Free-text country value (may come from form submissions or integrations). |
| primary_country | Standardized country enumeration for reporting and segmentation. |
3.3 Interaction & Engagement Details
| Property Name | Description |
|---|---|
| interaction_type | Type of interaction (e.g., Program Feedback, Prayer Request, Event Participation). |
| user_interaction_name | Descriptive name for the interaction (e.g., “Prayer Request - August 2025”). |
| message_content | Content or message submitted during the interaction (e.g., feedback text, prayer request details). |
| sw_episode | Shalom World episode associated with the interaction. |
| sw_program | Shalom World program name associated with the interaction. |
| sw_program_rating | Numeric rating given to the program. |
| appmastery_video_id | ID of the AppMastery video related to the interaction (if applicable). |
| contribution | Contribution type linked to the interaction (if applicable). |
| represent_shalom_world_news_in_my_region | Indicates if the contact has volunteered to represent Shalom World News regionally. |
3.4 Career & Consent Information
| Property Name | Description |
|---|---|
| careers___job_role | Job role selected by the contact in career-related forms. |
| consent_to_display | Consent status for displaying user-provided content (e.g., testimonials, names). |
4. Important Notes
-
hs_object_id is the primary identifier for all ingestion, mapping, and updates.
-
interaction_type, user_interaction_name, and message_content are key for reporting and categorizing engagement.
-
primary_country should be used for standardized geographic reporting instead of the free-text country field.
-
Consent fields (consent_to_display) must be respected for privacy and compliance.
-
Merged record IDs indicate that this record may consolidate multiple past interactions.