Connect your data: overview
A connection tells Birdseye where records come from. A track is the record type that receives them. A mapping connects source fields to Birdseye fields. A rooftop or domain identifies the operating scope that owns the records.
What you will accomplish
You will choose the correct connection type and understand what must be verified before data can be trusted.
Who can do this
Owners and Admins can manage customer-facing connections. Members who need a feed changed should contact an Owner or Admin.
Before you start
Collect the source owner, target track, rooftop or domain, field definitions, a safe sample, and any schedule or credential information. Never paste credentials into a support ticket or help article.
Open integrations
- Open the account menu.
- Select Config.
- Select Connect your data.
Expected result: Birdseye opens /config/integrations, where the available connection types appear. Availability can depend on vertical and workspace configuration.
Choose a connection method
- Choose CSV for a manual file or pasted comma-separated sample.
- Choose SFTP when a source places files on a remote server on a schedule.
- Choose API when Birdseye should poll a JSON endpoint.
- Choose Google Analytics for a supported GA4 property.
- Choose Google Sheets for an approved spreadsheet connection.
- Choose Zapier when a Zap will create or update records through the Birdseye integration.
- Choose Webhooks when another system will push records to a Birdseye endpoint.
- Choose Write-back to review eligible corrections waiting to return to a connected system.
Verify a connection
- Confirm the target track.
- Confirm the rooftop or domain.
- Test or preview the source when that control is available.
- Map required fields, including the correlation key that identifies a record.
- Review warnings before importing or enabling a run.
- Inspect the run or import history after the first attempt.
Expected result: successful records appear in the intended track and scope after that connection's configured processing cycle. Birdseye does not promise a universal “few minutes” arrival time: CSV is user-triggered, while SFTP and API timing use explicitly configured polling intervals.
Troubleshooting and recovery
- Config is missing: only Owners and Admins can manage these connections.
- A connection type is missing: it may not apply to the workspace vertical or enabled product configuration.
- Records appear in the wrong place: stop further runs and verify the target track, rooftop, routing, and mapping.
- A run failed or a file was quarantined: open its history and read the specific result before retrying.
Related articles
Last verified against the product on 2026-07-29.