Skip to main content
Snowplow is a behavioral data platform. You run the pipeline, and it loads enriched first-party events into a warehouse. SourceMedium reads those events and uses them in funnel and multi-touch attribution reporting. There is no API key. Your Snowplow pipeline writes enriched events to BigQuery. SourceMedium reads the event table. Snowplow event schemas are defined per brand rather than fixed by the vendor, so the mapping from your events to SourceMedium’s funnel events is collected during setup. Plan requirement: New connections require Pro or Enterprise. Existing connections remain available on Foundation. See Foundation and Pro.
Sign in to SourceMedium, open your store, then choose Data sources → Connect data source and select the platform. You need an Admin or Editor workspace role.After you connect explains the first sync and connection statuses.

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.

Plan requirements

To add a new connection on Foundation, ask a workspace admin to upgrade to Pro. In Connect, the source shows Requires Pro and links to your plan details. If your workspace already has this source connected, you can continue using and managing it on Foundation.

Pro: self-serve BigQuery loader

Pro delivers a dedicated BigQuery project you administer. Connect shows the project ID. Set up the loader in Snowplow Console pointed at that project, then select and verify its tables in SourceMedium.

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

Select data for this store only. If the export contains multiple stores, first create a BigQuery view that filters to this store (for example, by your Snowplow app_id or RudderStack store property). SourceMedium assigns the selected rows to the store you are configuring. Each table can belong to only one store.After the first load, choose Find my datasets in SourceMedium and select your dataset and event table. Map the event ID, event timestamp and loaded timestamp. Both timestamps must be BigQuery TIMESTAMP columns. Use load_tstamp as the loaded timestamp. It records when the row reached BigQuery, so events that load late are still picked up. collector_tstamp does not do that. Map optional visitor, session, page, order, revenue and campaign columns when available. Map Snowplow’s domain_sessionid as the session ID. SourceMedium uses it directly.Enter the exact event names for page view, add to cart, begin checkout, purchase and any other supported reporting events. Nested or conditional events need a BigQuery view exposing the selected columns and event names as ordinary columns. Choose Verify and save source to check read access and save the mapping.A successful check confirms read access only. It does not mean your events are in reports yet. The connection shows Awaiting first data until SourceMedium confirms data from it. Existing historical events remain available. You can’t change the event ID or event timestamp column after saving, because that would duplicate events already in reporting. Contact SourceMedium to change them.

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? Open Configure warehouse source from the connection and check the table, column and event mappings. Event names are case-sensitive.
  • Table too large to check? A view that would scan more than 10 GB can’t be checked. Select the underlying table, or a view that reads less data.
  • Resumed a paused source? SourceMedium stops reading a source when it is paused. After you resume it, the connection shows Setting up until you open Configure warehouse source and choose Verify and save source. Events already in reporting stay.
  • 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.