1. Lighthouse

Level 1 · Sessions to orders, honestly

The request

From Jordan Reyes, Head of Marketing

“Someone in the leadership meeting said our website converts 27% of visits, because we had about 4,400 orders and 16,000 sessions last year. That can't be right. What is our real conversion rate, and how has it moved since 2023?”

Your goal

From web_sessions, return one row per year with: year (the year of started_at), sessions (number of sessions), conversions (sessions with converted = true) and conversion_rate_pct (conversions * 100 / sessions, rounded to 2). Sort by year ascending.

  • Read from the web_sessions tablenot done yet
  • Show exactly year sessions conversions conversion_rate_pctnot done yet
  • 3 rows, sorted as askednot done yet

Your query

SQL

Loading the editor…

    ResultPreview of web_sessions · press Run to see yours
    Preview of web_sessions
    session_idcustomer_idstarted_atdevicesource
    1NULL2023-01-01 23:02:24mobilepaid
    2182023-01-01 15:07:49desktoppaid
    3NULL2023-01-01 16:55:46desktopdirect
    4NULL2023-01-01 12:43:28mobileorganic

    Mote checks your result

    Press Run. Each row that matches the goal becomes a firefly in your lantern.

    Tables

    Harbor & Pine store data, ready to query.

    web_sessions40,000 rows · 7 columns
    • session_idinteger
    • customer_idinteger
    • started_attimestamp
    • devicevarchar
    • sourcevarchar
    • pages_viewedinteger
    • convertedboolean
    First 5 rows of web_sessions
    session_idcustomer_idstarted_atdevicesourcepages_viewedconverted
    1NULL2023-01-01 23:02:24mobilepaid1false
    2182023-01-01 15:07:49desktoppaid1false
    3NULL2023-01-01 16:55:46desktopdirect7false
    4NULL2023-01-01 12:43:28mobileorganic3false
    5NULL2023-01-01 13:06:21mobilesocial2false
    customers2,018 rows · 9 columns
    • customer_idinteger
    • first_namevarchar
    • last_namevarchar
    • emailvarchar
    • cityvarchar
    • statevarchar
    • signup_datedate
    • segmentvarchar
    • referral_sourcevarchar
    First 5 rows of customers
    customer_idfirst_namelast_nameemailcitystatesignup_datesegmentreferral_source
    1OwenHudsonowen.hudson@icloud.comSan FranciscoCA2022-06-02consumersearch
    2DouglasMendozadmendoza69@gmail.comAtlantaGA2022-06-02consumerNULL
    3HenryBrookshbrooks@lakesidecafe.comLos AngelesCA2022-06-04businessNULL
    4BrianGrahambgraham@bluecedarhomes.comSeattleWA2022-06-06businesspinterest
    5KyleJimenezkjimenez27@yahoo.comIndianapolisIN2022-06-07consumerNULL
    products120 rows · 8 columns
    • product_idinteger
    • namevarchar
    • categoryvarchar
    • subcategoryvarchar
    • unit_pricedecimal
    • unit_costdecimal
    • launched_ondate
    • is_activeboolean
    First 5 rows of products
    product_idnamecategorysubcategoryunit_priceunit_costlaunched_onis_active
    101Vale Velvet LoveseatFurnitureSofas1659.00NULL2023-09-11true
    102Alder Oak Coffee TableFurnitureTables919.00503.502024-05-16true
    103Orchard Rattan Dining ChairFurnitureChairs789.00429.872023-05-27true
    104Upland Oak BookcaseFurnitureStorage429.00214.702022-12-20true
    105Avery Leather Bed FrameFurnitureBeds449.00232.702021-08-31true
    orders12,000 rows · 7 columns
    • order_idinteger
    • customer_idinteger
    • order_datetimestamp
    • statusvarchar
    • channelvarchar
    • shipping_feedecimal
    • coupon_codevarchar
    First 5 rows of orders
    order_idcustomer_idorder_datestatuschannelshipping_feecoupon_code
    10011252023-01-01 20:51:19completedweb0.00NULL
    10021562023-01-02 07:58:46completedweb0.00NULL
    1003222023-01-02 10:25:27completedmarketplace4.99WELCOME10
    1004482023-01-02 11:21:51completedmarketplace4.99WELCOME10
    1005822023-01-02 11:43:36completedweb0.00WELCOME10
    order_items30,338 rows · 6 columns
    • order_item_idinteger
    • order_idinteger
    • product_idinteger
    • quantityinteger
    • unit_pricedecimal
    • discount_pctdecimal
    First 5 rows of order_items
    order_item_idorder_idproduct_idquantityunit_pricediscount_pct
    11001121931.990.00
    21001154311.990.00
    31002154411.990.00
    410021941149.000.00
    51002193219.990.00
    returns1,673 rows · 5 columns
    • return_idinteger
    • order_item_idinteger
    • returned_ondate
    • reasonvarchar
    • refund_amountdecimal
    First 5 rows of returns
    return_idorder_item_idreturned_onreasonrefund_amount
    1142023-01-10damaged83.69
    2422023-01-10wrong_item19.99
    31052023-01-14wrong_item10.99
    4242023-01-16changed_mind26.99
    51262023-01-16late20.99
    employees60 rows · 8 columns
    • employee_idinteger
    • first_namevarchar
    • last_namevarchar
    • departmentvarchar
    • titlevarchar
    • manager_idinteger
    • hire_datedate
    • salaryinteger
    First 5 rows of employees
    employee_idfirst_namelast_namedepartmenttitlemanager_idhire_datesalary
    1CatherineHaleExecutiveChief Executive OfficerNULL2016-03-01285000
    2RobertKimExecutiveChief Operating Officer12017-01-09235000
    3MeganCollinsSalesHead of Sales12018-04-16172000
    4ChloeGutierrezSalesAccount Executive32020-01-2172000
    5FrankBellSalesAccount Executive32023-05-2173000
    marketing_spend3,276 rows · 3 columns
    • spend_datedate
    • channelvarchar
    • amountdecimal
    First 5 rows of marketing_spend
    spend_datechannelamount
    2023-01-01paid492.99
    2023-01-01email37.38
    2023-01-01social200.53
    2023-01-02paid709.13
    2023-01-02email64.13

    The lesson

    What a conversion rate is

    A conversion rate is the share of some unit that did the thing you wanted. In a web funnel the unit is usually the session: one visit, from arrival to leaving. The rate is

    converted sessions * 100.0 / all sessions

    Both counts come from web_sessions, in the same year, under the same filters. That is what makes the number mean something: every session in the denominator had the chance to be in the numerator.

    Where the 27% came from

    The number in the ticket divides 4,409 booked orders in 2025 by 16,225 web sessions. It looks like a conversion rate and is not one:

    • Orders come from three channels: web, app and marketplace. In 2025 only 1,805 booked orders were placed on the web. App and marketplace buyers never create a web session.
    • web_sessions has no order_id. It is a separate funnel dataset, and it does not cover every web order either: 2025 has 500 converted sessions against those 1,805 web orders.
    • One customer can visit five times and buy once. Orders and sessions count different things.

    Dividing a count from one table by a count from another only works when the numerator is a subset of the denominator. Here it is not, so the result is meaningless, however precise it looks.

    Session, visitor or order?

    The same funnel gives different rates depending on the unit:

    • Per session: 500 / 16,225 = 3.08%. This is the standard web metric.
    • Per buyer: the 500 converted sessions belong to 431 different customers; a customer who buys twice counts once.
    • Per order: needs orders linked to sessions, which this data does not have.

    None of them is wrong. Mixing them is. A report that says “conversion rate” without the unit invites the 27% mistake.

    Reading the trend

    2.99% in 2023, 2.86% in 2024, 3.08% in 2025. Sessions grew every year, so a flat rate still means more conversions: 317, 376, then 500. When someone asks whether conversion “improved”, show the rate and the counts together.

    Common mistakes

    • Dividing orders by sessions. Different tables, different units, no link between them.
    • Integer division. COUNT(*) FILTER (...) * 100 / COUNT(*) on integers rounds down to whole percents. Use 100.0.
    • Dropping anonymous sessions. They are real visits. Removing them makes every rate look better.

    Pick what may run on this site. You can change this any time from "Cookie settings" at the bottom of every page.