Quiriz connectors: every dataset and metric definition
16 read-only connectors that refresh daily, and 252 metric definitions written down so every answer uses the same one. Each connector page shows exactly how its metrics are calculated.
All connectorsHow definitions workCross-source metricsYour ownGood pairsFiles and folders
All connectors
Store and payments
ShopifyBeta
9 datasets · 28 metrics
Bring in orders, line items, refunds, a sales ledger that matches Shopify reports, products and customers, plus variant cost history and contribution margin inputs.
WooCommerceBeta
6 datasets · 10 metrics
Bring in orders, net sales, refunds, products and stock, and new versus returning customers.
StripeBeta
7 datasets · 20 metrics
Bring in payments, refunds, fees and payouts that match the Stripe Balance report, plus subscriptions and MRR by month.
KlaviyoBeta
4 datasets · 13 metrics
Bring in email and SMS revenue by day, campaign and flow results, and list growth.
Advertising
Google AdsBeta
7 datasets · 30 metrics
Bring in campaign, ad group and keyword performance, plus search terms, impression share, quality score parts and device performance.
Meta AdsBeta
7 datasets · 20 metrics
Bring in Facebook and Instagram campaign, ad set and ad performance, plus video hook and hold rate, reach and frequency, creative, and age, gender and placement breakdowns.
Microsoft AdvertisingBeta
3 datasets · 9 metrics
Bring in Microsoft (Bing) campaign, ad group and ad performance.
Web and product analytics
Google AnalyticsBeta
3 datasets · 8 metrics
Bring in GA4 sessions, users, key events and revenue by day, channel and landing page.
Google Search ConsoleBeta
3 datasets · 5 metrics
Bring in Google search clicks, impressions and positions by day, query and page.
Bing Webmaster ToolsBeta
4 datasets · 7 metrics
Bring in Bing search clicks, impressions, queries, pages and crawl stats. and keeps up to 25 months of history.
PostHogBeta
7 datasets · 19 metrics
Bring in PostHog traffic, signups, activation, retention and feature usage by day, channel and page.
Sales and CRM
HubSpotBeta
8 datasets · 24 metrics
Bring in deals, contacts, companies, stage history, a daily pipeline snapshot, support tickets, marketing emails and campaigns.
SalesforceBeta
7 datasets · 17 metrics
Bring in leads, opportunities, stage history, accounts and campaigns. Needs Salesforce Enterprise edition or above; your Salesforce admin installs the Quiriz package once.
Finance and time
QuickBooksBeta
5 datasets · 12 metrics
Bring in the profit and loss and balance sheet by month, the general ledger, and open invoices and bills. Matches QuickBooks reports.
HarvestBeta
6 datasets · 14 metrics
Bring in hours, billable and unbilled amounts, utilization, invoices, project budgets and expenses.
Engineering
How definitions work
A number is only as consistent as its definition. When you connect a tool, Quiriz imports its data as datasets and adds a definition for each common metric to Company Context: which dataset it reads, the column it totals, any filter, and the date that decides which period a row belongs to.
- One definition everywhere. The app, Slack and the six Office and Google add-ins all use it, so “win rate” is the same number in a deck and in a cell.
- Editable. An admin can change any definition. A refresh never overwrites one that someone has changed.
- Assumptions are marked. Where the data does not hold a figure, such as Shopify shipping cost, the definition starts with a stated assumption you replace with your own rate.
- Names line up across tools. Ad platforms use the same metric names (Google Ads spend, Meta Ads spend, Microsoft Ads spend), so comparisons across platforms are like for like.
Cross-source metrics
Some questions need two connectors: what a new customer costs needs spend from the ad platform and new customers from the store. Quiriz adds these metrics for you once both sides are connected.
| Metric | How it is calculated | Needs | Notes |
|---|---|---|---|
| Meta Ads nCAC | Meta Ads spend ÷ New customers | Shopify + Meta Ads | Meta Ads spend per new customer: Meta Ads spend divided by New customers in the same period. |
| Meta Ads aMER | New customer net sales ÷ Meta Ads spend | Shopify + Meta Ads | First-order net sales per Meta Ads dollar: New customer net sales divided by Meta Ads spend in the same period. |
| Google Ads nCAC | Google Ads spend ÷ New customers | Shopify + Google Ads | Google Ads spend per new customer: Google Ads spend divided by New customers in the same period. |
| Google Ads aMER | New customer net sales ÷ Google Ads spend | Shopify + Google Ads | First-order net sales per Google Ads dollar: New customer net sales divided by Google Ads spend in the same period. |
| Microsoft Ads nCAC | Microsoft Ads spend ÷ New customers | Shopify + Microsoft Advertising | Microsoft Ads spend per new customer: Microsoft Ads spend divided by New customers in the same period. |
| Microsoft Ads aMER | New customer net sales ÷ Microsoft Ads spend | Shopify + Microsoft Advertising | First-order net sales per Microsoft Ads dollar: New customer net sales divided by Microsoft Ads spend in the same period. |
| Contribution margin before ads (actual fees) | Net sales − Cost of goods sold − Shipping and fulfillment cost − Payment processing fees | Shopify | Net sales minus cost of goods sold, shipping and fulfillment (assumption) and the Shopify Payments fees actually charged. Fees of other gateways are not included. |
| Break-even MER (actual fees) | Net sales ÷ Contribution margin before ads (actual fees) | Shopify | Net sales per ad dollar at which ad spend uses up the whole contribution margin before ads (actual fees). Above it ads add profit, below it they lose money. |
| Blended nCAC | (Meta Ads spend + Google Ads spend) ÷ New customers | Shopify + Meta Ads + Google Ads | Meta Ads and Google Ads spend per new customer. |
| Blended aMER | New customer net sales ÷ (Meta Ads spend + Google Ads spend) | Shopify + Meta Ads + Google Ads | First-order net sales per paid ad dollar across Meta Ads and Google Ads. |
| Blended MER | Net sales ÷ (Meta Ads spend + Google Ads spend) | Shopify + Meta Ads + Google Ads | Marketing efficiency ratio: Shopify net sales per paid ad dollar across Meta Ads and Google Ads, in the same period. Net sales are Shopify's own, not what the platforms report. |
- They appear on their own. Quiriz adds each one to Company Context once the datasets it needs are connected. Nobody has to write the formula.
- Shopify is the source of truth for customers and sales. The ad platforms contribute spend only, not the revenue they attribute to themselves.
- They line up on time. Each part is totaled over the same window, so you can ask for a month, a quarter or a monthly trend. They do not break down by product, channel or campaign, because Shopify’s columns and an ad platform’s are not the same dimension.
- Guest checkouts count in neither New customers nor New customer net sales, so nCAC reads high for a store with many guest first orders.
- Spend stays in the ad account currency. No currency conversion is done.
- A Blended metric names its platforms. With exactly Meta and Google it is “Blended MER”; with another set, the platforms are in the name, so a metric never changes meaning when you connect another platform.
Your own cross-source metrics
An admin can define a metric from metrics on different datasets, in Company Context, the same way as any other definition. Quiriz totals each part over the same period and does the arithmetic. Some examples, using the metric names the connectors add:
| Example | Formula | Needs |
|---|---|---|
| Pipeline per ad dollar | Closed-won revenue ÷ (Google Ads spend + Meta Ads spend) | HubSpot + Google Ads + Meta Ads |
| Books against the store | Revenue − Net sales | QuickBooks + Shopify |
| Revenue per tracked hour | Revenue ÷ Harvest hours | QuickBooks + Harvest |
| Signups per search click | PostHog signups ÷ Search Console clicks | PostHog + Google Search Console |
Breaking it down needs a shared dimension. By default a cross-source metric answers for a period or a trend over time. To break it down by something else, such as channel or client, an admin maps a Dimension in Company Context: one column in each dataset that means the same thing, for example the UTM source on store orders and the platform on ad spend. The values have to match across the two columns, and Quiriz checks that they overlap when the Dimension is saved. A metric can be broken down by a Dimension only when every dataset it uses has that Dimension mapped.
Connections that work well together
- Shopify + Meta Ads: New-customer cost and return on Meta. Meta Ads nCAC and aMER are added for you: Meta spend against Shopify’s new customers and their first-order net sales.
- Shopify + Google Ads: New-customer cost and return on Google. Google Ads nCAC and aMER, the same pair for Google spend.
- Shopify + Microsoft Advertising: New-customer cost and return on Microsoft. Microsoft Ads nCAC and aMER, the same pair for Microsoft Advertising spend.
- Shopify + Meta Ads + Google Ads: Blended MER across ad platforms. With Meta and Google both connected, Blended nCAC, aMER and MER divide Shopify’s figures by the combined spend.
- Shopify + Klaviyo: Email and SMS revenue against store sales. Klaviyo flow and campaign revenue next to Shopify net sales, and why the two never match. Read the guide.
- Shopify + Google Analytics: Store revenue against analytics revenue. Why Shopify and GA4 disagree on revenue, and how to line them up by day. Read the guide.
- WooCommerce + Google Analytics: WooCommerce against GA4. The same reconciliation for a WooCommerce store. Read the guide.
- Stripe + Google Analytics: Payments against traffic. Stripe revenue next to GA4 sessions and key events. Read the guide.
- PostHog + Stripe: Signups to revenue. PostHog signups and activation next to what Stripe collected. Read the guide.
- QuickBooks + Stripe: Burn multiple. Net burn from the books against net new ARR from billing. Read the guide.
- QuickBooks + Shopify: Books against the store. QuickBooks Revenue is the books; Shopify Net sales is the store’s own figure. Compare them by month to find what has not been booked.
- Harvest + QuickBooks: Client profitability. Fees from the books, hours from Harvest, margin per client. Read the guide.
- Google Ads + Google Analytics: Ad conversions against analytics. Why Google Ads and GA4 count conversions differently. Read the guide.
- Meta Ads + Google Ads: Meta against Google. ROAS by platform on the same basis, because the metric names line up across ad platforms. Read the guide.
- Google Search Console + Bing Webmaster Tools: Google and Bing search. Clicks, impressions and position from both search engines side by side. Read the guide.
- HubSpot + Google Ads + Meta Ads: Pipeline per ad dollar. HubSpot closed-won revenue against ad spend by month, as your own cross-source metric.
Files and folders
For a tool without a connector, the data can still come in:
- Google Sheets, Google Drive or OneDrive. Most systems can export to a sheet or a folder. Share it with Quiriz once and it refreshes daily, weekly or monthly.
- Upload. Excel, CSV and text files, or PDFs and images that contain tables, by upload, email or Slack. Good for a budget, a quota sheet or anything that changes rarely.
Datasets from files have no definitions added automatically. An admin defines their metrics in Company Context, and they then work in cross-source metrics like any connector’s.
Connect a tool, ask in plain words
Try the questions on sample data with no signup, then connect your own tools read-only.
Try Quiriz free →