Birdie CSV Export

Mariana Carrero Rodrigues

Last Update 한 달 전

Birdie provides four interrelated CSV files when exporting user feedback data. This document explains their structure, relationships, and common usage rules.

1. feedbacks.csv – Main Feedback Export

This file contains raw records of all feedback captured in your Birdie account, based on the filters applied at export time.


Each row represents a unique piece of feedback. Feedback may or may not be mapped to any area or opportunity. Unmapped feedback is common and can include irrelevant or neutral comments.

Key fields:


  • Ingested_ID

  • Posted_at

  • Text

  • Source

  • Rating

  • Account_id

  • Language

2. areas.csv – Feedback to Area Relationships

This file lists feedbacks that have been associated with one or more Areas configured in your Birdie account.


A single feedback can be linked to multiple areas. Feedback not associated with any area will not appear in this file.


Key fields:

  • Feedback Ingested ID

  • Area_ID

  • Area_Name

3. opportunities.csv – Relationship Between Feedbacks, Areas, and Opportunities

This file lists cases where feedback has been mapped to both an Interest Area and a Business Opportunity.


Feedbacks with positive sentiment or without friction typically do not generate opportunities, so they may appear in areas.csv but not in  opportunities.csv.


Key fields:

  • Feedback Ingested ID

  • opportunity_id

  • opportunity_name

4. area_opportunities.csv – Linking Areas and Opportunities

This new file defines the many-to-many relationship between Areas and Opportunities.

Previously, this relationship was included inside opportunities.csv.
Now, it has been extracted into this separate file for improved clarity and flexibility.

Each row represents a unique pairing between an area and an opportunity.

Key Fields

  • area_id

  • opportunity_id

Linking and Rules

  • All files use the field ingested_id (in feedbacks.csv) and area_id / opportunity_id as linking keys between tables.

    You can join them using the following logic:

    Join GoalPrimary Key(s)ExampleFeedback → Areasfeedbacks.ingested_id = areas.ingested_idFind all areas mentioned in feedbackFeedback → Opportunitiesfeedbacks.ingested_id → areas.ingested_id → area_opportunities.area_id → opportunities.opportunity_idTrace which feedback generated specific opportunitiesArea ↔ Opportunityarea_opportunities.area_id = areas.area_id and area_opportunities.opportunity_id = opportunities.opportunity_idLink opportunities to their respective areas
Typical Data Presence Rules

  • A feedback may appear only in feedbacks.csv if it hasn’t been mapped to any area or opportunity.

  • A feedback may appear in areas.csv but not in area_opportunities.csv if no opportunity was identified in that area.

  • A feedback appears in all four files if it is linked to both an area and an opportunity.

Additional Fields

The following additional fields are present in the CSVs but are typically used for internal or metadata purposes:


feedbacks.csv
  • ID, Batch ID, Ingested At, Updated At

  • Messages First Posted At, Messages Last Posted At, Total Messages

  • Accounts, Custom Fields, Channel, Kind Name

  • Source Alias, Status, Priority, Subject, Category, URL

areas.csv

  • Feedback ID, Area ID, Area Name

opportunities.csv
  • Feedback ID, Area ID, Area Name

  • Opportunity ID, Opportunity Name, Signal Type

Diagram – Birdie CSV Data Export Structure

Below is a conceptual diagram that illustrates the relationship between the CSVs:

Was this article helpful?

0 out of 0 liked this article