Skip to main content
The BigQuery integration is available by invitation only. Contact Outpost to request access.
Outpost’s BigQuery integration exports your member, subscription, and analytics data to Google BigQuery, enabling advanced analysis and custom reporting.

​
What gets exported

Outpost populates three BigQuery tables:

​
Setup

1

Create a Google Cloud project

If you don’t have one, create a project in Google Cloud Console.
2

Create a BigQuery dataset

In BigQuery, create a dataset to receive Outpost data. Note the dataset ID.
3

Create a service account

Create a service account in Google Cloud with BigQuery Data Editor and BigQuery Job User roles. Download the credentials file (JSON format).
4

Request access

Contact Outpost to request the BigQuery integration for your site. Outpost enables it for you, then it appears on the Integrations page under Big Query.
5

Connect in Outpost

Go to Integrations and Core Connections → Integrations and open Big Query. Upload the credentials file, enter your project ID and dataset name, then enable the data sources you want to export (Stripe, Ghost, and/or Plausible) and optionally set a table name for each.
6

Data starts flowing

Once connected, Outpost begins writing rows to BigQuery as members change. No manual export step is required.

​
How exports run

Exports are event-driven. Whenever a member is created or updated in Ghost or Stripe, Outpost writes that member’s current row to the corresponding BigQuery table. Plausible analytics (the previous day’s stats) are uploaded once a day. Data flows continuously as members change: there is no batch “export now” step.

​
Use cases

  • Custom dashboards in Looker, Data Studio, or Tableau
  • Cohort analysis across multiple months
  • Revenue forecasting with subscription data
  • Joining Outpost member data with ad server or analytics data
  • Cross-publication reporting for multi-property publishers

​
Schema

Each table is created with a fixed schema the first time Outpost writes to it. Existing tables are not altered automatically if the export schema later changes, so new fields won’t appear on a table that already exists.