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
Snowplow’s loader asks for your cloud project and region, the dataset name, an allow-list entry for Snowplow’s IP addresses, and a service account with permission to write to the dataset. 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 or write service account yourself.- In SourceMedium, open Connect a data source and find Snowplow.
- Fill in the form: Console organization, pipeline name, and which of your events are page view, add to cart, checkout, and purchase. If events already land in BigQuery, include that project and dataset.
- Click Request integration. That opens a support ticket with those details. The card shows Setting up until SourceMedium creates the destination, applies the mapping, and starts reading events.
Pro: self-serve BigQuery loader
Pro delivers a dedicated BigQuery project you administer. Connect shows the project ID. You set up the loader in Snowplow Console pointed at that project, then click Connect so SourceMedium can start reading the tables.What you need
- Access to Snowplow Console for your pipeline
- Access to your dedicated BigQuery project (Connect shows the project ID)
How to connect
1
Create a dataset
In your dedicated project, create a dataset for enriched events (for example
snowplow).2
Set up the loader connection in Snowplow
In Snowplow Console, go to Settings → Connections, select Set up connection, choose Event loading, and pick BigQuery. Enter the project ID from Connect, the region, and the dataset name. Allow-list Snowplow’s loader IPs and grant a service account BigQuery Data Editor on the dataset. Snowplow’s BigQuery guide is the vendor procedure.
3
Deploy the destination
Go to Destinations → Warehouses and lakes, click Add destination, select BigQuery, and choose the pipeline, the connection from the previous step, and enriched events.
4
Confirm in SourceMedium
Click Connect on Snowplow in SourceMedium so we can mark the source as in setup and map your events to funnel events. Use the same event names you would put on the Foundation form: page view, add to cart, begin checkout, and purchase.
What data syncs
SourceMedium reads first-party behavioral events and keeps the ones mapped to its funnel events. Where it lands in the warehouse: obt_funnel_event_history, the same table used for GA4, RudderStack, and other tracking sources.- Only events mapped to a SourceMedium funnel event are ingested. Bespoke micro-steps with no equivalent are not carried through.
- Snowplow feeds funnel and attribution reporting, not order or catalog tables. Order data comes from your commerce platform integration.
- Because the pipeline is yours, history depth is whatever your warehouse already holds. Confirm the backfill window during setup.
Troubleshooting
- Events not appearing? Confirm the loader is active in the Snowplow Console under Destinations → Warehouses and lakes, and that events are landing in the dataset you configured.
- Missing a funnel step? Only mapped events become funnel events. If you added or renamed an event, open a support ticket so the mapping can be updated.
- Attribution looks incomplete? Snowplow captures first-party on-site events only. Combine it with your ad platform and commerce integrations for full multi-touch attribution.