> For the complete documentation index, see [llms.txt](https://developer.collibra.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://developer.collibra.com/tutorials/configure-google-cloud-platform-for-collibra-insights-consumption.md).

# Configure Google Cloud Platform for Collibra Insights consumption

## Introduction

Usage Analytics creates Parquet files to store and deliver the Reporting Data Layer. You must store the files and make the reporting data available for consumption. The Google Cloud Platform provides ways for storage via Google Cloud Buckets and catering thorough Google BigQuery.

Follow these steps to create and configure a bucket named **collibra-insights-dg** where you store Parquet files with tables of the Reporting Data Layer exported from Collibra Platform, and configure BigQuery to use that data.

## Prerequisites

* Access to a Google Cloud account with Cloud Buckets and BigQuery.
* The Parquet files with the tables of the Reporting Data Layer extracted from the ZIP file.
* A project, for example, *Collibra Insights*.

## Configure Google Cloud Storage to store Parquet files

{% stepper %}
{% step %}
In the Google Cloud Platform project, go to **Storage** → **Browser**.

<img src="/files/3q38oiQrVEui8Nq5oadV" alt="Path to the storage browser in a Google Cloud Platform project" width="25%">
{% endstep %}

{% step %}
Select **CREATE BUCKET**.

<img src="/files/eJP16D1RTvz9a0FAfODB" alt="The Create Bucket button in the storage browser of a Google Cloud Platform project" width="50%">
{% endstep %}

{% step %}
Enter the required information:

* **Name**: for example, *collibra-insights-dg*.
* **Location type**: *Region*.
* **Location**: for example, *europe-west1*.
  {% endstep %}

{% step %}
Select a default storage class for your data: *Standard*.
{% endstep %}

{% step %}
Select how to control access to objects: set object-level and bucket-level permissions.
{% endstep %}

{% step %}
Optionally, select an encryption method in the **Advanced settings** section: for example, *Google-managed key*.
{% endstep %}

{% step %}
Click **CREATE** to finish the process.
{% endstep %}

{% step %}
In the newly created bucket, upload the Parquet folders with the tables of the Reporting Data Layer.

<img src="/files/Av0nqF3YJjrfrQelJJmf" alt="A list of default Parquet folders representing tables of the Reporting Data Layer extracted from the Collibra Platform." width="25%">
{% endstep %}
{% endstepper %}

## Configure BigQuery to make the Reporting Data Layer available

1. In the Google Cloud Platform project, go to **BigQuery**.

   <img src="/files/W7b8uWMhjI6acD3JiL3I" alt="Location of BigQuery in a Google Cloud Platform project" width="25%">
2. In the **Resources** section, select the bucket with the Reporting Data Layer tables. We are using **collibra-insights-dg** in this example.

   <img src="/files/m4FLQEZZ8H302c0qVPoR" alt="Location of the collibra-insignts-dg bucket in Google BigQuery" width="25%">

### Create a dataset

{% stepper %}
{% step %}
In the **collibra-insights-dg** bucket, select **CREATE DATASET**.
{% endstep %}

{% step %}
Enter the name of the dataset in the **Dataset ID** filed. The name is appended to the bucket name to form the ID.
{% endstep %}

{% step %}
Leave all other fields to their default values.
{% endstep %}
{% endstepper %}

### Create the dataset tables

{% stepper %}
{% step %}
In the **collibra-insights-dg** bucket, select **CREATE TABLE**.
{% endstep %}

{% step %}
Enter the required **Source** information:

* **Create table from**: select *Google Cloud Storage*.
* **Select file from GCS bucket**: *collibra-insights-dg/asset/\**.
* **File format**: select `Parquet`.
  {% endstep %}

{% step %}
Enter the required **Destination** information:

* **Project name**: select your project. We are using *Collibra Insights* in this example.
* **Dataset name**: select your dataset name. We are using *insights*.
* **Table name**: enter the Reporting Data Layer table name, for example, *asset*.
  {% endstep %}

{% step %}
Leave all other fields to their default values.
{% endstep %}

{% step %}
Click **CREATE**.
{% endstep %}
{% endstepper %}

<i class="fa-chevrons-right">:chevrons-right:</i> When the job completes, the table appears under the dataset.

Repeat the above steps for each table.

<img src="/files/iQfflBLnZmp0bJm9JoLx" alt="A list of tables created in a Google BigQuery dataset corresponding to tables of the Reporting Data Layer extracted from the Collibra Platform" width="25%">

## Verification

To verify that everything is working, you can run a test SQL in the Query editor:

```
select c.community_name
, d.domain_name
, a.*
from insights.asset a
join insights.domain d
on a.domain_id = d.domain_id
and a.snapshot_date = d.snapshot_date
join insights.community c
on c.community_id = d.community_id
and c.snapshot_date = d.snapshot_date;
```

## Next steps

You can now [configure Tableau](https://developer.collibra.com/tutorials/tableau-bigquery/) to display the data you store in Google Cloud Platform.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://developer.collibra.com/tutorials/configure-google-cloud-platform-for-collibra-insights-consumption.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
