Reference

Insights metrics and business decisions

Reference for engagement, menu interest, retailer opportunities, assortment gaps, source coverage, freshness, aggregation, and practical follow-up actions.

Updated Sep 17, 2026 Source reviewed Sep 17, 2026 4 minute read
For: farm ownersbrand ownerssales teamsbusiness analysts

Coverage and freshness first

Engagement compares the selected period with the preceding period and excludes interactions classified as bots or internal activity. A session is a tracked browser session, not a known person. Retailer opportunity and assortment reports depend on current source coverage and must distinguish insufficient evidence from a confirmed zero.

Before acting on a retailer report, read Menu data through, Fresh retailer locations, attribution coverage, category-mapping coverage, and locations excluded for stale or insufficient data. A missing listing can mean the brand is absent, but it can also mean the retailer menu is stale, incomplete, not attributed, or outside coverage.

Important engagement metrics

  • Human interactions: recorded events in the selected period after the current bot and internal-activity classification; compared with the immediately preceding period of the same length.

  • Unique sessions: distinct tracked session identifiers among eligible interactions. A session is not a known person, and interactions without a session ID are excluded from the unique-session count.

  • Product and menu views: recorded view events for owned product and menu URLs in the period.

  • Interest actions: searches, QR scans, email clicks, menu requests, and new page subscriptions. Approximate email opens are reported separately because automated clients can load tracking pixels.

  • Menu performance: top five active Public or Unlisted menus by current-period recorded views. Menu requests remain business-level because the recorded request does not identify a menu.

  • Delivered-order value: value from orders in Delivered status, grouped by the report window. It is not cash received.

Repeat visits are inferred only when view events exceed distinct tracked sessions. This can indicate repeat viewing within a session, shared devices, or missing session coverage; it does not prove customer retention. Current bot and internal flags are applied, but no claim is made that every automated visit is detected.

Worked example: find nearby retailers

  1. Open Insights > Opportunities > Retailer Matches and select the brand and county that match the sales territory.

  2. Check Fresh retailer locations and the data-through date. If many locations are stale or excluded, treat the list as partial.

  3. Review a retailer's distance, active license status, menu freshness, shared classifications, matching brands, and current-placement check.

  4. A reasonable conclusion is that the retailer has fresh comparable assortment and the selected brand was not observed. It is a prospect signal, not proof that the buyer wants the product.

  5. Choose Add prospect, then continue in Trading Partners with a contact, task, stage, and outreach note. Adding a prospect does not send a message or email.

Worked example: assess interest in a shared menu

  1. Open Insights > Engagement > Products & Menus and select the period.

  2. Compare menu Views with Unique Sessions and check session-attribution coverage. Eight views from three sessions suggests repeated viewing, not eight buyers.

  3. Check product views and whether frequently viewed products are on an active menu.

  4. Use the signal to update the menu or create a Trading Partner follow-up. Do not claim buyer intent from a view alone.

Worked example: partners needing follow-up

  1. Open Insights > Opportunities > Outreach and review Prospects with no activity, Prospects contacted in 30 days, and relationship status.

  2. Open the saved account in Trading Partners and check Last Activity, open tasks, contacts, and stage.

  3. Create a dated task or record the real call, email, or meeting. The report does not send outreach for you.

Worked example: assortment gap or missing data

  1. A possible assortment gap requires an active canonical retailer, a fresh complete menu observation, reliable brand attribution, comparable selected-brand categories, and no current selected-brand listing.

  2. If the location appears under stale or insufficient coverage, conclude only that current evidence is missing. Do not call it a confirmed gap.

  3. Review comparable products, price coverage, package normalization, menu freshness, and the qualifying observation.

  4. Use a confirmed signal to create a Trading Partner prospect or a targeted menu. Recheck evidence before outreach because retailer menus change.

Membership

Free Insights exposes aggregate context and samples. Retailer-level, geographic, assortment, pricing, and detailed recommendation views can require Membership. After signing in, open Support Higher Origins to review the offer available to the selected business.

Was this guide helpful?

HigherOrigins
Are you 21 or older?
By continuing, you acknowledge that you have read, understood, and agree to our terms of use and privacy policy