The integration between Synerise and Google BigQuery opens up possibilities of exporting data collected in Synerise. By means of the **Upload Data to Table** node, you can push data from Synerise to add it in the form of rows in a BigQuery tables. You can use this connection in various scenarios such as exporting transactions, event data, customer information (such as marketing agreements), results of [metrics](/docs/analytics/metrics), [aggregates](/docs/analytics/aggregates/introduction-to-aggregates), [expressions](/docs/analytics/expressions/introduction-to-expressions), [reports](/docs/analytics/reports/introduction-to-reports), and many more to Google BigQuery. During the configuration of the node, you can use [Jinjava inserts](/developers/inserts/automation) which let you dynamically refer to the profile attributes and event parameters in the workflow.

This node is not optimized for batch operations that send large volumes of data (for example, updating all events for each profile). Use it to export changes within one event, profile attribute (for example, marketing agreement), analysis results and so on.

## Prerequisites --- - You must have a Google BigQuery project created. - Make sure that billing is enabled for your project. [Learn how to check if billing is enabled on a project](https://cloud.google.com/billing/docs/how-to/verify-billing-enabled). - Check the [quota policy for streaming data](https://cloud.google.com/bigquery/quotas#streaming_inserts). - You must create a dataset and a table in a BigQuery project. - You must define the schema of the BigQuery table (column definitions). ### Node configuration --- 1. Click **Google BigQuery > Upload Data to Table**. 2. Click **Select connection**. 3. From the dropdown list, select the connection. - If no connections are available or you want to create a new one, see [Create a connection](#create-a-connection). - If you selected an existing connection, proceed to [defining the integration settings](#define-the-integration-settings). ### Create a connection To allow the data exchange, establish a connection between Synerise and Google BigQuery. 1. At the bottom of the **Select connection** dropdown list, click **Add connection**. 2. On the pop-up, click **Sign in with Google**. 3. Select a Google account which has write access to the dataset that contains your destination table. [Learn about required permissions](https://cloud.google.com/bigquery/docs/streaming-data-into-bigquery#required_permissions). 4. Follow the instructions on the interface. 5. After the successful authentication, click **Next**. 6. In the **Connection name** field, enter the name of the connection. It's used to find the connection on the list. 7. Click **Apply**. **Result**: A connection is created and selected. ### Define the integration settings In this step, fill in the form that allows you to send data from Synerise to a table in Google BigQuery.

A blank configuration form in Upload Data to Table (Google BigQuery)

Fields marked with the

icon accept [snippets](/docs/assets/snippets) or [inserts](/developers/inserts). This integration allows usage of profile-related inserts.

