• ANALYTICS • SETUP GUIDE

Understanding Rivio Checkout Customizer Analytics

By Rivio Support Team
2 min read

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.

EXPECTED SETUP TIME Varies by feature
COMPATIBILITY See requirements in this guide
TECHNICAL DIFFICULTY Zero Code Required

Analytics shows the orders and sales associated with Rivio features for the selected period. It is useful for reviewing feature usage; it does not establish how much additional revenue would have occurred without the app.

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: Read attribution and acceptance without double counting

Example setup: A selected reporting period; one completed feature-using order and one accepted but abandoned checkout upsell.

Step-by-step instructions

  1. Open Analytics and choose a clearly stated period, such as Last 30 days.

  2. Read Sales driven by this app as sales associated with orders using supported Rivio upsells, gifts, bundles, links, or discounts.

  3. Read Orders influenced as confirmed orders using at least one Rivio feature.

  4. Read Checkout upsells accepted as acceptances, which can include a checkout the buyer later abandons.

  5. Review feature rows for Orders, Revenue, and Average order value and compare the same date/currency context.

  6. Use an order containing both a gift and a bundle to demonstrate that feature sections can overlap.

  7. Record the order identifier and period for your demo; avoid summing feature revenues as unique total store revenue.

Verify the result

Test case Expected result or verification
Upsell accepted then checkout abandoned An acceptance is not a confirmed influenced order.
Completed order using gift and bundle It can appear in overlapping feature sections.
Reported sales attributed to features This is not proof that all those sales were additional revenue caused by Rivio.

Important: Ask support about refund handling and historical backfill before financial reconciliation; confirm the definitions with support before reconciling reports.

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.

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.