Connector name: Birdeye

Table name: CHILD_BUSINESS, with one row per child location of the configured enterprise business. Loading the children as extra rows in the existing BUSINESS table, plus their rows in HOURS_OF_OPERATION and WORKING_HOUR, would also work for us.

API documentation link: https://docs.birdeye.com/api/business/get-child-businesses (Endpoint: GET /resources/v1/business/child/all?pid=<parent business ID>)

Additional details: 

• Enterprise Birdeye accounts are one parent business with many child locations; ours has 443. Today the connector syncs only the configured parent's profile and hours, as support confirmed in ticket 429578. BUSINESS has 1 row, while REVIEW already covers all the child locations (450 distinct BUSINESS_ID values).
• So reviews can't be joined to location details. Reviews carry only the business ID and name, with no address, coordinates, timezone or hours.
• Fields needed for each child: business ID (so it joins to REVIEW.BUSINESS_ID), name/alias, status, address, latitude/longitude, timezone, phone and hours of operation.
• Birdeye's engineering team confirmed the endpoint returns all 443 locations for our parent ID. The parent ID stays as the connector's setting, so review coverage isn't affected.
• Any multi-location Birdeye customer (franchises, retail chains, service networks) is likely affected the same way. Without this, each one has to build a separate pipeline just for location data.