Design Assistant report overview
The Design Assistant report shows how often shoppers used the assistant on your website, what it showed them, and what those shoppers went on to do. Open it to answer "what has the Design Assistant done for us?"
The Design Assistant is the assistant on your website that answers a shopper’s questions and shows products. This article covers the report’s Overview tab, which reads top to bottom: conversations, assisted outcomes, the trends, then every day behind the charts.
Before you start
- You need the Marketing, Manager or Admin role.
Steps
-
In the sidebar, under Neural Analytics, select Design Assistant.
-
Choose a date range, such as Last 7 days, Month to date or Last month.

-
Read Conversations to see how much shoppers used the assistant.

-
Read Assisted outcomes to see what those shoppers did next.

-
Scroll to Trends to see the days the assistant was used.
-
Under Details, read the Daily table for every day behind the charts.

-
Select the question mark on a tile to read what that number means.
Good to know
Conversations
- Conversations counts each time a real shopper opened the assistant. A shopper who opens it and asks nothing still counts as one conversation.
- A conversation counts as human only when it was opened in a real browser that doesn’t identify itself as a bot. Every other session is shown on the tile as a non-browser or bot session. Those sessions are kept separate, not deleted, and are left out of every other number.
- Turns counts the assistant’s replies. Each reply is one turn.
- Avg duration is the average length of conversations that reported an end. A conversation closed without a clean ending is left out.
- Products shown is the total number of products the assistant put in front of shoppers, counting repeats.
- Product clicks counts each time a shopper selected a product the assistant showed.
- Conversations your own team has on your website count too. There is no filter for test traffic.
What assisted means
Assisted means the same shopper used the Design Assistant before acting. It does not mean the assistant caused the cart, the lead or the sale. The shopper might have acted anyway.
- Assisted carts counts add-to-cart actions by the same shopper, from the start of their conversation until 30 minutes after it ended.
- Assisted leads counts form submissions by the same shopper in that same window.
- Assisted purchases (same day) counts orders the same shopper placed later that same day (UTC), after their conversation started.
- Assisted revenue (same day) is the gross value of those orders, before refunds, in your store’s currency.
- Each cart, lead or order is counted once, against the shopper’s earliest conversation. A shopper who opens the assistant twice doesn’t inflate the numbers.
Limits of the assisted numbers
- An order placed the next day or later is not counted. Considered purchases often take days, so assisted purchases and revenue understate what really followed.
- The day is the UTC day. A US evening purchase can fall on the next UTC day and not be counted.
- If the range mixes currencies, Assisted revenue (same day) shows unavailable rather than a total.
- A cart or a form more than 30 minutes after the conversation ended is not counted.
- The link between a conversation and a cart, lead or order is the shopper’s browser. A shopper who switches device is not linked.
How conversations ended
Each conversation gets exactly one result: Lead, Cart, Signup, Saved, Product clicked or Abandoned. The six add up to Conversations.
- If more than one applies, the highest in that list wins. A shopper who selected a product and then added to cart counts once, as Cart.
- Cart includes an add-to-cart in the 30 minutes after the conversation, not only during it.
- A conversation whose tab was closed without a clean ending still gets a result from what was seen. If nothing else happened, it is Abandoned.
Trends
Five charts: Conversations per day, Turns per day, Product clicks per day, Assisted carts per day and How conversations ended.
Days with no bar
- A day appears only when the assistant had any activity, including bot sessions. A day with only bot sessions shows zero conversations. A day with no activity at all has no bar and no row in Daily.
- Read a missing day as no data, not as zero. Don’t average missing days in as zeros.
- A range with no activity at all says “No Design Assistant data for this range”. That is correct, not a fault.
When numbers arrive
- Each day is a UTC day. Yesterday’s numbers are added each morning, around 6 a.m. Eastern.
- A day runs midnight to midnight UTC, so a chat after about 7 or 8 p.m. Eastern counts toward the next day. The Email & SMS and Advertising reports cut days in your account’s time zone instead. A conversation that crosses midnight UTC has its later part counted as a bot session on the second day. This is rare.
- Midnight UTC also cuts the 30-minute window. A conversation at 11:50pm UTC followed by a cart at 12:10am is not counted.
- Conversation and turn counts start on October 10, 2026.
What to expect
Conversation counts are often small. Assisted outcomes can read zero for a while, because they need a shopper to chat and then add to cart, send a form or buy on the same visit. A small number does not mean something is broken.
What the numbers are made from
The Overview numbers are built from counts, product references and timings. No message a shopper typed and no answer the assistant gave goes into these numbers. A room photo a shopper attaches is recorded only as a photo having been attached.
Admins also see a Conversation log tab, which shows conversation transcripts. Marketing and Manager users don’t see it.