A Google Cloud project is not the full billing boundary. A Cloud Billing account can pay for several projects, and its BigQuery export contains their costs together. For a useful cost report, identify the billing account, export dataset, and reporting period before connecting the source.
Choose the data source
| Question | Check |
|---|---|
| Which account should the report cover? | Match the export to the Cloud Billing account ID, not just a project name. |
| Do you need resource detail? | Enable Detailed usage cost export. Standard export has less resource detail. |
| How much history exists? | Inspect the earliest date in the export table before promising a comparison period. |
| Who may read the data? | Keep the grant at dataset scope and record the granted principal. |
Google describes Detailed usage cost export as standard billing data plus resource-level fields. Detail varies by service. A breakdown of GKE cluster cost in Google's export also requires GKE cost allocation. That Google setting does not imply a per-pod cost view in Costfluent.
Check history before connecting
A newly enabled export does not contain every past invoice. For a new EU or US multi-region dataset, Google backfills usage from the start of the previous month; for supported single-region datasets, collection starts when export is enabled. Initial backfill can take time. Changing the export dataset does not copy older exports into the new one.
Costfluent imports at most the previous six months, only as far back as the selected export has data. The effective history is the shorter of that product window and the rows actually present. Compare the first available usage day with the first month you intend to report before explaining a trend.
Grant access without a customer key
Costfluent creates a service account for your organization. Grant it BigQuery Data Viewer on the dataset holding the Detailed usage cost export. You do not upload a key from a service account in your Google Cloud organization. Costfluent runs queries in its own project, so the grant does not include permission to run jobs billed to yours. The connection guide shows where to copy the account address and test the connection.
After granting access, test the connection. If the export table is still empty, wait for its first rows and try again. Record the billing account, dataset, first export day, and grant together. That makes a cost report traceable through a monthly cloud cost review to the invoice. Keep billed cost and usage time distinct when you do so.
Sources and review boundary
Reviewed on 25 September 2026: Google Cloud, Export Cloud Billing data to BigQuery and set up export, including data availability and GKE. The Costfluent connection path and import window are in the product guide. Check the schema and first available row in your own dataset; a general backfill rule is no substitute for that check.