1. Lighthouse

Level 5 · Does more ad spend bring more visits?

The request

From Jordan Reyes, Head of Marketing

“When we spend more on paid ads on a given day, do we actually get more paid visits that day? Give me one number for how strongly they move together, and a chart.”

Your goal

Build a table with one row per day of 2025 on which marketing_spend has a 'paid' row: paid_spend (that day's amount) and paid_sessions (the number of web sessions that day with source 'paid', 0 if none). Set result to the correlation between paid_spend and paid_sessions (pandas' default, Pearson), a float rounded to 2. Draw it with sns.regplot.

  • Use the web_sessions DataFramenot done yet
  • Use the marketing_spend DataFramenot done yet
  • Store a number in resultnot 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
    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
    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

    The lesson

    One number for “moving together”

    The correlation coefficient r measures how closely two numbers follow a straight-line relationship. It runs from -1 to +1:

    • the sign is the direction: + means they rise together, - means one rises as the other falls;
    • the size is the strength: as a rough guide, above 0.7 is strong, 0.3 to 0.7 moderate, below 0.3 weak;
    • 0 means no straight-line relationship (there could still be a curved one).

    In pandas it’s one call on two Series of the same length, lined up row by row:

    daily["paid_spend"].corr(daily["paid_sessions"])     # about 0.65

    That’s pandas’ default, Pearson’s r. method="spearman" gives a rank-based version that is less sensitive to a few extreme days.

    Lining the data up first

    Correlation compares row 1 with row 1, row 2 with row 2. So both numbers must describe the same thing, here the same day. Spend has one row per day and channel; sessions have one row per visit. Count the visits per day, then merge them onto the spend days:

    per_day = visits.groupby("day").size().rename("paid_sessions").reset_index()
    spend_days = paid[["spend_date", "amount"]].rename(columns={"spend_date": "day", "amount": "paid_spend"})
    daily = spend_days.merge(per_day, on="day", how="left").fillna({"paid_sessions": 0})

    The left merge keeps every spend day, and fillna gives 0 to days with no paid visits. Those zero days are real observations; dropping them would hide the low end of the relationship.

    Seeing it: scatterplot and regplot

    sns.scatterplot(data=daily, x="paid_spend", y="paid_sessions") draws one dot per day. sns.regplot draws the same dots plus a fitted straight line and a shaded band around it showing how uncertain the line is. It’s the np.polyfit line from chapter 11 in one call:

    ax = sns.regplot(data=daily, x="paid_spend", y="paid_sessions",
                     scatter_kws={"alpha": 0.35}, line_kws={"color": "#c0392b"})

    With r around +0.65, days with higher spend tend to have more paid visits, but the dots are far from a line: plenty of high-spend days had few visits. Report it as “paid spend and paid visits are clearly associated”, with the number. Both also rise in November and December, so part of this link is the season itself, which the next levels deal with.

    Common mistakes

    • Correlating columns that aren’t aligned on the same unit (one row per day on both sides).
    • Calling r = 0.65 “65% of visits are explained by spend”. r is not a percentage.
    • Reading only the size and forgetting the sign, or the other way round.
    • Writing “spend causes visits”. Correlation shows that they move together, not why.

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