1. Lighthouse

Level 2 · Which traffic source converts

The request

From Andrew Ramos, Marketing Manager

“I'm preparing the channel slide. For all three years together, how well does each traffic source convert? And our agency says organic 'really' converts at over 5% if you only count logged-in visitors. Which number should I put on the slide?”

Your goal

Set result to a DataFrame with one row per source in web_sessions (all years) and columns source, sessions (number of sessions), conversions (converted sessions), conversion_rate_pct (conversions * 100 / sessions) and known_rate_pct (conversions * 100 / sessions with a customer_id), both rates rounded to 2. Sort by conversion_rate_pct descending, with a fresh 0..n-1 index.

  • Use the web_sessions DataFramenot done yet
  • Show exactly source sessions conversions conversion_rate_pct known_rate_pctnot done yet
  • 5 rows, sorted as askednot done yet

Your code

Python

Loading the editor…

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

    Mote checks your result

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

    DataFrames

    Loaded for you as pandas DataFrames, plus pd and np.

    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
    1NaN2023-01-01 23:02:24mobilepaid1false
    2182023-01-01 15:07:49desktoppaid1false
    3NaN2023-01-01 16:55:46desktopdirect7false
    4NaN2023-01-01 12:43:28mobileorganic3false
    5NaN2023-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-02consumerNaN
    3HenryBrookshbrooks@lakesidecafe.comLos AngelesCA2022-06-04businessNaN
    4BrianGrahambgraham@bluecedarhomes.comSeattleWA2022-06-06businesspinterest
    5KyleJimenezkjimenez27@yahoo.comIndianapolisIN2022-06-07consumerNaN
    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.00NaN2023-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.00NaN
    10021562023-01-02 07:58:46completedweb0.00NaN
    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 OfficerNaN2016-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

    One rate per source

    A channel slide needs the conversion rate for each traffic source. It is the same formula as before, computed per group:

    s.groupby("source").agg(sessions=("session_id", "size"), conversions=("converted", "sum"))

    converted is a boolean column, so summing it counts the converted sessions. Dividing conversions by sessions within each row gives each source’s rate. Over 2023 to 2025, email converts 9.41% and social 0.62%: a fifteen-fold gap.

    The denominator decides the story

    The agency’s 5% comes from a different denominator. In this data a conversion is only recorded for a known, logged-in customer, so anonymous sessions can never convert. Divide by known sessions only and every rate goes up, by very different amounts:

    source anonymous share all sessions known only
    email 10.7% 9.41% 10.54%
    organic 65.3% 1.83% 5.28%
    social 71.3% 0.62% 2.18%

    Email traffic is almost all known customers clicking a newsletter, so the two rates are close. Organic and social bring mostly new, anonymous visitors, so removing them nearly triples the rate.

    Which one goes on the slide

    The all-session rate answers “of the traffic this source brings, how much buys?” That is the marketing question, and it is the KPI. The known-only rate answers “once a visitor is logged in, how likely are they to buy?” That is useful for diagnosing the checkout, and misleading as a channel comparison, because it hides how much of each channel’s traffic never gets that far.

    Give both if you like, but label the denominator in the column name, as this task does.

    Common mistakes

    • Averaging per-session flags in the wrong place. s["converted"].mean() is the overall rate; per source you need the group mean or the two counts.
    • Silently filtering customer_id.notna() early in the analysis “to clean the data”. Anonymous sessions are not dirty, they are most of the traffic.
    • Sorting without resetting the index, which leaves the old row labels behind.

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