Appearance
Yesterday and Lucrative findings
Two sections on every Home dashboard sit around your KPI cards. Yesterday tells you what moved on the last full day. Lucrative findings lists the money your store is leaving on the table, with a next step for each item. Both change with the dashboard you open. See Home dashboards.
Problem and intended user
The ecommerce manager (the person who runs the store), the media buyer (the person who runs your paid ads) and the creative strategist (the person who plans and makes ad creatives) each want to know each morning what moved in their own numbers. Without a daily summary, a drop in sales or a wasteful ad can go unseen while attention goes to smaller problems.
Current workflow
Each morning a merchant reads yesterday's orders in Shopify admin reports, ad spend in Meta Ads Manager and Google Ads, and sessions in GA4. The merchant judges each figure against a recent average by eye or in a spreadsheet. To decide what to fix first, the merchant ranks the problems by hand or asks an agency.
Prerequisites
- Store data. Both sections need store data. Until it arrives, each shows a short message.
- Ad account. The Ads and Creative versions also need a connected ad account.
- History. A highlight shows a change figure only when Nexus has earlier days to compare.
- Insights. Findings are insights Nexus has already produced for your store, and each needs a money estimate.
How Nexus works
Fixed rules produce both sections. No AI runs when you open them. They change nothing in your store or ad account and need no approval.
Yesterday. Nexus compares each figure for the last full day with a baseline, such as a trailing daily average or the week before. A move of 5% or less counts as noise.
Lucrative findings. Nexus picks open insights that carry a money estimate, ranks them by priority and sorts them onto the dashboard for their role. Nexus set the text on a card when it created the insight.
Read Yesterday
- Open Home and read the headline and highlights on the Yesterday card.
- Click See more insights at the top right for Top findings.
Work through a finding
- Scroll to Lucrative findings under the KPI cards.
- Read the card. Click its action button for the detail page, or See ad details for the ad.
- Click Dismiss only when you decide the finding is not worth your time.
WARNING
Dismiss has no undo. Nexus also sets the finding to Dismissed in Insights > Top findings. To see a dismissed finding again, set Status to Dismissed in Insights > Top findings. To track a finding through statuses instead, see Work through findings.
If Nexus cannot save a dismissal, the card comes back.
Exact output
The Yesterday card
The card shows the date, one headline and a list of highlights. Each highlight starts with an arrow and carries a change figure when Nexus has a baseline:
- A green arrow that points up marks good news.
- An amber arrow that points down marks something to watch.
- A grey dash marks no clear change, or no baseline to compare against.
If nothing passes the 5% bar, the headline says it was a quiet day. Otherwise it leads with the biggest move, as "A solid day" or "A tougher day". A highlight appears only when Nexus knows yesterday's figure.
| Dashboard | Highlights can cover |
|---|---|
| Store overview | Revenue, new customers, repeat orders, orders and average order value |
| Ads overview | Ad spend and return, own ads launched, ads burning budget, aMER |
| Creative overview | Cuts launched and hook rate, average watch time, active angles |
The repeat orders highlight reads "Repeat orders made up X% of the 7 days ending yesterday". It is the share of customers who ordered in the 7 days before who ordered again in the last 7 days.
The Lucrative findings row
Under the KPI cards, Lucrative findings shows money the store is leaving on the table. Nexus orders the findings by priority, not by money. Each dashboard shows findings for its own role. A finding is a problem or an opportunity that Nexus detected in your data.
Nexus shows a short row of findings. Scroll the row or use its arrow buttons. When you have more than one, click See all N to lay them out in a grid. Click Show fewer to go back to the row.
Read a finding card
A card holds these parts, top to bottom:
- Category tag. Store overview uses Retention, Store fix, Acquisition and Merchandising. Ads overview uses Creative, Budget, Placement and Audience. Creative overview uses Creative.
- Source count. The number of data sources behind the finding. A New badge marks a finding you have not worked on.
- Title and subject. The product, ad or area the finding is about. A picture sits beside the buttons when Nexus has one.
- Impact. An estimated range per month. Some findings show lifetime profit instead. Some cards show an information icon next to the figure. Select it to see how Nexus estimated the impact.
- Summary and supporting data. What Nexus found, and the lines of data that support it.
- Recommendation. What to do next, in bold.
Card buttons
| Button | What it does |
|---|---|
| Action button | Opens the finding's detail page. The label follows the category: Start, Review fix, Create bundle, Brief a refresh, Review budget, Review placements or Review audience. |
| See ad details | Opens the ad behind the finding. It appears only when an ad is linked. |
| Dismiss | Hides the card. |
The detail page shows What we found and Recommended actions when the finding has that text. It also shows Projected impact and Data sources. A small flask icon beside Projected impact says, on hover, that impact estimation is still being calibrated. Click Back to Top findings to return to the list.
What to do with it
| What you see | Decision or action | Owner |
|---|---|---|
| A green or amber highlight on Store overview | Decide whether the move needs a closer look. | ecommerce manager |
| A highlight on Ads overview that says ads are burning budget | Review the ads in Performance > Ad performance. Change budget in Meta Ads Manager or Google Ads, outside Nexus. | media buyer |
| Start, Review fix or Create bundle | Click the button, read Recommended actions, then act in your store. | ecommerce manager |
| Brief a refresh | Click the button, read Recommended actions, then plan a replacement creative. | creative strategist |
| Review budget, Review placements, Review audience or See ad details | Click the button, then change the ad in Meta Ads Manager or Google Ads, outside Nexus. | media buyer |
| Dismiss | Hide a finding you have decided to ignore. | ecommerce manager, media buyer or creative strategist, by dashboard |
Expected value and measurement
These sections can help you spot a drop sooner and choose which problem to work on first. The impact on a card ranks work. It is not a forecast. To check a result:
- Store. Open Home > Store overview. Compare Revenue and Orders in Your KPIs with the previous period, if you kept those cards.
- Ads. Open Performance > Ad performance. Compare spend and return before and after a change.
- Findings. Open Insights > Top findings and set Status to Resolved.
Nexus does not measure whether a finding produced its estimated impact. If you change ads, prices or promotions in the same period, you cannot isolate one effect.
Limitations and exceptions
- Estimates. The impact range is an estimate. Some card text is written by AI and can be wrong. Check a finding before you act.
- Delivered orders. On Store overview, revenue, orders, average order value and repeat orders count only orders your store has marked as delivered. A new order does not count until then. The Revenue and Orders cards in Your KPIs follow the same rule. New customers count first orders, delivered or not.
- Yesterday reads low. An order enters yesterday's figures once your store marks it delivered. Yesterday's orders and revenue can read low and can rise later, and the headline can then say "A tougher day". For how each number counts orders, see Understanding your numbers.
- Which findings show. Nexus orders your highest-priority open insights by priority, not by impact. A dashboard can show fewer findings than you expect, or none.
- Headline. A count line, such as ads launched, can lead the headline over a percentage move.
When a section shows a message
| Message | What it means and what to do |
|---|---|
| "No orders or sessions were recorded yesterday." | Nexus found nothing to report. Check again tomorrow. If you expect orders, see While your data imports. |
| "Yesterday's data is temporarily unavailable. Try again shortly." | Nexus could not reach the data source. Wait, then reload. |
| "Couldn't load Yesterday." | The request failed. Click Retry. If it keeps failing, see Contact support. |
| "You have cleared every finding. New ones appear here as the store keeps trading." | No card is left, or no finding fits your role yet. Nothing to do. |
Demo Mode
In Demo Mode the Yesterday card and the findings show sample data. Dismiss does not touch your own store data. In the public demo, Dismiss shows "This action is not available in the public demo." and the card comes back.
