What Is Assisted Revenue in Ecommerce?
Assisted revenue connects orders with prior shopping-assistant participation under defined rules. Learn what the metric observes, what it cannot prove, and how to use it.
Assisted revenue is the value of orders associated with a qualifying assistant interaction under a defined reporting rule. It helps merchants observe where guided shopping participated in a purchase journey.
It is not automatically incremental revenue, causal lift, or revenue that would have disappeared without the assistant. The distinction is essential for accurate ecommerce analysis.
What the metric is designed to answer
Assisted revenue can answer a descriptive question: “Which orders were connected to shoppers who used the assistant in a qualifying way within the reporting scope?”
To make that answer meaningful, the implementation needs a documented definition. That definition may specify the qualifying interaction, identity or session logic, time window, order status, currency handling, exclusions, and update behavior.
Without those rules, the number is difficult to compare over time and easy to misinterpret.
A simple conceptual example
Suppose a shopper asks the assistant for eventwear, views a recommended product, and later places an order that can be associated with the journey under the platform’s rules. The order value may appear as assisted revenue.
The observation is useful: the assistant participated somewhere in that journey. It does not reveal the counterfactual. The shopper might have purchased anyway, selected a different product, spent a different amount, or left. Assisted revenue alone cannot determine which outcome would have occurred without the interaction.
What should be included in the definition
Qualifying interaction
Specify whether any widget open qualifies or whether the shopper must send a message, view a product, use Virtual Try-On, or take another meaningful action. A stricter rule may produce a smaller but more interpretable set.
Association window
Document how long an interaction can remain associated with a later order. A window that is too broad may capture weak relationships; one that is too narrow may miss longer consideration journeys.
Identity and session logic
Explain how visits are connected within privacy and technical constraints. Cross-device and anonymous journeys may remain incomplete. Reporting should acknowledge those blind spots.
Order treatment
Clarify whether values use gross or net order totals, how cancellations or refunds are handled, which order statuses count, and how currencies are presented.
Multiple touchpoints
Define what happens when a shopper has several assistant interactions or engages with multiple products. Avoid counting the same order more than once in an aggregate total.
Assisted revenue versus incremental lift
Incremental lift asks a causal question: “How much additional outcome occurred because the experience existed?” Answering it generally requires an appropriate experimental or quasi-experimental design, reliable assignment, sufficient data, and careful analysis.
Assisted revenue asks an observational question. It is closer to participation reporting than proof of causation. Both can be useful, but they should not share a label.
WardrobeIt’s Usage and Outcome Analytics is framed around observed interactions and outcomes. Merchants should preserve that language in dashboards, reviews, and executive summaries.
How to use assisted revenue responsibly
Combine it with usage quality
Review the number alongside conversations, product engagement, unresolved questions, and feature completion. A rising total may reflect more traffic, higher order values, broader assistant adoption, or changes in association—not necessarily a better experience.
Segment with purpose
Useful segments may include device, category, entry surface, interaction type, or new versus returning context when supported. Avoid slicing small datasets until noise appears meaningful.
Track definition changes
If the qualifying action or window changes, annotate the date. Historical trends can break even when the storefront does not.
Use it to guide review
Associated journeys can identify conversations worth examining. Merchandising teams can inspect which product missions lead to deeper engagement and where guidance fails. The metric is a map for questions, not a verdict.
Questions merchants should ask vendors
- What exact event qualifies an order as assisted?
- What is the association window?
- How are anonymous, returning, and cross-device shoppers handled?
- Are tax, shipping, discounts, cancellations, and refunds reflected?
- Can one order appear in more than one category or feature report?
- How quickly do orders and adjustments update?
- Can the underlying journeys be audited?
- Which privacy controls and retention rules apply?
Connect analytics to merchandising
The most useful analysis turns observations into catalog questions. If shoppers repeatedly ask for a specific occasion or attribute, check whether the catalog represents it consistently. If assisted journeys cluster around a product type, review what makes that category require guidance.
Likewise, a low associated value does not prove a category is unsuitable. The assistant may not be offered, product content may be sparse, or shoppers may use it for questions that do not lead directly to an order.
WardrobeIt’s Merchant Portal provides the operational context for reviewing the connected experience, while Track Assistant Outcomes focuses on the measurement use case.
Report the metric in plain language
A good reporting note states the period, total, definition, and limitations. For example: “This view includes order value associated with qualifying assistant interactions under the current reporting window. It is observational and does not estimate incremental lift.”
Keep that explanation close to the number. A tooltip alone may be insufficient if screenshots or exports remove the context.
Use observation to ask better questions
Assisted revenue is valuable when it is treated as a transparent participation metric. It helps teams locate commerce journeys involving guided shopping and decide where deeper investigation is warranted.
Define it before reporting it, audit changes, pair it with interaction quality, and reserve causal language for evidence that can support it. Visit Usage and Outcome Analytics to explore WardrobeIt’s observational approach.
