> ## Documentation Index
> Fetch the complete documentation index at: https://docs.sourcemedium.com/docs/llms.txt
> Use this file to discover all available pages before exploring further.

# RudderStack - Integration Instructions

> Connect RudderStack first-party event data to SourceMedium through its BigQuery warehouse destination.

## Follow this integration guide to connect your RudderStack data to SourceMedium.

RudderStack is a customer data platform (CDP) that collects first-party behavioral events from your site and streams them to a data warehouse. SourceMedium reads those events directly from RudderStack's [BigQuery warehouse destination](https://www.rudderstack.com/docs/destinations/warehouse-destinations/bigquery/) and runs them through its funnel and multi-touch attribution pipelines, so on-site behavior links to orders for session-to-order and attribution analysis.

<Snippet file="connect-managed-note.mdx" />

### How it works

There is no API key or SourceMedium-hosted collector. RudderStack streams your events into BigQuery, and SourceMedium reads the event tables from that dataset.

<Steps>
  <Step title="Enable RudderStack's BigQuery destination">
    In RudderStack, connect your web and mobile event source(s) to a **BigQuery** warehouse destination, following [RudderStack's BigQuery destination guide](https://www.rudderstack.com/docs/destinations/warehouse-destinations/bigquery/). RudderStack writes one table per event, plus its deduplicated `<event>_view` views.
  </Step>

  <Step title="Coordinate the destination with SourceMedium">
    SourceMedium provides the BigQuery project, dataset, and service account to point the destination at (or, if RudderStack already writes to your own BigQuery, share those details instead). Exchange these with your account manager or [integrations@sourcemedium.com](mailto:integrations@sourcemedium.com), not in public channels.
  </Step>

  <Step title="SourceMedium validates and syncs">
    Once events are landing in BigQuery, SourceMedium confirms the tables are readable, maps your events to its canonical funnel events, and begins running them through funnel and attribution reporting.
  </Step>
</Steps>

### What data SourceMedium reads

SourceMedium reads first-party behavioral events from RudderStack and maps the standard e-commerce events to its canonical funnel events. For example:

| RudderStack event                         | SourceMedium funnel event |
| ----------------------------------------- | ------------------------- |
| `page`                                    | `page_view`               |
| `product_added`                           | `add_to_cart`             |
| `product_removed`                         | `remove_from_cart`        |
| `checkout_started`                        | `begin_checkout`          |
| `checkout_step_completed` (shipping step) | `add_shipping_info`       |
| `payment_info_entered`                    | `add_payment_info`        |
| `order_completed`                         | `purchase`                |

These land in `obt_funnel_event_history` with `source_system = 'rudderstack'` (the same unified table used for GA4, Snowplow, and other tracking sources) and feed SourceMedium's multi-touch attribution models.

### Data coverage notes

* SourceMedium reads RudderStack's deduplicated `<event>_view` views (RudderStack's BigQuery de-dup contract), so repeated event deliveries are collapsed.
* Only events that map to a canonical SourceMedium funnel event are ingested. Non-canonical micro-steps (for example, 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 whitelisted events map to canonical funnel events. If you need a custom event tracked, tell your SourceMedium team 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.