Menu → Sources → New import → Sync → BigQuery
In short: if your data is already in Google Cloud, push your feedback into a BigQuery table: Feedier reads it automatically. It's the easiest method to maintain for a regular flow.
Connector overview
Type | Automatic sync |
What is imported | The rows of a table, with the chosen fields |
Prerequisites | A Google Cloud service account with read access to the table |
Who can set it up | Admin, or Editor with the Sources module |
Set up the import
In Google Cloud, create a service account with read access to your table, and download its key in JSON format.
In Sources, click New import, choose Sync then BigQuery.
Fill in the fields:
Field | Content |
Service account credentials (JSON) | The content of the JSON key |
BigQuery dataset name | The dataset |
BigQuery table name | The table that contains the feedback |
Fields to import | The columns to import (questions and attributes) |
Date field | The column that gives the feedback date |
Unique identification field(s) | The column or columns that identify a row, to avoid duplicates |
Import condition (optional) | A filter on the rows to import |
Choose the source, map the fields, then finish.
Best practices
Apply the CSV import formats: NPS from 0 to 10, numeric ratings, consistent dates.
Choose a stable unique ID (for example
ticket_id): an updated row doesn't create a duplicate.Don't rename columns once the import is in place.
Use the import condition to send only the useful rows: you limit the volume analyzed.
What AI does with this data
Each imported text column (comment, transcript, ticket…) is analyzed by AI as soon as it arrives: sentiment, topics from your taxonomy, and masking of personal data (nlp_… attributes). Your warehouse data becomes comparable with your surveys and reviews, with no processing on your side. Each analyzed verbatim is deducted from your AI analysis budget.
Last reviewed: November 11, 2026, version 4.23.5.
