What is the BigQuery integration?
The BigQuery integration gives you direct access to your subscription program data in your own BigQuery data warehouse. You can analyze this data using SQL and combine it with other business datasets (like order history, customer behavior, or marketing performance) to unlock deeper insights into your subscription business.
The BigQuery integration is ideal if you:
Want to run custom SQL queries on your subscription data
Need to combine Skio data with other business data sources (e.g., Shopify orders, marketing analytics, inventory systems)
Use BigQuery or Google Cloud as your primary data warehouse
Have a data team or analyst who works with SQL and wants direct access to raw subscription data
Want to build custom dashboards or reports outside of Skio's analytics tools
Data refreshes every 24 hours by default, with the option to increase refresh frequency to every 4 hours (up to 6 times per day).
What kind of data is included?
All data available through code.skio.com is included in this integration, delivered as raw tables within your BigQuery warehouse. This includes subscription records, customer data, order history, and related metrics.
How to set up the BigQuery integration
To enable the BigQuery integration, reach out to your Merchant Success Manager or email success@skio.com. Skio will create and share a dataset with a user you control in your Google Cloud project.
Before we can share a dataset with you, you’ll need:
A BigQuery account
Email(s) of team members that should have access
Your service email (you can find this under IAM & Admin > Service Accounts in your Google Cloud Console)
Once the integration is set up, follow the steps below to access your data.
How to access your Skio data in BigQuery
Some steps may require your Google Cloud administrator to grant additional permissions. The Skio team can't directly modify your Google Cloud permissions, but we're happy to provide guidance.
Step 1: Verify your account has permission to run queries
Before you can query your Skio data, your account needs permission to launch jobs in BigQuery.
Confirm your organization's Google Cloud project is selected in the project dropdown at the top of the page.
.png?sv=2022-11-02&spr=https&st=2026-02-04T01%3A06%3A00Z&se=2026-02-04T01%3A20%3A00Z&sr=c&sp=r&sig=Olz4BQtP7iok7Z7FK9iZEra2uMWWfqx2j0ViYS%2B4uqY%3D)
Click SQL Query to open a new query tab.
Type
SELECT 1;into the editor and click RUN.

If the query runs successfully, you're all set. Continue to Step 2.
If the RUN button is grayed out and you see a message like "
You need permissions for this action. Required permission(s): bigquery.jobs.create," your account needs additional permissions. Ask your Google Cloud administrator to follow the instructions in How to grant BigQuery permissions (below).
Step 2: Access your Skio dataset
Once you have the proper permissions, you can connect to your Skio dataset.
In the Explorer panel on the left, click + Add.
Select Star a project by name.
In the text box, enter
largedata-380204and click Star.

The largedata-380204 project will now appear in the Explorer panel. Click the arrow to expand the project, then expand your dataset (named after your Skio store) to view the available tables. Click on any table to view its schema.

Step 3: Run queries against your Skio data
You can now write and execute SQL queries against your Skio data. For example:
SELECT * FROM `largedata-380204.your_dataset_name.Subscription`;Replace your_dataset_name with the actual name of your dataset (e.g., skio_dev_site).
Managing access and permissions
By default, Skio manages read access to your data. However, you can take control of access management:
Delegate access control: Provide Skio with a Google Group you control. You can then add or remove members from the group without contacting Skio.
Grant access to service accounts: If you need to connect batch jobs or third-party integrations (like Snowflake), share the service account name with Skio. If you've set up a Google Group, you can add the service account directly to the group.
Access data via GCP bucket: Skio can also provide your data as files in a Google Cloud Storage bucket. This can be useful for data pipelining or specific third-party integrations. Contact Skio to set this up.
How to grant BigQuery permissions (for administrators)
If a user needs permission to run queries in BigQuery, a Google Cloud administrator can follow these steps.
Unless the project is linked to a billing account, query volume will be limited by the BigQuery free tier.
Step 1: Navigate to IAM settings
Locate the user account in the list of principals.
Click the pencil icon next to their name to edit permissions.

Step 2: Add the BigQuery Job User role
Click + Add Another Role.

Search for and select BigQuery Job User.
Click Save.

The user should now have the BigQuery Job User role listed in the permissions table.
FAQ
Who pays for the data access?
Skio creates and maintains the dataset, which is shared to a user you control. Queries on this dataset are billed by Google Cloud to the user who launched the query.
How much does this feature cost?
Most merchants will pay less than $5 per month to use this feature.
For higher-volume stores or advanced use cases, the cost may be closer to $10 per month, and in rare cases could be up to $20 per month. Overall, the majority of merchants will pay under $5 per month.
What if I use a different data warehouse?
Skio can also produce a periodic export of the dataset to Google Cloud Storage as a CSV. This CSV can be ingested into any standard data warehouse. Contact your Merchant Success Manager or success@skio.com to set this up.
Are there any alerts or logs if syncs fail?
Not currently. However, you can check for issues by reviewing the timestamps of the most recent data to confirm whether syncs are running as expected.
What if I don't have access to my Google Cloud project?
Contact your Google Cloud administrator to request access or to have them complete the setup steps on your behalf.
How often is my Skio data updated in BigQuery?
Data refreshes every 24 hours by default. You can request to increase the refresh frequency to every 4 hours (up to 6 times per day). Contact your Merchant Success Manager to adjust your sync schedule.
