Ecommerce integration
Turn store orders, revenue, customers, and refunds into governed ecommerce reporting.
What you can do with Shopify in Maven
Maven connects Shopify and models orders, products, customers, refunds, and discounts into governed ecommerce metrics. Track orders, net revenue, AOV, units, and refunds, break revenue down by customer type or order status, and tie store performance back to the ads and email that drove it.
What you can measure
Maven keeps Shopify numbers consistent across dashboards, reports, and answers so the team is not debating which spreadsheet is right.
Count of orders
Gross revenue from orders
Net revenue from orders
Discounts from orders
Refunds from orders
Units sold from orders
Average order value from orders
Orders represented by the order-level ecommerce fact
Gross revenue at order grain
Net revenue at order grain
Refund amount at order grain
Units sold at order grain
Orders not marked cancelled in the canonical order fact
Orders marked cancelled in the canonical order fact
Order subtotal before tax shipping discounts and refunds
Order subtotal before tax shipping discounts and refunds
Seller-funded discounts on TikTok Shop orders
Platform-funded discounts on TikTok Shop orders
Distinct SKU counts reported on TikTok Shop orders
Items represented on TikTok Shop orders
Gross revenue on TikTok Shop orders
Line items represented across canonical orders
Tax amount collected on order-level ecommerce rows.
Shipping amount charged on order-level ecommerce rows.
Product-listing impressions reported by Google Merchant Center
Product-listing clicks reported by Google Merchant Center
Product-listing conversions reported by Google Merchant Center
Product-listing conversion revenue reported by Google Merchant Center
Gross product revenue across commerce and shopping product rows
Units sold for the product at daily grain.
Line-level product discounts.
Net product revenue after line-level discounts.
Distinct orders containing this product.
Distinct customers acquired in the cohort month. Repeated on every offset row of the cohort — only valid within a single months_since_first_order slice.
Distinct cohort customers who placed an order at this month offset. Summing across offsets yields customer-months, not distinct customers.
Orders placed by the cohort at this month offset.
Gross revenue (order total price) from the cohort at this month offset.
Net revenue (gross revenue minus refunds) from the cohort at this month offset.
Running gross revenue for the cohort from month 0 through this offset. Level, not a flow — do not sum across offsets.
Running sum of active_customers for the cohort from month 0 through this offset (customer-months; can exceed cohort_size). Level, not a flow — do not sum across offsets.
Paid media spend attributed to a geo region by the ad platform
Business revenue by geo region from KPI sources
Platform-reported conversion value from regional paid-media rows
Orders shipped to a geo region (Shopify)
Web sessions from a geo region (GA4)
Ad impressions served in the region.
Ad clicks from the region.
Platform-reported conversions from the region.
Web users from the region (GA4 rows; null for Shopify).
Weekly ad spend by region from the geo spend-response panel (summed across platforms and campaigns)
Weekly platform-attributed conversions by region from the geo spend-response panel
Weekly total business orders by region from the geo spend-response panel (single KPI source platform per workspace)
Weekly orders not attributed by ad platforms (total orders minus platform-attributed conversions) — descriptive correlation input; not a causal measure
Baseline-relative, cross-region demeaned weekly spend difference. Analysis aid for region-week scatter/correlation views — only meaningful at region x week grain or as an intentional rollup; correlation, not causation
Baseline-relative, cross-region demeaned weekly unattributed-orders difference. Analysis aid for region-week scatter/correlation views — only meaningful at region x week grain or as an intentional rollup; correlation, not causation
Prior week's spend delta for the same region (1-week lag). Analysis aid for lagged region-week scatter/correlation views — only meaningful at region x week grain or as an intentional rollup; correlation, not causation
Questions you can ask
Maven’s agent answers in plain language with the right metric definitions applied automatically. These are real, verified questions it can run today.
How many ecommerce orders did we get per week over the last 12 weeks?
Show ecommerce refunds by platform
Show cancelled orders by financial status
Show order discounts by customer type
Report templates
Use Shopify reporting templates to see what needs attention, what can be trusted, and which optional fields need cleanup before the next review.
Map paid delivery and business outcomes by country, state, and region using the geographic sources available in the workspace.
Requires at least one governed geo-level paid-delivery or regional-outcome source. Cross-source comparisons appear only when compatible geography and date coverage overlap.
Compare regional paid-media movement with non-platform outcome movement over time without presenting correlation as causal lift.
Requires overlapping geo-level paid-media and governed outcome history. It is descriptive correlation, never an incrementality result.
How it works
No SQL, no warehouse setup, no data engineer. Connect the source, then Maven models the fields needed for the first trusted workflow.
Authorize or configure Maven from the Data Sources screen, then pick the account and workspace to sync.
Maven pulls your Shopify data (11 objects) and models it into governed, conformed tables, no SQL, warehouse, or pipeline setup required.
Ask questions in natural language with the Maven agent, drop the metrics into dashboards, set alerts on what matters, and schedule deliveries to your team.
What Maven syncs from Shopify
Works well with
FAQ
Maven exposes 57 governed Shopify metrics, including Orders, Gross Revenue, Net Revenue, Ecommerce Discounts, Ecommerce Refunds and Units Sold (Ecommerce), each defined once so it means the same thing in every report.
You can break Shopify metrics down by Order Number, Source Timezone, Cancel Reason, Financial status, Fulfillment status, Is Test, Taxes Included and Payment Gateway Names, and more.
Yes. Shopify reports alongside sources like Facebook Ads, Google Ads, Klaviyo and Google Analytics 4. Maven models every source into one governed layer, so you can blend them in a single dashboard, report, or question.
Maven syncs Shopify automatically: a fast first source pull after connecting, then scheduled refreshes that keep reports current. The last successful sync time is always visible, so you know the source data is fresh before it feeds a trusted reporting workflow.
Yes. Because Shopify orders sit in the same governed layer as your ad spend and email sends, you can compare revenue against channel spend and report blended ROAS and customer acquisition cost.
Yes. Maven connects to Shopify over its official OAuth flow, no password sharing, stores access tokens encrypted, and pulls read-only reporting data into a governed warehouse you control.
Bring one recurring report, disputed metric, or client workflow. We'll show where the time goes, what can be trusted now, and how Maven would improve it.
We'll review the workflow behind one client report
You'll see what Maven can own across data, QA, and delivery
No pitch deck. No pressure. 20 minutes.
