On the Birdeye connector, survey response data is already being pulled, but one of the elements in the API response, extraParams, is not parsed & stored. This data allows us to connect responses to surveys (like NPS or CSAT surveys, or other custom workflows) back to an event that triggered the survey. In our case, we send an appointment ID as a "check-in", which then triggers a survey to a customer. In order for us to tie back NPS and CSAT responses to specific employees, we need to be able to tie back to our appointment ID that is returned in the extraParams data from a survey response. Below is additional detail about these fields from the support team:

I’ve reviewed this further and would like to share what we’ve found. The Birdeye endpoint you referenced (/survey/ext/list/responses) is already implemented in our connector under the Response entity. From the API response payload, we currently receive and process two parameters:

• customParam – This appears to represent custom fields that are specific to the survey response itself and is already supported in the connector.
• extraParams – This seems to contain additional custom fields that are primarily used for reporting or analytics context.

 
At this time, while the connector does receive extraParams in the API response, it is not yet parsed and stored as a dedicated field in the destination schema. Since this would be considered a custom-field enhancement to extend the existing connector behaviour, it is not currently implemented.
 
As a next step, we recommend raising a feature request for supporting extraParams in the Birdeye connector. This will allow our product and engineering teams to review the request and implement this accordingly.