Skip to main content
RudderStack is a customer data platform that collects first-party behavioral events and streams them to a warehouse. SourceMedium reads those events from RudderStack’s BigQuery warehouse destination and uses them in funnel and multi-touch attribution reporting. There is no API key. RudderStack writes event tables (and <event>_view views) into BigQuery; SourceMedium reads them. Who can self-serve: Pro, which delivers a dedicated BigQuery project you administer. On Foundation, the shared project, SourceMedium creates the destination. Use Request integration in Connect and fill in the setup details so we can finish it. See Foundation and Pro.
You connect data sources yourself in SourceMedium. Sign in to your SourceMedium account, open your store, then in the Data sources section click Connect data source and choose the platform. You need an Editor or Admin role on the store. If you have view-only access, ask an admin or editor on your team to connect it.Once it is connected, what happens next covers first-sync timing and what each connection status means.

​
Vendor documentation

RudderStack’s destination asks for a Project, Location, Staging GCS Storage Bucket Name, Namespace (the dataset), and a service account Credentials file. You cannot change the namespace later. The Pro steps below are for whoever administers your Google Cloud project.

​
Foundation: request integration

Foundation delivers a shared project, so you cannot create the BigQuery dataset, bucket, or service account yourself.
  1. In SourceMedium, open Connect a data source and find RudderStack.
  2. Fill in the form: RudderStack workspace URL, whether you already write to BigQuery, the sources to connect, and which events are page view, add to cart, checkout, and purchase.
  3. Click Request integration. That opens a support ticket with those details. The card shows Setting up until SourceMedium creates the destination and starts reading events.
You do not need to email us separately.

​
Pro: self-serve BigQuery destination

Pro delivers a dedicated BigQuery project you administer. Connect shows the project ID. You create the destination in RudderStack pointed at that project, then click Connect so SourceMedium can start reading the tables.

​
What you need

  • An active RudderStack workspace with a web or mobile source
  • Access to your dedicated BigQuery project (Connect shows the project ID)

​
How to connect

1

Create a dataset and staging bucket

In your dedicated project, create a dataset (for example rudderstack) and a Cloud Storage bucket in the same region. RudderStack stages files in the bucket before loading BigQuery.
2

Create a write service account

Create a service account with BigQuery Job User on the project, BigQuery Data Owner on that dataset (BigQuery Data Editor is enough if the dataset already exists), and Storage Object Creator plus Storage Object Viewer on the bucket. Download the JSON key. RudderStack’s BigQuery destination guide lists these roles and the equivalent custom-role permissions.
3

Add the BigQuery destination in RudderStack

In RudderStack, add a BigQuery destination on the sources you want to sync. Enter the project ID from Connect, the location, the bucket name, namespace rudderstack (or the dataset you created), and paste the JSON key into Credentials.
4

Confirm in SourceMedium

Click Connect on RudderStack in SourceMedium so we can mark the source as in setup and map your events to funnel events.

​
What data syncs

SourceMedium reads first-party behavioral events from RudderStack and maps the standard ecommerce events to its funnel events. For example: Where it lands in the warehouse: obt_funnel_event_history, the same table used for GA4, Snowplow, and other tracking sources.
  • SourceMedium reads RudderStack’s deduplicated <event>_view views, so repeated event deliveries are collapsed.
  • Only events that map to a SourceMedium funnel event are ingested. Micro-steps with no equivalent are not carried through.
  • RudderStack feeds funnel and attribution reporting, not order or catalog tables. Order data comes from your commerce platform integration.

​
Troubleshooting

  • Events not appearing? Confirm RudderStack’s BigQuery destination is active and the event tables and their <event>_view views are landing in the dataset you configured.
  • Missing a funnel step? Only mapped events become funnel events. If you need a custom event tracked, tell us in the connect form or a support ticket so it can be mapped.
  • Attribution looks incomplete? RudderStack captures first-party on-site events only. Combine it with your ad platform and commerce integrations for full multi-touch attribution.