Skip to main content

​
Marrow data sources

Marrow connects your store and advertising accounts, syncs a curated set of business tables into your Marrow data layer, and makes that data available to AI platforms (via OAuth or MCP), Data Explorer, and related tools. After you authorize a Connector, Marrow obtains read-only access, extracts data from the platform APIs, normalizes it into a consistent schema, and keeps it updated through scheduled syncs. See Data Fetch Periods for how often refreshes run. The full list of tables and columns for your connections is in Data Schema (also reachable from Data Explorer).

​
Which platforms does Marrow support?

Marrow’s Integrations cover the store and ad platforms below. Some are actively synced into the Marrow data layer today; others are available or expanding—you can connect them in Integrations as coverage rolls out. Always check Data Schema for the tables currently available on your account.

​
Actively synced into Marrow Data

These platforms have ongoing ETL into Marrow tables:

​
Available or expanding

These Integrations appear in Marrow’s product lineup. Connect them from Integrations when offered for your account; table-level sync coverage may still be rolling out. Use Data Schema to confirm what is stored for you—do not assume every UI connection already has a full daily table set.

​
What kinds of business data does Marrow include?

Across actively synced platforms, Marrow focuses on operator-ready categories such as:
  • Sales & traffic — orders, ASIN- or product-level sales, sessions, conversion-oriented metrics
  • Inventory & logistics — FBA / warehouse health, shipments, returns where the platform provides them
  • Advertising — campaign structure and daily performance for Amazon Ads and Google Ads
  • Finance — settlements, fees, and related money movement on supported Amazon Seller flows
  • Catalog & listings — products, attributes, and listing state
  • Web & search analytics — GA4 daily metrics and Google Search Console performance
  • Vendor operations — POs, shipments, and vendor reports for Amazon Vendor
Ultra-high-volume, low-signal slices (for example Google Ads hourly click or campaign hourly stats) are intentionally out of scope so schemas stay usable and row costs stay predictable.

​
Why does Marrow curate endpoints and reports?

Store and ad platforms expose hundreds of reports and endpoints. Many overlap, change often, or return shapes that are hard to use in analysis or AI tools. Marrow selects the sources that map to real seller and advertiser workflows, normalizes field names and keys, and stores them in PostgreSQL-backed tables you can query through MCP and AI platforms. Related concepts—orders and settlements, ads and sales, listings and inventory—are aligned so you spend less time cleaning data yourself.

​
Request more data sources

We keep adding platforms, reports, and tables. If you need a source or metric that is missing, contact Marrow support and tell us which platform, account type, and business question you are trying to answer.