1. Revenue differs from your webshop's own reports
Metrara counts revenue per order in a fixed way, which can differ from the report you compare with.
WooCommerce
- Only orders with the status Processing or Completed count. Pending, on-hold, cancelled, failed and refunded orders are left out.
- Revenue is the order total: including VAT and shipping, after discounts.
- Partial refunds on a counted order are subtracted.
- An order counts on the date it was created, in your website's own time zone.
Shopify
- Cancelled orders and orders with the payment status voided, refunded or expired are left out.
- Revenue is the current order total after refunds, including VAT and shipping as Shopify records them.
- An order counts on the date it was created, in your shop's time zone.
To compare fairly:
- In your webshop report, use the same dates as Metrara and the same order statuses.
- Compare with the total including VAT and shipping, not net sales.
- Check whether your webshop report counts refunds on the refund date. Metrara subtracts them from the original order.
See WooCommerce.
2. Revenue per product or category doesn't add up to total revenue
Product and category figures are calculated differently from the order total.
- WooCommerce: revenue per product and category is net revenue from WooCommerce Analytics: after discounts, excluding VAT and without shipping.
- Shopify: revenue per product and category is the original item price times the quantity, before discounts.
- A product in two categories counts in both.
The revenue on Metrics is the order total including VAT and shipping, so it does not match the sum of the products.
3. Visitors differ from Users in Google Analytics
Visitors in Metrara is the sum of the users per day. Someone who visits on three different days counts three times. Google Analytics counts that person once for the whole period.
- Compare Sessions instead. A session counts once, so the totals are much closer.
- Or compare a single day. Visitors per day match Google Analytics.
4. Revenue per channel differs from webshop revenue
What does each channel bring in? on Metrics uses the revenue that Google Analytics measures on your website, not the orders from your webshop. Google Analytics tracking does not always record every order the same way your webshop does, and it does not apply Metrara's order status rules.
Use the revenue card for your actual revenue. Use the channel table to see the share per channel.
5. Key events differ from your number of orders
Google Analytics counts key events, which can include more than purchases. For webshops, Metrara therefore shows no Key events card on Metrics: the orders from WooCommerce or Shopify are leading.
For businesses without a webshop, you choose which events count as a lead. See Metrics.
6. Search Console clicks look too low for the last days
Search Console runs two to three days behind. The most recent days in the period are empty or incomplete until Google fills them in. When you compare with previous period, the current period then looks like a drop.
- Look at the chart: a dip on the last two or three days is the delay, not a real drop.
- Choose last 28 days or last 90 days, so the missing days weigh less.
- Check again after a few days. Metrara fetches the last 30 days every night and overwrites them with Google's completed figures.
7. Search Console average position differs
Metrara weighs the position of each day by that day's impressions. Search Console calculates the average for the period itself. The two can differ slightly. Metrara shows the position with one decimal.
8. Today's figures are low
Metrara fetches figures early in the morning. Today's figures only contain what had happened at that moment, and the period in the period bar runs up to and including today.
- Click Refresh figures to fetch the latest figures.
- Or compare periods that end yesterday in your other tool.
9. The date range doesn't match exactly
Metrara uses Dutch time (Europe/Amsterdam) to decide what "today" is. The data itself keeps the time zone of its source:
- Google Analytics uses the time zone of your Analytics property.
- WooCommerce uses the time zone of your website.
- Shopify uses the time zone of your shop.
If your property or shop uses another time zone, orders and visits around midnight can fall on a different day than in Metrara.
- Check the time zone in your Analytics property settings and your webshop settings.
- Compare full weeks or months rather than single days.
10. Percentages differ from your own calculation
The percentage compares the chosen period with the period in Compare with:
- previous period: the same number of days right before the chosen period.
- last year: the same dates one year earlier.
When the previous figure is 0, Metrara shows no percentage. Check that your own calculation uses the same periods.
11. Amounts are rounded
Revenue and ad costs on the cards are shown in whole euros. Numbers such as visitors and orders are rounded to whole numbers. Totals in your webshop or Google Ads can show cents, so small differences are normal.
12. Figures for one language don't match the whole website
A language version of a business shows only its own part of the website. Google Analytics figures are filtered by the URL path or domain of that language. For a WooCommerce shop with several languages, each language only counts its own orders. Orders without a language count for the main language.
Compare with the same filter in Google Analytics, or add up the language versions.
13. Bol.com sales are missing from revenue
Bol.com sales are shown separately under E-commerce, with amounts including VAT as Bol.com provides them. They are not added to your webshop revenue on Metrics.
14. Figures changed after a few days
Metrara fetches the last 30 days again every night and replaces the stored figures. Late corrections in your source then show up in Metrara, for example Search Console filling in days, an order that was refunded or cancelled, or Google Analytics processing late data.
This is expected. Figures older than 30 days are not fetched again every night, so they stay as stored.