The Events data source in Gather Analytics provides comprehensive data on all scheduled events related to your cases. Each row in this data source represents a single event, offering an overview of various ceremonies, appointments, and other important engagements. This data source is essential for funeral homes that need to track and manage event schedules effectively to ensure seamless coordination and resource planning.
Where Does the Data Come From?
The data in the Events data source comes from scheduled events entered and managed on cases' organize pages.
As funeral home staff update and schedule events, this data source is refreshed in real-time, ensuring that all relevant information about case-related events is accurate and up-to-date.
This provides a centralized view of all event activities, supporting better scheduling, resource allocation, and communication.
Column Definitions for the Events Data Source
Funeral Home: The funeral home location in Gather to which this case currently belongs.
Case Type: The currently applied Case Type: At-Need, Pre-Need, Trade, One-Off. Case Types can be adjusted over the lifespan of a case.
Case Name: The name of the decedent as specified in the Death Certificate. Legal First Name + Legal Last Name. Clicking the name will link to the Organize page. [DC Section = ABOUT]
Event Name: The name of the event as entered by the funeral home.
Event Date: The date of the event. This field includes the Event Start Time, which is visible on hover and in the download. Timezone is driven by the funeral home location timezone.
Event Start Time: The start time of the event. Timezone is driven by the funeral home location timezone.
Event End Time: The end time of the event. Timezone is driven by the funeral home location timezone.
Event Duration: The time between the Event Start Time and the Event End Time, expressed in minutes.
Event Full Address: The full address provided for the event. This will show either the address found via Google Maps or the address as it was entered manually. There are fields for the individual address components.
Event Address 1: The first address line of the helper's location. Use the Event Full Address field for the address on a single line.
Event Address 2: The second address line of the helper's location. Use the Event Full Address field for the address on a single line.
Event City: The city name as found via Google Maps or the city name that was entered manually. Use the Event Full Address field for the address on a single line.
Event State: The city state as found via Google Maps or the city state that was entered manually. Use the Event Full Address field for the address on a single line.
Event Zip: The zipcode as found via Google Maps or the zipcode that was entered manually. Use the Event Full Address field for the address on a single line.
Is Invite Only: Specifies if the event was marked as invite only, which means the event can ONLY be viewed by logged in Admins and Guests.
Is LiveStream: Specifies if the event was marked to be LiveStreamed. This does NOT indicate that the LiveStream has occurred but just that the LiveStream flag on the event was set.
Is Conference: Specifies if the event is marked as an Arrangement Conference.
Is Event Passed: Specifies if the event has already happened. If the event start date is in the past, this flag will be set to True.
Case Created On: The date the case was first created in Gather UNLESS the Case Type has been converted to a new Case Type (e.g., Pre-Need to At-Need) then the most recent conversion date is used instead. This field includes the time if available, which is visible on hover and in the download. Timezone is driven by the funeral home location timezone.
Case Assignee: The currently assigned team member on this case.
Case WorkFlow: Custom WorkFlows allow you to change the way Gather works to fit the way you work so that you can focus more on what matters most. This field represents the currently applied WorkFlow.
Case Watcher: One or more individuals can be added as a watcher, allowing them to emulate the case assignee.
Case Death Date: Safest way to filter by date of death. If no death date, the date the case was first created in Gather is used. If no death date AND the Case Type has been converted to a new Case Type (e.g., Pre-Need to At-Need) then the most recent conversion date is used instead. NOTE: If a range is used for an unknown death date, this field will use the earliest date of the range.
KeepTrack #: The unique, 7-digit code assigned to a case when KeepTrack™ is initialized on a case to help maintain an accurate chain of custody. Cannot be changed.
Case Labels: Labels are a helpful way to categorize cases across multiple dimensions. Each applied label will display here.
Report Examples: Using Events Data
The Events data source allows funeral homes to generate a variety of reports to manage scheduling and monitor event-related activities. Here are some example reports you can create:
Upcoming Events Schedule: Generate a report listing all upcoming events over the next week or month, with details such as event type, date, and location. This report helps teams prepare resources, allocate staff, and coordinate with families.
Location Availability Report: Generate a report on the events taking place at specific location to determine upcoming availability for scheduling.
Events by Director: Create historical records of the events each staff member directed over the last month.
Case-Specific Event Summary: Develop a report that compiles all events related to a specific case. This is particularly useful for internal reviews or for providing families with a clear timeline of services and ceremonies.
Accessing the Events Data Source
Access to the Events data source can be managed by funeral home admins to ensure data security and appropriate permissions:
Individual Access: Admins can grant or restrict access based on employee roles and responsibilities, ensuring that only relevant team members can view event data.
Location-Specific Access: For funeral homes with multiple locations, admins can control data access per location. For example, an employee may have access to event data for Location A but not for Location B.
Admin Privileges: Admins automatically have access to the Events data source for the locations they oversee, ensuring full visibility into event management and coordination.
These controls help ensure that only authorized personnel can access and manage sensitive event data while allowing teams to stay informed and organized.
Need More Help? 👋
If you have questions about using the Events data source or need assistance setting up reports, feel free to reach out to our team anytime or call us at (208) 908-0488. We’re here to help!