Why Rivio Analytics Shows Zero or Differs from Shopify
What you will achieve in this guide
Follow the feature-specific setup and testing instructions below. Check the supported pages and plan requirements before activating the feature.
A zero or different analytics total can come from date range, feature eligibility, completed-versus-abandoned checkout activity, overlapping attribution, or differing report definitions. Compare a known completed order and the same reporting context.
How this feature works
Rivio reports attributed feature activity for the selected period. Sales driven by this app represents sales associated with orders using supported Rivio features; Orders influenced concerns confirmed feature-using orders. Checkout upsells accepted records acceptance and can include abandoned checkouts. Feature sections can overlap and must not be summed as unique store revenue.
Before you begin
Choose a clearly stated reporting period. Use a known completed order that actually used the feature when verifying order/revenue attribution.
Worked example: Explain a zero or mismatched analytics result
Example setup: A completed test order known to have used a Rivio feature.
Troubleshooting steps
Record the order identifier, completion time, and feature actually used.
Open Rivio Analytics and select a period including that completion time.
Distinguish an editor preview or accepted upsell from a confirmed order; neither preview nor acceptance alone proves a sale.
Check the relevant feature row and whether multiple features touched the same order.
Compare Shopify using the same date range, currency, and the closest available metric definition rather than an unrelated gross/net total.
If the order still appears missing, send support the order identifier, feature, date range, and screenshots of both reports.
Verify the result
| Test case | Expected result or verification |
|---|---|
| Order outside selected period | Widen the range before diagnosing missing attribution. |
| Upsell accepted but unpaid | Acceptance can differ from confirmed order counts. |
| Dashboard This month versus Analytics Last 30 days | Align ranges before comparison. |
Important: Do not invent a reporting-delay, refund, or backfill guarantee when the product source does not define it.
If the result is different
| Check | What it means / what to do |
|---|---|
| Zero despite a preview or accepted offer | An editor preview is not a sale; an acceptance can occur without a completed order. |
| Different from Shopify | Align date range, currency, and metric definition, and check overlapping feature attribution. |
| Known completed order still missing | Send support the order identifier, feature, selected period, and report screenshots. |
Related guides
- Understanding Rivio Checkout Customizer Analytics
- Understanding Sales Driven, Orders Influenced, and Upsells Accepted
- How to Uninstall Rivio Checkout Customizer from Shopify
Need help?
Email support@rivioapps.com with your store domain, feature name, target page, the relevant settings, and a screenshot of the actual result. Include the test cart, customer, or order details needed to reproduce the issue.
Screenshot reference
Screenshot to add: The saved settings described in this guide, with its selected conditions or scope visible.
Screenshot to add: The worked example’s actual customer result or saved Shopify record, including the relevant test inputs.
Was this article helpful?
Your feedback helps us continuously improve our setup guides and documentation.
Thank you for your feedback! Our documentation team reviews all suggestions.