Current Data Feed Offerings
A data feed is an automated daily transfer of bulk data from your community that you can download from the CSRconnect Admin Portal or set up to deliver to an SFTP. The following list provides descriptions for each of our data feed offerings.
Tip: Refer to the Data Dictionary for details on the columns included in each data feed. To download, go to CSRconnect Admin Portal, Admin tools, Reporting, Data Feeds, then select Download Data Dictionary.
-
Admin Roles: Employee data for every user tied to a CSRconnect Admin Role (not legacy Admin roles)
Pulls the all-time load - date datapoint is not needed
-
Board Membership: Details for any active board membership or present board member positions
Pulls the all-time load - date datapoint is not needed
-
Custom Questions: Details related to custom questions and answers
-
Contains a date datapoint (custom_question_response_date) that determines if there is new data to include
-
The event_id can be null for a number of reasons:
-
Custom questions were used for non-volunteer event elements.
-
Individual activities with a custom question set assigned to them won’t have an event_id (since they’re individual activities).
-
Event creators who don’t participate in the event they created do not have a custom question set response for participation.
-
Custom questions for volunteering can be assigned to event creators or event participants. A participant who didn’t create an event would have null custom question responses for custom question sets associated with creators.
-
-
If an active participation is associated with custom questions, the volunteer_question_source will display the following results:
-
If there is an associated event creator custom question set response id, then "Creator" appears.
-
If there is an associated custom question set response id, then "Signup" appears.
-
If there is an associated CRA custom question set response id, then "CRA" appears.
-
If there is an associated campaign custom question set response id, then "Campaign" appears.
-
If none of the above are associated with the opportunity, then the result is null.
Note: A participation can be inactive if the participant didn't attend.
-
-
-
Donations (formerly All Giving): Donation and matches
Contains a date datapoint (updated_date) that determines if there is new data to include
-
Employees: Employee data and registration detail; includes non-HR user information
Pulls the all-time load - date datapoint is not needed
Note: In the Employee data feed, the employee_registration_date column lists the date when the support account or community admin added an employee. The last_login_date displays when a user most recently logged into CSRconnect.
-
Events: Details and event attributes for all events entered into the CSRconnect platform
-
Contains a date datapoint (event_updated_date) that determines if there is new data to include
-
The event_status column displays all event status values, including Live, Pending, and Declined. This feed can also have null values.
-
The number_of_occurrences column only includes active occurrences.
-
-
Groups: Groups and member detail
Pulls the all-time load - date datapoint is not needed
-
Incentives: Details related to Incentive requests
Contains a date datapoint (incentive_updated_date) that determines if there is new data to include
-
Match Custom Questions: Details related to matching custom questions and answers
Contains a date datapoint (custom_question_response_created_date) that determines if there is new data to include.
-
Payments: Details related to disbursals
Contains a date datapoint (payment_updated_date) that determines if there is new data to include
-
Pledges: Active and inactive payroll pledges
-
Contains a date datapoint (pledge_updated_date) that determines if there is new data to include
-
The is_payroll_request_onetime column determines whether a pledge is one-time or recurring. It is populated when a user creates a pledge or a pledge is imported from the provided client file using the Payroll Pledge Import Tool.
-
The is_employee_active column is populated based on the client's HR File.
-
The is_payroll_pledge_active column is populated when a user creates a pledge or a pledge is imported from the provided client file using the Payroll Pledge Import Tool.
-
-
SDG: Details related to Sustainable Development Goals
Pulls the all-time load - date datapoint is not needed
-
Volunteer (formerly New Volunteer): Volunteer Manager transactional detail
-
Contains a date datapoint (volunteer_participation_updated_date) that determines if there is new data to include
-
When FALSE appears in the is_volunteer_participation_active column, it indicates that an employee canceled their participation or their participation is no longer associated with an event.
-
The participation_type column is associated with various event scenarios:
-
If an employee created the event, then it is set to "Creator."
-
If an employee has organized the event, then it is set to "Organizer."
-
If guest id tied to a participation is null, then it is set to "Participant."
-
The column is set to null for any other scenario.
-
-
The sign_up_source column provides an employee's participation information.
-
If the employee created the opportunity, it is listed as "Organizer." Otherwise, the column lists "Employee."
-
If the employee created a wait list, the term "Organizer" appears. Otherwise, the column lists "Employee."
-
-
The event_has_recurrences column does not list recurrences for NPO events. NPO events do not have recurrences and this column will be null.
-
If an employee is wait listed and therefore was not tied to an active participation, the volunteer_participation_id column will be null and the is_wait_list column is set to TRUE.
-
For Add Your Own organizations, the associated details are listed in the event_benefitting_organization column. Any charity-specific details, such as charity_id, charity_name, and parent_charity_name, are null.
-
-
VTO: Details related to Volunteer Time Off requests
Note: To ensure you can reliably build on the fields, we will not adjust the column order. We may add columns to the end of a data feed as new functionality is developed. Clients are updated as columns are added.