Skip to content

Commit e9ead23

Browse files
committed
update Reverse-ETL bigQuery docs
1 parent a492bb7 commit e9ead23

File tree

1 file changed

+14
-12
lines changed

1 file changed

+14
-12
lines changed

src/connections/reverse-etl/reverse-etl-source-setup-guides/bigquery-setup.md

Lines changed: 14 additions & 12 deletions
Original file line numberDiff line numberDiff line change
@@ -4,7 +4,7 @@ redirect_from:
44
- '/reverse-etl/bigquery-setup/'
55
---
66

7-
Set up BigQuery as your Reverse ETL source.
7+
## Create service account
88

99
> warning ""
1010
> You need to be an account admin to set up the Segment BigQuery connector as well as write permissions for the `__segment_reverse_etl` dataset.
@@ -22,16 +22,6 @@ To set up the Segment BigQuery connector:
2222
10. When your service account pulls up, click the 3 dots under **Actions** and select **Manage keys**.
2323
11. Click **Add Key > Create new key**.
2424
12. In the pop-up window, select **JSON** for the key type and click **Create**. The file will download.
25-
13. Copy all the content within the file you just created and downloaded.
26-
14. Navigate to the Segment UI and paste all the credentials you copied from step 13 into the **Enter your credentials** section.
27-
19. Enter your **Data Location**.
28-
20. Click **Test Connection** to test to see if the connection works. If the connection fails, make sure you have the right permissions and credentials and try again.
29-
6. Click **Add source** if the test connection is successful.
30-
31-
After you've added BigQuery as a source, you can [add a model](/docs/connections/reverse-etl/setup/#step-2-add-a-model).
32-
33-
> info "BigQuery Reverse ETL sources support Segment's dbt extension"
34-
> If you have an existing dbt account with a Git repository, you can use [Segment's dbt extension](/docs/segment-app/extensions/dbt/) to centralize model management and versioning, reduce redundancies, and run CI checks to prevent breaking changes.
3525

3626
## Constructing your own role or policy
3727
When you construct your own role or policy, Segment needs the following permissions:
@@ -52,4 +42,16 @@ Permission | Details
5242

5343
The `bigquery.datasets.*` permissions can be scoped only to the `__segment_reverse_etl` dataset.
5444

55-
After you've successfully added your BigQuery source, [add a model](/docs/connections/reverse-etl/setup/#step-2-add-a-model) and follow the rest of the steps in the Reverse ETL setup guide.
45+
After you've successfully added your BigQuery source, [add a model](/docs/connections/reverse-etl/setup/#step-2-add-a-model) and follow the rest of the steps in the Reverse ETL setup guide.
46+
47+
## Set up BigQuery as your Reverse ETL source
48+
1. Copy all the content within the **JSON** file created and downloaded in previous section.
49+
2. Navigate to the Segment UI and paste all the credentials you copied from previous step into the **Enter your credentials** section.
50+
3. Enter your **Data Location**.
51+
4. Click **Test Connection** to test to see if the connection works. If the connection fails, make sure you have the right permissions and credentials and try again.
52+
5. Click **Add source** if the test connection is successful.
53+
54+
After you've added BigQuery as a source, you can [add a model](/docs/connections/reverse-etl/setup/#step-2-add-a-model).
55+
56+
> info "BigQuery Reverse ETL sources support Segment's dbt extension"
57+
> If you have an existing dbt account with a Git repository, you can use [Segment's dbt extension](/docs/segment-app/extensions/dbt/) to centralize model management and versioning, reduce redundancies, and run CI checks to prevent breaking changes.

0 commit comments

Comments
 (0)