Shopify (sample data)
Commerce
Shopify (sample data) data, published as Shopify (sample data) publishes it. Ingest delivers this data to a data warehouse you own as 3 tables, and updates it on the schedule you choose. There is no code to write and nothing to install.
What you get
| Table | Each row is |
|---|---|
customerscustomers | Customers with their location, marketing consent, order count and lifetime spend. |
ordersorders | Every order with its totals, discount code, UTM attribution and shipping location; line items land in a child table (orders__line_items) joined on _ingest_root_id. |
productsproducts | The product catalog: title, type, vendor, price and compare-at price. |
How it works
- Choose Shopify (sample data). The data is public, so there is nothing to sign in to.
- Pick where it goes. BigQuery, Snowflake, Databricks, Redshift and 10 more, in an account you own.
- Pick a schedule. Daily is the default, and weekly and monthly are there too.
- Ingest runs it from then on. If a run fails, your dashboard shows which table and why.
Questions
- Do I need an account with Shopify (sample data)?
- No. The data is public, so there is nothing to sign up for and nothing to paste in.
- Which warehouses can Shopify (sample data) data go to?
- Amazon S3, Google Cloud Storage, Azure Blob Storage, Apache Iceberg, Ingest Managed Lakehouse, MotherDuck, Postgres, Amazon Athena, Databricks, Redshift, BigQuery, ClickHouse, MySQL / generic SQL and Snowflake, in an account you own.
- How fresh is the data?
- As fresh as your schedule: daily by default, or weekly or monthly. Schedules as often as every 15 minutes are on the Enterprise plan.
- Will running it again create duplicate rows?
- No. Each row is stored once, by its key: when a run reads a row that is already there, it replaces that copy instead of adding a second one.
- Do I need to write code?
- No. Ingest builds, runs and maintains the connector. Someone with access to your warehouse connects it once, following a short guide.
For your data team: technical reference
Connector sample_shopify, version 0.1.0, a REST source, status beta, authentication none.
Vendor documentation: https://2k247ci8d7.execute-api.us-east-1.amazonaws.com/docs
Configuration
No configuration required.
Resources
| Resource | Status | Plan | Write | Primary key | Overrides |
|---|---|---|---|---|---|
customersCustomers with their location, marketing consent, order count and lifetime spend. | beta | full | merge | customer_id | - |
ordersEvery order with its totals, discount code, UTM attribution and shipping location; line items land in a child table (orders__line_items) joined on _ingest_root_id. | beta | full | merge | order_id | - |
productsThe product catalog: title, type, vendor, price and compare-at price. | beta | full | merge | product_id | - |
Where this lands, and what else connects
Setting up the destination is its own short guide, one per warehouse or lake: Amazon S3, Google Cloud Storage, Azure Blob Storage, Apache Iceberg, Ingest Managed Lakehouse, MotherDuck, Postgres, Amazon Athena, Databricks, Redshift, BigQuery, ClickHouse, MySQL / generic SQL, Snowflake.
Other sources Ingest connects for ecommerce teams: Shopify, Etsy, Faire, Walmart Marketplace, Walmart Connect, Mercado Libre.
- How Ingest reads a REST source
- Ingest for ecommerce teams
- The tables Ingest creates
- Every source Ingest connects
Get Shopify (sample data) data into your warehouse
Last updated .