Kustom + Bigquery
Everything you need to connect Kustom and Bigquery: how to connect, which data moves, which settings there are and what to do when something goes wrong.
1. Getting started
Prepare both systems first, then connect them in Junipeer.
Prepare Kustom
Have your login details for this system ready. The full instructions show what Junipeer needs.
Full instructions- about 3 minutes
Prepare Bigquery
- Open the BigQuery connector in Junipeer
- Click Connect
- Sign in with the correct Google account
- Review and approve access
- Confirm the target project or dataset if prompted
- Return to Junipeer and verify the connection
Connect and test
Enter the details in Junipeer, switch on the flows you need and test with one order before you go live.
Getting started with Junipeer
2. Settings
The settings you see in Junipeer, in plain words. Open one to read more. The key is the technical name.
You don't need to read them all
In Junipeer every setting has a ? that opens the same explanation next to the form, right when you need it. With the Junipeer MCP your AI assistant can also propose the settings from your own data.
How the Junipeer MCP worksSettings for Kustom (3)
| Setting | What it controls | Key |
|---|---|---|
| Kustom API password or secret | Enter the password for the Kustom settlements API. | kustom_api_pass |
| Kustom API user/id | Enter the username or ID for the Kustom settlements API. | kustom_api_user |
| Kustom settlements API Url | Enter the web address (URL) of the Kustom settlements API. | kustom_api_url |
Settings for Bigquery (12)
| Setting | What it controls | Key |
|---|---|---|
| Customer table name | Enter the name of the table in BigQuery where customers are added. | bigquery_customer_table_name |
| Data Source | Enter the source to set on the data that is sent to BigQuery, so you can see where it came from. | bigquery_data_source |
| Dataset ID | Enter the ID of the dataset in BigQuery where Junipeer should create its tables. | bigquery_dataset_id |
| Define Extra Customer Fields | Add extra fields (columns) to the customer table in BigQuery. | bigquery_custom_customer_fields |
| Define Extra Order Fields | Add extra fields (columns) to the order table in BigQuery. | bigquery_custom_order_fields |
| Define Extra Order Rows Fields | Add extra fields (columns) to the order row table in BigQuery. | bigquery_custom_order_rows_fields |
| Include Order Rows | Decide whether order rows are included when orders are sent to BigQuery. | bigquery_include_order_rows |
| Include Personal Information | Decide whether personal information , such as names and addresses, is included when orders are sent to BigQuery. | bigquery_include_personal_information |
Show all 12 settings
| Setting | What it controls | Key |
|---|---|---|
| Include Postal Code and City | Decide whether the customer's postal code and city are included when orders are sent to BigQuery. | bigquery_include_postal_code |
| Map Custom Order Rows Fields | Fill your extra BigQuery order row fields with data from the order rows. | bigquery_map_custom_order_rows |
| Order table name | Enter the name of the table in BigQuery where orders are added. | bigquery_order_table_name |
| Project ID | Enter the ID of your Google Cloud (GCP) project where your BigQuery data lives. | bigquery_project_id |
Did this page help you?