Appearance
Top findings: what Nexus found and how it ranks it
Top findings is the ranked feed of what Nexus detected in your store data. It covers products, customers, customer experience (CX) and ads. Open it from Insights > Top findings.
Problem and intended user
The ecommerce manager (the person who runs the store) has more signals than time. Sales, returns, reviews and ad results sit in different places. The media buyer (the person who runs your paid ads) has the same issue across ad platforms. Without a shared ranking, a quiet but costly issue can wait.
Current workflow
Many merchants check Shopify admin reports, GA4, Meta Ads Manager, Google Ads and their review app one after another. They export the numbers to a spreadsheet, line them up by product or campaign, and rank them by judgment. Some hand this work to an agency.
Prerequisites
Findings come from your imported store data and from the sources you connect. Each expanded card lists its Data Sources. GA4 adds findings about traffic, conversion and revenue changes. Without GA4 you still see findings from your other sources. See Google Analytics 4.
To get revenue estimates on ad findings, connect your ad platforms. See Meta Ads and Google Ads.
What the revenue estimate needs
Ad findings need three inputs before they show a revenue range:
- Ad spend from a connected ad platform.
- Orders attributed to the ad creative. Your landing page links must carry
utm_contenttagged with the creative ID. - Order profit. Your product costs must reach Nexus.
Without all three, the finding still appears with no revenue range.
How Nexus works
Nexus reads your imported store and ad data and checks it against fixed rules and statistics. Many findings come from these rules. Some findings, for example those drawn from reviews, customer feedback or ad analysis, are written or classified by an AI model. Nexus then ranks them.
A finding is one signal that earned a recommendation, for example a product that sells but is returned often. Some cards also carry recommended actions. Nothing in the feed changes your store, your ads or your customers, so no approval step applies.
The feed needs your store data to finish importing. While the feed is empty and a source is still preparing, a notice says what is pending.
Order the feed
The feed shows the highest priority first. The Impact button changes the order:
- Select Impact once to sort by revenue impact, high to low.
- Select it again to sort low to high.
- Select it a third time to return to the priority order.
Findings without a revenue estimate sort last when you sort by Impact.
Open a card
Select See More to expand a card. Select See Less to close it.
Go to the ad a finding is about
A finding about one of your ads names that ad under its title. To see the ad's numbers:
- Select Open in Ad performance under the ad's name. The page opens in a new tab.
- Read the ad's row. The page shows the By ad view, with the ad's name in Search ads by name and the ad's row highlighted.
- Select the X in the field (Clear search) to see every ad again.
See Ad performance.
Rescan Data
Rescan Data reloads the feed from Nexus. It does not start a new analysis. New findings appear on their own as your data updates.
When findings update
The feed shows no update time. The sentence "new findings appear automatically as your data updates" shows only when the feed is empty and reads No active insights right now. Nexus updates findings on its own. If GA4 is connected, Settings > Store Status lists a Daily insights analysis row with its last run. Some findings come from other jobs on other schedules, so the feed has no single refresh time. See Store Status.
Exact output
The finding card
Each card shows these parts.
| Part | What it tells you |
|---|---|
| Priority label | High, Medium or Low. The numeric score is not shown on this page. |
| Category tag | The kind of finding, in short form. |
| Status badge | Where the finding is in your workflow. See Work through findings. |
| Platform logos | The platforms behind the finding. Some findings show none. |
| Title and description | What Nexus detected. |
| Ad line | Shows only on a finding about one of your ads. It names the ad as your ads account names it, then the platform, such as Meta or Google, and the ad ID that platform shows. The campaign and the ad set follow when Nexus knows them. When the ad's headline differs from its name, the headline shows underneath. |
| Open in Ad performance | Shows with the ad line. Opens the ad on the Ad performance page in a new tab. |
| Impact: | An estimated revenue range, or one value when Nexus has no range. A dash means Nexus has no revenue estimate. |
| Confidence: | How sure Nexus is, as a percentage. A dash means Nexus has no value. |
| Issue and Action Agent box | A short summary of the issue and the first recommended action. It shows only when the finding has recommended actions. |
The Confidence percentage is coloured by level. Read the number, not the colour.
Impact and its tooltip
Impact is a range, not a promise. A small flask icon sits beside the label. It has no click action. Hover over it to read that impact estimation is still being calibrated. Use the range to rank your work.
Hover over the (i) icon next to the range to see how Nexus calculated it. With a revenue range, the tooltip shows the formula, its inputs and the result. Without one, it explains why. For an ad finding, it lists the three inputs named in Prerequisites: ad spend, orders linked to the ad, and order profit. When the finding has its own low and high estimate, the tooltip adds a Range width note that says so.
The expanded card
The expanded card shows Recommended Actions as a numbered list, then Category, Channel and Data Sources. A finding with no recommended actions shows a Deterministic detection note instead. It means a rule surfaced the finding. When available, Triggered by names the rule that raised it.
Search and filter controls
| Control | What it does |
|---|---|
| Search agents, insights... | Matches the title, description, category and channel. |
| Status | Filters by workflow status. |
| Types | Filters by category. |
| Agents | Filters by data source, such as Shopify, Meta or GA4. |
| Impact | Sorts by revenue impact. |
| CX, Customers, Products, Ads | Domain chips. Select one or more to show only those domains. |
| Select & Merge | Sits below the domain chips. Starts merge mode, where you tick related findings and join them under one card. See Work through findings. |
The page address keeps your search, status, types, agents and Impact sort. Reload the page or go back and the view stays. The domain chips are not kept.
What to do with it
Top findings tells you where to look. It does not run the fix. See Work through findings to track your decision.
| What you see | Decision or action | Owner |
|---|---|---|
| A High finding with a revenue Impact range | Read Recommended Actions and decide what to do first. | ecommerce manager |
| An ad finding with a Meta or Google logo | Decide whether to change the ad or the budget. You make the change in Meta Ads Manager or Google Ads, outside Nexus, or in Create or Performance. | media buyer |
| A finding that names one of your ads | Select Open in Ad performance to check the ad's numbers before you act. Use the ad ID to find the same ad in Meta Ads Manager or Google Ads. | media buyer |
| A recommended action that calls for a new creative | Plan the new creative in Create. | creative strategist (the person who plans and makes ad creatives) |
| A Customers finding | Decide whether a follow-up campaign is needed. You run it in your email tool, outside Nexus. | retention marketer (the person who runs email and repeat-purchase campaigns) |
| An Impact dash | Rank the finding by its priority label and Confidence instead. | ecommerce manager |
| A notice about data being prepared | Connect the missing data source. | ecommerce manager |
Expected value and measurement
Top findings can help you decide what to work on first and see signals from several sources in one ranked list.
To check whether it helps:
- Open Insights > Top findings and set Status to Resolved to see the findings you closed.
- Open the page that holds the metric the finding is about:
- Ad finding: Performance > Ad performance. See Ad performance. Compare Gross profit after ad spend or Matched revenue.
- Product finding: Insights > Products > Product List. See Product List. Compare Return %, Revenue or Margin.
- Customer finding: Insights > Customers, tab All Customers. See All Customers. Compare Churn Risk or Days Since Order.
- Compare the metric before and after you acted. Where the page lets you pick dates, use periods of the same length.
The Impact range is an estimate. You cannot isolate the effect of one finding when other changes ran at the same time, such as a new campaign or a sale.
Limitations and exceptions
- Impact and Confidence are estimates. Nexus is still calibrating impact estimation.
- A recommended action can be wrong. Check it against what you know about your store before you act. Text that an AI model writes can be wrong too.
- Ad findings without all three inputs show no revenue range.
- An older finding can show a revenue range with no breakdown. Its (i) tooltip then says the calculation breakdown is not available.
- The feed shows a limited number of findings at once. It has no button to load more.
- Only some findings name an ad. A finding about several ads, or about a product or a customer group, has no ad line and no Open in Ad performance link.
- Ad performance shows the ad only for the selected dates. If the ad had no spend in those dates, the page says it has no row for the selected dates. Widen the dates in the date picker. Select Dismiss to close the notice.
When the feed is empty
| What you see | What it means |
|---|---|
| No insights match your filters | Your filters hide every finding. Select Clear filters. |
| No active insights right now | All data has loaded and nothing needs attention. |
| "We're still finishing ..." | The sentence names what is pending, for example your Google Analytics data. Wait. |
| "Connect your Google Analytics data to fill in this section." | Connect it under Settings > Integrations. |
| Failed to load insights. | The feed did not load. Select Retry. |
No active insights right now shows only when nothing is pending. No set amount of history is needed, and a new store can see few findings.
Demo Mode
In Demo Mode the feed shows a sample set of findings. Rescan Data only shows a message, "Not available in demo mode", and the feed does not change.