> ## Documentation Index
> Fetch the complete documentation index at: https://docs.hibonsai.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Definitions

> Understand the sessions, visitors, orders, and revenue in your reports.

<table>
  <colgroup>
    <col width="235" />

    <col width="757" />
  </colgroup>

  <thead>
    <tr>
      <th>Term</th>
      <th>Meaning</th>
    </tr>
  </thead>

  <tbody>
    <tr>
      <td>**Visitor**</td>
      <td>A recorded storefront visitor whose available activity is grouped in Human Visitors. One visitor can have multiple sessions.</td>
    </tr>

    <tr>
      <td>**Session**</td>
      <td>A visit to your store. A session ends after 30 minutes of inactivity.</td>
    </tr>

    <tr>
      <td>**Session containing a search**</td>
      <td>A session in which the shopper actually searched with Bonsai. Search click-through and Searches per Search session use this population.</td>
    </tr>

    <tr>
      <td>**Search session**</td>
      <td>The broader reporting population used for Search attribution, conversion, and revenue per session. It is based on shoppers who searched during the same calendar week, Monday through Sunday. It is not limited to sessions containing a search.</td>
    </tr>

    <tr>
      <td>**Concierge session**</td>
      <td>A session containing at least one Concierge conversation.</td>
    </tr>

    <tr>
      <td>**Attributed session**</td>
      <td>A session included in the Search or Concierge reporting population. A session included in both counts once in the combined total.</td>
    </tr>

    <tr>
      <td>**Credited order**</td>
      <td>An order assigned to Search or Concierge under that experience's attribution rules. Search uses a calendar-week basis; Concierge uses a seven-day window following a conversation.</td>
    </tr>

    <tr>
      <td>**Attributed revenue**</td>
      <td>The total paid for credited orders, including tax and shipping. Refunds are not deducted.</td>
    </tr>

    <tr>
      <td>**New or returning visitor**</td>
      <td>Whether the visit is the shopper's first recorded visit. This describes visit history, not whether the person has purchased before. Clearing cookies can make a returning visitor appear new.</td>
    </tr>

    <tr>
      <td>**Acquisition channel**</td>
      <td>The source assigned to a session, such as paid search, organic search, email, referral, direct, or an AI assistant.</td>
    </tr>
  </tbody>
</table>

When both experiences qualify for an order, the last qualifying experience receives credit. The order is counted once in the combined revenue and order totals.

Search and Concierge conversion rates use different populations as well as different attribution windows. Compare each metric with its own prior periods; do not treat the two rates as equivalent measures of performance.

## Orders in Journeys

Journeys counts progression within a session. An order in a later session does not complete an earlier session's funnel, even when an attribution rule credits an earlier interaction.

For example, a Monday conversation followed by a Thursday purchase may qualify for Concierge credit. The Monday session still has no Order placed event in Journeys.

> **[Analytics](/project/docs/bonsai-analytics/analytics.md)**
>
> Explore Sales, Performance, and Behavior.

> **[Installing Your Pixel](/project/docs/pixel.md)**
>
> Set up and verify the pixel that connects shopper activity.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.