06:00 UTC













Join marketing, finance, CRM, and product data inside the same warehouse.
Metrics availables
Dimensions availables
Select your Google Cloud project and BigQuery dataset. Catchr automatically prepares the destination and maps your data into analytics-ready tables.
Catchr continuously imports new and updated data into BigQuery.
Your warehouse stays fresh automatically, ready for SQL, dbt, BI tools, and AI workloads.
Open the dedicated route for each platform. Its field catalog, reporting grain, historical constraints, and warehouse use cases should be specific to that source.
Answers about available Meta Ads data, reporting cadence, history, table settings, attribution changes, and downstream joins.
Add Amazon Vendor Central as a source in Catchr, authorize it through Vendor Central, select the marketplace you want to report on, choose your fields, and connect the target Google Cloud project and dataset.
Export from a schema of 30 metrics and 34 dimensions covering ordered and shipped revenue, ordered and unfilled units, purchase orders, inventory costs, shipped COGS, vendor lead time, report level, and normalized date fields.
Amazon Vendor Central data can include sales, traffic, inventory, forecasting, and net pure product margin reports, with aggregate and ASIN sections identified by the report level field.
Yes. Keep each source in separate Big Query tables, then use SQL views or models to join them on compatible fields such as normalized date or product identifiers available in your selected data.
Forecasting provides Amazon’s latest forecast snapshot and uses the forecast generation date for normalized date fields, while sales, traffic, inventory, and net pure product margin reports use the requested date window.
If your selected schema contains an eligible date field, you can configure that field as the optional date partition for the destination table. Catchr does not configure table clustering or design your downstream analytical models.
Yes. Configure the historical period supported by the source for the initial import, then keep the table updated with recurring exports. The available range is determined by the source API and the settings of your job, not an unlimited-history promise.
Our teams is always here to responds to any question you could have about our data connector.
Connect your accounts, choose the fields then send the configured export to your BigQuery project.