The built-in “Streaming” module allows you to collect raw data in Google BigQuery. After connecting the streaming module, SegmentStream starts sending all of your users behavior data to the BigQuery cloud data storage. The format of data storage completely corresponds to the DigitalData standard.
Create an account in Google BigQuery and configure the rights and roles.
Enter the “Integration” tab and click on the block with the SegmentStream Streaming logo.
Log in to Google with an account that has full access to BigQuery.
Click “Authenticate with Google” and follow the instructions. After successful authorization the integration setup form will appear.
Enter your BigQuery dataset name (2).
You can specify the name of an existing dataset. In this case, SegmentStream will automatically create and update tables in this dataset. You can also specify a new name. In this case, SegmentStream will automatically create a new Dataset.
The “Disconnect” (3) button is needed to disconnect your Google account from SegmentStream. Data streaming will end after the disconnection, but the settings will be saved.
Enter the console and select the required project from the drop-down list.
Type ddmanager_streaming into the BigQuery DataSet name.
We recommend using the ddmanager_streaming name. If you want the data to stream into another DataSet, specify its name instead of ddmanager_streaming. Use only Latin letters and underscores.
Select the time zone. For example, for all reports to be generated according to Moscow time, select “+03:00”.
By default, DDMStreaming sends a certain set of variables to BigQuery. These variables are sufficient for most data analysis tasks. If you do not have enough variables, you can send custom variables along with each event.
Similarly to custom dimensions, SegmentStream can pass custom metrics.
There is a big difference between metrics and parameters. A metric is a quantitative value, a number (an integer, a fractional number, a time). Parameters are data attributes. All metrics (numeric data) are calculated in the parameter sections.
context.device.model STRING Model of the device. Irrelevant for “desktops”.
context.device.vendor STRING Device manufacturer. Irrelevant for “desktops”.
event.cart.lineItems RECORD Description of goods in the cart and their quantity.
event.cart.subtotal FLOAT The total cost of the cart, not including shipping and discounts applied to the cart.
event.cart.total FLOAT The total cost of the cart, including shipping and discounts applied to the cart.
event.listing.currentPage INTEGER The number of the listing page on which the user is located.
event.listing.pagesCount INTEGER Number of pages with goods.
event.listing.resultCount INTEGER The number of all products in the category or the number of all products found by the search query.
event.listing.sortBy STRING The value by which the user has sorted the list.
event.transaction.lineItems RECORD Description of goods in the transaction and their quantity.
event.transaction.subtotal FLOAT The total cost of the cart, not including shipping and discounts applied to the cart.
event.transaction.total FLOAT The total cost of the cart, including shipping and discounts applied to the cart.