1. In the **Project ID** field, enter the unique identifier of your project in Google BigQuery. You can learn how to find the project ID [here](https://support.google.com/googleapi/answer/7014113). 2. In the **Dataset ID** field, enter the unique identifier of the dataset in the BigQuery project. 3. In the **Table ID** field, enter the unique identifier of the table in the dataset. 4. In the **Rows** field, enter JSON with rows which you want to upload to BigQuery project. - Optionally, you can add the `insertId` parameter to the request body. It is a property used in the BigQuery streaming API to ensure the uniqueness of records being inserted into a BigQuery table. When you stream data into BigQuery, `insertId` acts as a unique identifier for each record. To ensure an automatic generation of the `insertId` parameter value, we recommend using the following Jinjava: `{{ currentStep.actionId }}`. This will generate a unique value of this parameter for each request sent from Synerise to BigQuery.

You can read more about insert ID in the [Google Big Query documentation](https://cloud.google.com/bigquery/docs/streaming-data-into-bigquery#dataconsistency).

- Each object in the array of the request body inserts data into a row. The `json` property contains keys (columns names) and values (column values). You can use [Jinjava inserts](/developers/inserts/automation) as the values of columns to dynamically send data stored in Synerise. This way, Jinjava dynamically fills in values (for example, ID, email address, expression/aggregate result) for each profile/item.

Click here to see example of the request body

[ { "insertId": "{{ currentStep.actionId }}", "json": { "name": "{{ customer.firstname }}", "email": "{{ customer.email }}" } } ]

4. Confirm the settings by clicking **Apply**. **Result**: When the Upload Data to Table node is executed, a [`bigQuery.uploadData` event](/docs/assets/events/event-reference/integration#bigqueryuploaddata) is generated on the activity list of the profile who is the actor in the workflow. ### Test integration --- You can run a test request. If the request body contains a dynamic reference to a profile attribute and/or an event data from preceding nodes, then you can define the context using [test profile data](/docs/settings/configuration/test-profiles).

Complete description of the feature is available in [Testing outgoing integrations](/docs/automation/test-requests-for-outgoing-integrations).

1. In the **Test integration** section, click **Send test request**. **Result**: A test request builder opens. If: - a request body contains dynamic references, the request preview appears after you select the context of test profiles and events. - a request body contains static data, the preview of the body request appears immediately.

2. If your request contains dynamic references (otherwise, the options aren't available): - From the **Test profile** dropdown, select a test profile in the context of whom the test request will be performed. - From the **Event context** dropdown list, you can select a particular occurrence of an event whose values/information will be used for the test request. 1. Select a test profile. **Result**: A history of test profile events appears.

A stream of events of a test profile

2. From the list of events, select one whose data you want use as a context. If there is no event you can use, in the upper-right corner of the pop-up, click **Define own event** and provide the body of the event. 3. Confirm by clicking **Apply**. 3. Verify the request body. If there is something you want to change, come back to the node settings from previous steps. 3. If the request body is ready to test, in the upper-right corner, click **Send request**. **Result**: The response section appears and the **Update response event** button becomes active. 4. Optionally, you can update response event with new parameters by clicking **Update response event** in the upper-right corner. ## Example of use --- You can use the integration to send information about complaint to Google BigQuery. So every time the complaint event is generated, the data from the event will be sent automatically to BigQuery. In this example, we use a custom event - `complaint.filed`. If you want to collect such event in your workspace, you must [implement it](/docs/assets/events/event-definitions) first.

1. Start the workflow with the **Profile Event** node. In the configuration of the node: 1. Enter the following title to the node: `complaint`. 2. Select the event that signifies a customer's complaint.

Click here to see example event and its parameters for an example customer

{ "time": "2023-02-15T15:24:49Z", "action": "complaint.filed", "label": "", "client": { "id": 5092159999, "email": "e0097757-d1e2-44ac-ba3c-d97979a354c1@anonymous.invalid", "uuid": "e0097757-d1e2-44ac-ba3c-d97979a354c1" }, "params": { "eventCreateTime": "2023-02-15T15:25:08.861Z", "name": "John", "surname": "Doe", "complaintNumber": "123", "complaintText": "Hello, my order didn't arrive." } }

2. As the next step of the workflow, select **Upload Data to Table** node. In the configuration of the node: 1. Fill out the form according to the instructions in the [Define the integration settings](#define-the-integration-settings) section. 2. In the **Rows** field, enter the JSON that extracts name, surname, complaint number and the contents of complaint from the event selected in the **Profile Event** node. The example body contains the [Automation inserts](/developers/inserts/automation) that retrieve data from the event included in the **Profile Event** node.

[
           {
             "insertId": "{{ currentStep.actionId }}",
             "json": {
               "name": "{{ automationPathSteps['complaint'].event.params.name }}",
               "surname": "{{ automationPathSteps['complaint'].event.params.surname }}",
               "complaintNumber": "{{ automationPathSteps['complaint'].event.params.complaintNumber }}",
               "complaintText": "{{ automationPathSteps['complaint'].event.params.complaintText }}"
             }
           }
       ]

3. As the finishing node, add the **End** node. **Result**: The event data is sent to a BigQuery table.