Measure the feedback workflow using the events it actually records. Delivery is not readership, a submission is not publication, and a widget click is not an order.
Keep the funnel stages separate
The collection workspace reports invitation activity and matched review submissions. Its submission rate uses completed submissions divided by sent invitations. A saved draft, a queued request, a dispatched email, and a delivered email are separate states. Do not treat each stage as a new customer or add their totals into a larger engagement number.
The overview separately reports published direct reviews, pending moderation, and unanswered feedback. A completed invitation route does not guarantee publication. Collected reviews are not new submissions from your campaign; keep them out of campaign results.
Use a clearly defined reporting period
Record store, campaign, and observation date. Give campaigns time before comparing results; participation is optional. Customer groups and timing differ, so a rate difference alone does not prove a subject line or widget caused it.
Free includes 50 invitations per calendar month in UTC, and the workspace shows the remaining allowance. Quota usage is a delivery-planning measure, not a review count. Keep the report’s timeframe explicit and do not label the currently displayed campaign totals as lifetime customer activity. Your internal worksheet can track a consistent period without changing the underlying events.
Interpret widget activity at its actual scope
The storefront area reports approximate widget loads and profile clicks for script embeds on the verified domain and its subdomains. Preview loads and iframe-only embeds are excluded. Repeat loads can belong to the same person, and client-reported events do not establish unique visitors. A missing activity count also does not prove no customer saw an iframe or used a plain profile link.
Widget activity does not connect to checkout or payments. A click is not a purchase, and reviews are not revenue. Use your own orders and an explicit method for commercial measurement. Keep the activity report descriptive rather than inventing uplift.
Choose a practical improvement from the evidence
For failures, inspect delivery errors and recipient quality. For pending submissions, check moderation. For unanswered concerns, assign a reply. Follow the stage needing work instead of basing improvements on a fictional sales number.
An illustrative report could say: “Twenty invitations were sent, four matched submissions arrived, and three were published at the observation date.” The submission rate is four divided by twenty, or 20 percent; publication remains a separate count. These are fictional arithmetic inputs, not ReviewList performance benchmarks. Reuse that structure with your actual events, record unresolved issues, and keep invitation selection fair as you improve the workflow.
Honest collection report
| Measure | Definition and limit to record |
|---|---|
| Sent invitations | Dispatched campaign requests during your stated observation period. |
| Matched submissions | Reviews submitted through matched invitations, separate from publication. |
| Published direct reviews | Eligible public feedback after moderation; do not add collected reviews. |
| Unanswered feedback | Published direct reviews still awaiting a business response. |
| Widget activity | Approximate eligible script loads/clicks, not unique visitors or sales. |
Questions and answers
How is the campaign submission rate calculated?
The workspace uses matched completed submissions divided by sent invitations. It does not use queued requests or published review counts as interchangeable inputs.
Can I calculate sales from widget clicks?
No. ReviewList widget events do not connect to checkout or payment records. They are approximate activity counts, not purchases, revenue, or evidence of sales uplift.
Why do campaign submissions and public reviews differ?
Submitted reviews await moderation and may not yet be eligible for publication. Public counts also have their own scope, so check the state and origin of the feedback before comparing totals.
Sources and scope
ReviewList publishes this guide to explain a practical research or review workflow. Linked sources support the specific external principles discussed; they are not endorsements of ReviewList. Current merchant terms and the details of a particular order may differ.
- ReviewList collection reporting
- ReviewList invitation quota
- ReviewList publication and review-origin methodology
Editorial date: Oct 13, 2026. Suggest a factual correction.