Skip to main content
RudderStack is a customer data platform that collects first-party behavioral events from your site and streams them to a data warehouse. SourceMedium reads those events from RudderStack’s BigQuery warehouse destination and uses them in funnel and multi-touch attribution reporting, so on-site behavior links to orders.

​
How to connect

There is no API key and no SourceMedium-hosted collector. RudderStack streams your events into BigQuery, and SourceMedium reads the event tables from that dataset.
This integration is set up with help from SourceMedium rather than in the self-serve picker. To enable it, reach out to your account manager or integrations@sourcemedium.com.
1

Enable RudderStack's BigQuery destination

In RudderStack, connect your web and mobile event sources to a BigQuery warehouse destination, following RudderStack’s BigQuery destination guide. RudderStack writes one table per event, plus its deduplicated <event>_view views.
2

Coordinate the destination with SourceMedium

SourceMedium provides the BigQuery project, dataset, and service account to point the destination at. If RudderStack already writes to your own BigQuery, share those details instead. Exchange these with your account manager or integrations@sourcemedium.com, not in public channels.
3

SourceMedium validates and syncs

Once events are landing in BigQuery, SourceMedium confirms the tables are readable, maps your events to its standard funnel events, and starts using them in funnel and attribution reporting.

​
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, such as the contact and address checkout steps, 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 shared with SourceMedium.
  • Missing a funnel step? Only mapped events become funnel events. If you need a custom event tracked, tell your account manager or integrations@sourcemedium.com 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.