DataStream-Model 2 - BigQuery Data Share [Analytics Hub] Setup Guide
Updated
Sprinklr DataStream Model 2 delivers your contact centre data directly into your own BigQuery Project using Google's secure AnalyticsHub Data Sharing.
No data is copied or moved outside the governed sharing flow, Sprinklr publishes a live, read-only listing that you subscribe to, and your teams can query it like a native BigQuery database.
Note: This guide explains the information Sprinklr needs from the customer and the customer-side steps required to subscribe to Sprinklr’s BigQuery Analytics Hub Listing.
Section 1: Provide Your BigQuery Details
Before Sprinklr can add you as a subscriber to our BigQuery Analytics Hub Listing, we need a few details from your BigQuery administrator to configure the Data Share. Sprinklr will create the listing and grant access based on the information you share below.
# | What Sprinklr Needs | Details / Where to Find It |
1 | Destination GCP Project ID | The project on your side where the linked dataset should land. Available in the Google Cloud Console → Project Selector (top navigation bar). |
2 | BigQuery Region | The region you will consume the data from. This helps us confirm regional alignment and, if needed, route you via a cross-region replica. Found in BigQuery Console → Dataset Info. |
3 | Subscriber Identity (one of) |
|
Section 2: Customer-Side Setup & Activating Your Data Share
Once Sprinklr confirms that your subscriber principal (Google Group or Service Account) has been added to our BigQuery Analytics Hub Listing, please follow the steps below to subscribe to the listing and make the data available to your team.
Choose the path that matches the subscriber identity you shared with Sprinklr:
Option A: Google Group → use the Google Cloud Console (browser UI)
Option B: Service Account → use the gcloud CLI or Terraform
Step 1: Open BigQuery Studio in Your Destination Project
Sign in to the https://console.cloud.google.com using an identity that is either:
A member of the Google Group you shared with Sprinklr, or
Authorised to impersonate the Service Account you shared.
From the project picker at the top of the page, select the destination GCP project you shared with Sprinklr. This is where your linked dataset will appear.

Step 2: Locate the Sprinklr Listing in Analytics Hub
From the left navigation pane, open Analytics Hub.
If prompted, click Enable to activate the Analytics Hub API.
Note: If your user is not able to enable this, please contact the internal BigQuery POC/Admin, who would have access to enable it.

Once enabled, click Search listings.

The Sprinklr listing will appear in the results.
Can't find the Sprinklr listing? Verify the following before proceeding:
Ensure you are signed in using an account that is a member of the Google Group that was provided to Sprinklr during the setup process.
Confirm that you have selected the correct destination GCP project where the linked dataset is expected to be created.

If both conditions are met and the listing is still not visible, contact your BigQuery administrator or your Sprinklr implementation team for further assistance.
Step 3: Subscribe to the Sprinklr Listing
Option A: Google Group (Browser UI)
Click the Sprinklr listing tile to open its details page.
Review the listing description, then click Subscribe (top-right).
In the Subscribe dialog, provide:
Destination project
Pre-filled with your current project. Update if needed.
Linked dataset name
A name of your choice — e.g.,
sprinklr_data. This is how the dataset will appear in your BigQuery explorer.
Click Save. Your linked dataset will be created within a few seconds.
Choosing the Right Region Sprinklr publishes each listing in a primary region (where the source dataset lives) and may also offer replica regions (read-only copies in other geographies).
When subscribing, select the region that matches where your existing BigQuery datasets reside. BigQuery requires both sides of a JOIN to be in the same region — subscribing in your data's region allows you to join sprinklr_data with your tables directly, with no cross-region copy needed.


Option B — Service Account (CLI / Terraform)
Your GCP administrator (with permission to impersonate the Service Account) should run the following command:
gcloud --impersonate-service-account=<sa-email> \
bigquery analytics-hub listings subscribe \
--listing=<listing-id-shared-by-sprinklr> \
--location=<region-shared-by-sprinklr> \
--destination-project=<your-destination-project> \
--destination-dataset=sprinklr_data
Sprinklr will share the exact --listing resource path and the corresponding --location (primary or closest replica region) once your Service Account has been added as a subscriber.
The subscribing user must have the following permission:
Note: bigquery.datasets.create
Step 4: Verify the Linked Dataset
Return to BigQuery Studio.
In the Explorer pane, expand your destination project.
You should see your new dataset (the name chosen in Step 3) with a linked icon next to it.
Expand the dataset to view the tables and views Sprinklr has published.

Step 5: Grant Your Team Read Access
By default, only the subscriber identity (the Group member who clicked Subscribe, or the Service Account) can query the linked dataset. To allow your wider team to query it, grant BigQuery Data Viewer access.
Via Browser
Click the ⋮ (three-dot menu) next to the linked dataset → Share → Manage permissions.
Click Add principal and enter the email of the user or group.
Assign the role BigQuery Data Viewer and click Save.
Via CLI
gcloud projects add-iam-policy-binding <your-destination-project> \
--member="group:analyst-team@<your-domain>.com" \
--role="roles/bigquery.dataViewer"
Step 6: Query the Linked Dataset
Your analysts can now open a new query tab in BigQuery Studio and query the dataset just like any other.
Note: No data is copied into your project, queries read directly from Sprinklr’s published views. There is no egress cost; you only pay for the BigQuery compute (slots) used by your queries.
Ongoing Access Management
Add an analyst | Grant roles/bigquery.dataVieweron the linked dataset (Step 5). |
Remove an analyst | Revoke the same role, or remove the user from the Google Group used as the subscriber principal. |
Unsubscribe | Open the linked dataset → ⋮ menu → Delete. The dataset is removed from your project. Sprinklr's source data is unaffected. |
Section 3 - What Happens Next?
Once you share the Section 1 details with Sprinklr, we will publish a dummy dataset to your listing to validate the connection end-to-end.
After joint confirmation that the test dataset is accessible from your side, Sprinklr will provision and share the actual production listing.
Intended Use and Prohibited Uses
DataStream is intended solely to support operational efficiency, service delivery, business intelligence, and process optimisation. The product is not designed or intended for employee monitoring, workplace surveillance, performance evaluation, profiling of individuals, or making decisions that materially affect an individual's employment, rights, opportunities, or access to services.
DataStream does not process biometric data for the purpose of identifying individuals and does not perform emotion recognition, affect detection, or emotion inference in the workplace.
Customers must not use DataStream in a manner inconsistent with these intended purposes and remain responsible for ensuring compliance with applicable legal and regulatory requirements as well as with Sprinklr's Acceptable Use Policy.