01
Connect
SourceMedium pulls data from your platforms directly, through connectors like Fivetran, or via Google Sheets you configure.
See all integrations →Inside the Connect stage
The end of
“can you download that CSV?”
Stop pasting exports into spreadsheets. SourceMedium connects commerce and operating systems, reconciles the differences, and delivers clean data to a maintained BigQuery foundation daily.
Why is moving data so hard?
Building your own connectors seems easy until the first API deprecation. Then it's a full-time job.
Why teams switch to SourceMedium → Maintaining a broad connector library in-house
Debugging rate limits and schema changes
Normalizing currency and timezones manually
Explaining why GA4 doesn't match Shopify
Coverage you can audit
50 integrations across commerce, marketing, and analytics, each with setup docs and known limitations.
Commerce and subscription
Connect storefront and order systems like Shopify, Amazon, Stripe, Chargebee, ReCharge, Stay AI, and Loop.
Marketing and ad platforms
Pull in spend and campaign data from Meta, Google Ads, TikTok, Amazon Ads, and other paid media platforms.
Analytics, attribution, and CRM
Bring in analytics and customer systems such as GA4, Google Search Console, HubSpot, and attribution tooling.
How data moves through SourceMedium
Every integration follows the same three-stage pipeline. Each stage has documented rules you can inspect.
02
Reconcile
Raw data is never clean. SourceMedium applies documented rules before anything reaches your reports.
- Choose financial source of truth: Shopify orders vs. payment processor vs. ad platform
- Normalize timezones and currency across all sources
- Explain GA4 vs. Shopify variance, ad platform discrepancies, and other cross-source gaps with documented reconciliation rules
03
Deliver
Trusted data lands in modeled BigQuery tables and powers dashboards backed by the same tables you query directly.
The BigQuery data foundation →Freshness expectations
The maintained platform baseline is complete through the prior day. A few sources have known lag. Connector-specific cadence and latency are documented when confirmed.
| Source type | Typical timing |
|---|---|
| Most core integrations | Complete through the prior day; some connectors refresh throughout the day. |
| Amazon Seller/Vendor and Amazon Ads | 24 to 72 hour lag can occur because of API rate limits. |
| Configuration Sheet updates | Changes applied within about 30 minutes. |
Next steps
Data movement is step one. Here's what happens after your data lands.
Ready to stop debating the numbers?
In 30 minutes, we will
-
Map your current systems and reporting gaps.
-
Show one workflow relevant to your team.
-
Outline likely fit, implementation scope, and next steps.
Book a platform walkthrough
Share a little context, then choose a time immediately after submitting.
Choose a time for your walkthrough
Loading available times...
We couldn't load available times here.
Open the scheduling calendar in a new tab. If you cannot schedule now, we will still follow up.
Open scheduling calendar