1. Lighthouse

Level 6 · Marketing spend per channel

The request

From Jordan Reyes, Head of Marketing

“Finance wants a one-glance view of our ad budget. Per channel: how many days we have spend for, the total over all three years, and what a typical day costs.”

Your goal

Set result to a DataFrame from marketing_spend with one row per channel and columns channel, days (number of rows), total_spend (sum of amount, rounded to 2) and avg_daily (mean amount, rounded to 2), sorted by total_spend descending, index reset.

  • Use the marketing_spend DataFramenot done yet
  • Show exactly channel days total_spend avg_dailynot done yet
  • 3 rows, sorted as askednot done yet

Your code

Python

Loading the editor…

    ResultPreview of marketing_spend · press Run to see yours
    Preview of marketing_spend
    spend_datechannelamount
    2023-01-01paid492.99
    2023-01-01email37.38
    2023-01-01social200.53
    2023-01-02paid709.13

    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.

    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
    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

    The lesson

    The whole summary in one agg

    marketing_spend has one row per day and channel: the date, the channel (paid, email or social) and the amount spent. Jordan’s three questions are three aggregations of the same groups, so one named agg answers them all:

    marketing_spend.groupby("channel", as_index=False).agg(
        days=("spend_date", "count"),
        total_spend=("amount", "sum"),
        avg_daily=("amount", "mean"),
    )

    Each keyword is an output column and each tuple says which column to aggregate and how. With as_index=False, channel stays an ordinary column, ready to sort and share.

    Reading the numbers

    channel days total_spend avg_daily
    paid 1091 888,774.13 814.64
    social 1093 345,764.76 316.34
    email 1092 100,187.71 91.75

    Paid spend is about 2.6 times social and nearly 9 times email. That’s normal for an online store: paid search and shopping ads cost money per click, while email costs little once the list exists.

    The days column holds a small surprise. 2023 to 2025 has 1,096 days, yet no channel has 1,096 rows. A handful of days are missing for each channel (tracking outages). For this summary that’s fine: the mean is the average of the days we have. Just don’t divide the total by 1,096 and call that the same number. Checking a count against the number you expect is a habit worth keeping, because gaps like these change totals and averages.

    Sorting a summary

    The ticket asks for the biggest channel first, so sort by total_spend with ascending=False and reset the index. Sorting by the rounded or the unrounded total gives the same order here, because no two channels are close. Rounding with a dictionary, .round({"total_spend": 2, "avg_daily": 2}), rounds only the money columns and leaves the day counts untouched.

    Common mistakes

    • Using "size" or "count" on amount and calling it spend.
    • Rounding amount before summing, which adds up rounding errors over 3,000 rows.
    • Forgetting as_index=False, so channel becomes the index and the column check fails.
    • Dividing the total by the number of calendar days instead of taking the mean of the rows.

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