Current Data Feed Offerings
A data feed is an automated daily transfer of bulk data from your community. You can download data feeds from the CSRconnect Admin Portal or set up delivery to an SFTP (Secure File Transfer Protocol) site. The following list describes each available data feed.
Tip: Refer to the Data Dictionary for details on the columns included in each data feed. To download it, go to CSRconnect Admin Portal, Admin tools, Reporting, Data Feeds, then select Download Data Dictionary.
-
Admin Roles: Includes employee data for every user assigned a CSRconnect Admin role (not legacy admin roles).
This feed loads the complete data history each time and doesn't require a date datapoint.
-
Board Membership: Includes details for active board memberships and current board member positions.
This feed loads the complete data history each time and doesn't require a date datapoint.
-
Custom Questions: Includes details about custom questions and their answers.
-
Includes a date datapoint (custom_question_response_date) that identifies new records to include.
-
The event_id column can be null for these reasons:
-
Custom questions are used for non-volunteer event elements.
-
Individual activities with a custom question set don’t have an event_id because they aren’t associated with an event.
-
Event creators who don’t participate in the event they created don’t have a custom question set response for participation.
-
Custom questions for volunteering can be assigned to event creators or participants. A participant who didn’t create the event has null custom question responses for the creator’s question set.
-
-
If an active participation is associated with custom questions, the volunteer_question_source column displays one of the following results:
-
If an associated event creator custom question set response ID exists, Creator appears.
-
If an associated custom question set response ID exists, Signup appears.
-
If an associated CRA custom question set response ID exists, CRA appears.
-
If an associated campaign custom question set response ID exists, Campaign appears.
-
If none of these apply, the result is null.
Note: A participation is inactive if the participant didn't attend.
-
-
-
Donations (formerly All Giving): Includes donations and matches.
Includes a date datapoint (updated_date) that identifies new records to include.
-
Employees: Includes employee data, registration details, and non-HR user information.
This feed loads the complete data history each time and doesn't require a date datapoint.
Note: In the Employees data feed, the employee_registration_date column lists the date a support account or community admin added the employee. The last_login_date column displays when the user most recently logged in to CSRconnect.
-
Events: Includes details and event attributes for all events entered in CSRconnect.
-
Includes a date datapoint (event_updated_date) that identifies new records to include.
-
The event_status column displays values such as Live, Pending, and Declined, and can also be null.
-
The number_of_occurrences column includes only active occurrences.
-
-
Groups: Includes groups and member details.
This feed loads the complete data history each time and doesn't require a date datapoint.
-
Incentives: Includes details about Incentive requests.
Includes a date datapoint (incentive_updated_date) that identifies new records to include.
-
Match Custom Questions: Includes details about match custom questions and their answers.
Includes a date datapoint (custom_question_response_created_date) that identifies new records to include.
-
Payments: Includes details about disbursements.
Includes a date datapoint (payment_updated_date) that identifies new records to include.
-
Pledges: Includes active and inactive payroll pledges.
-
Includes a date datapoint (pledge_updated_date) that identifies new records to include.
-
The is_payroll_request_onetime column indicates whether a pledge is one-time or recurring. The system populates it when a user creates a pledge or imports one from a client file using the Payroll Pledge Import Tool.
-
The system populates the is_employee_active column based on the client's HR file.
-
The system populates the is_payroll_pledge_active column when a user creates a pledge or imports one from a client file using the Payroll Pledge Import Tool.
-
-
SDG: Includes details about Sustainable Development Goals (SDGs).
This feed loads the complete data history each time and doesn't require a date datapoint.
-
Volunteer (formerly New Volunteer): Includes transactional details for Volunteer Manager.
-
Includes a date datapoint (volunteer_participation_updated_date) that identifies new records to include.
-
When the is_volunteer_participation_active column displays FALSE, it indicates that the employee canceled their participation or their participation is no longer associated with an event.
-
The participation_type column reflects the following event scenarios:
-
If the employee created the event, the column is set to Creator.
-
If the employee organized the event, the column is set to Organizer.
-
If the guest ID tied to a participation is null, the column is set to Participant.
-
For other scenarios, the column is null.
-
-
The sign_up_source column identifies how an employee signed up for the opportunity:
-
If the employee created the opportunity, the column displays Organizer. Otherwise, it displays Employee.
-
If the employee created a wait list, the column displays Organizer. Otherwise, it displays Employee.
-
-
The event_has_recurrences column is null for NPO events, which don't have recurrences.
-
If the employee is wait-listed and not tied to an active participation, the volunteer_participation_id column is null and the is_wait_list column is set to TRUE.
-
For Add Your Own organizations, the event_benefitting_organization column lists the associated details. Charity-specific details, such as charity_id, charity_name, and parent_charity_name, are null.
-
-
VTO: Includes details about Volunteer Time Off (VTO) requests.
Note: Column order remains consistent, so you can reliably build on these fields. We can add new columns to the end of a data feed as functionality expands. Clients are notified when this happens.