[Extension] How to Send Data from Blip to BigQuery

1. Introduction

2. Features

3. Prerequisites

4. Installation and setup

5. How data reaches BigQuery

6. Support

Brief description: Send your Blip bot's contacts, messages, and tracking events to Google BigQuery and build reports, dashboards, and analyses in your own infrastructure.

Introduction

The BigQuery extension sends your Blip bot's conversation data to a dataset in Google BigQuery. Whenever a new contact, message, or tracking event occurs, Blip forwards the record to BigQuery, where you can query it with SQL, combine it with other sources, and feed BI tools, while maintaining your own operational history in your infrastructure.

For example, a WhatsApp customer service operation can accumulate all exchanged messages in a BigQuery table and use this data to measure response time, volume by period, and the most frequent topics, without relying solely on Blip's native reports.

Features

• Send contacts to the contacts table, including name, group, city, email, phone number, source, document, and extra fields.

• Send messages to the messages table, including sender, recipient, type, content, and metadata.

• Send tracking events to the trackings table, including category, action, and extra fields.

• Automatically create the dataset and tables in BigQuery during installation.

Supported on the following channels: all channels available on the Blip platform.

Prerequisites

Before setting up the extension, make sure you have:

• An active Google Cloud project. See the Google documentation to create a project.

• The BigQuery API enabled in that project.

• Permission to create service accounts in the project.

Installation and setup

1. Go to BigQuery in the Blip Store and click Start free trial.

2. Install the extension on the bot whose data you want to send to BigQuery.

3. Open the bot and access the extension through the extensions menu.

Create the project in Google Cloud

The extension stores data in a Google Cloud project. If you don't have one yet:

1. Go to the Google Cloud Console and create a new project.

2. Name the project and confirm its creation.

3. Select the project you created.

4. Enable the BigQuery API in the project.

Create the service account and generate the JSON key

The extension authenticates with BigQuery using a service account. To create one:

1. In the project dashboard, open IAM & Admin > Service Accounts.

2. Click Create service account and enter a name, ID, and description.

3. Assign the BigQuery Job User and BigQuery Data Owner roles to the account. These roles allow the extension to create the dataset, create the tables, and insert records.

4. Complete the account creation.

5. Open the account you created and go to Keys > Add key > Create new key > Create. Google generates a JSON file containing the service account key. Store this file in a secure location and do not share it.

Set up the extension in Blip

On the extension page in Blip, fill in the fields:

1. Dataset: the name of the dataset that will receive the data. Use only letters and underscores. If the dataset does not yet exist, the extension creates it.

2. Location: the region where the dataset will be created. Choose US or southamerica-east1 (São Paulo). To reduce latency for an operation in Brazil, use southamerica-east1.

3. Service account (JSON): upload the JSON file generated in the previous step. The extension verifies that the file belongs to a service account.

4. Click Save. The extension creates the dataset and tables in BigQuery, registers the webhook in Blip, and starts sending the data.

Important: usage and storage costs in Google Cloud are the responsibility of the configured account. Free accounts have limits that may affect the extension's operation.

How data reaches BigQuery

After you save, the extension registers an analytics webhook in the bot. From then on, each new contact, message, and tracking event is recorded in the dataset in three tables:

• contacts: one record per bot contact.

• messages: one record per sent or received message.

• trackings: one record per tracking event, grouped by category.

Recording is asynchronous, so there may be a short delay between the event in Blip and its arrival in BigQuery. When comparing the numbers with Blip reports, check the time zone, period, and filters used in each query.

Support

If you have questions or problems with the extension, contact us by email at support@wiv.com.br.

Need more help? Explore our content on Blip Academy or Blip Community, watch tutorials on our YouTube channel or get answers to your questions through our support channel 😃