1. Lighthouse

Level 6 · Find and fill the tracking gaps

The request

From Jordan Reyes, Head of Marketing

“Our spend tracker had a few outages, so some days have no row for a channel. The money was still spent. How many days are missing per channel, and what's the total if we carry the previous day's spend into each gap?”

Your goal

marketing_spend should have one row per day and channel from 2023-01-01 to 2025-12-31. Set result to a DataFrame with columns channel, missing_days (days in that range with no row for the channel), recorded_total (sum of amount as recorded, rounded to 2) and filled_total (sum after filling each missing day with the previous day's amount for that channel, rounded to 2), one row per channel, sorted by channel A to Z, index reset.

  • Use the marketing_spend DataFramenot done yet
  • Show exactly channel missing_days recorded_total filled_totalnot 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

    Missing rows are invisible

    A missing value you can see is easy: it’s NaN, and isna() finds it. A missing row is harder. If the tracker had an outage on 28 January 2023, there simply is no paid row for that day, and nothing in the table tells you so. resample and rolling happily run over the hole, and a rolling(7) window quietly covers 8 calendar days.

    The fix is to put the data on a complete calendar, so every day that should exist has a row, and the missing ones show up as NaN.

    asfreq for one series

    For a single series with a DatetimeIndex, asfreq("D") does it in one call:

    paid = marketing_spend[marketing_spend["channel"] == "paid"].set_index("spend_date")["amount"]
    len(paid)                 # 1091
    filled = paid.asfreq("D")
    len(filled)               # 1096
    filled.isna().sum()       # 5

    asfreq builds a regular daily index from the first to the last date and inserts NaN where there was no row. Three years is 1,096 days (2024 is a leap year), so the paid channel is missing 5 days.

    reindex with date_range for many columns

    asfreq only fills between the first and last date present. If the whole first week were missing, it couldn’t know. pd.date_range lets you state the expected calendar explicitly, and reindex puts the table on it:

    days = pd.date_range("2023-01-01", "2025-12-31", freq="D")
    wide = marketing_spend.pivot(index="spend_date", columns="channel", values="amount").reindex(days)
    wide.isna().sum()
    # email 4, paid 5, social 3

    pivot turns the long table into one column per channel (chapter 9 covers it in depth), so all three channels get checked against the same calendar at once.

    Choosing a fill

    Once the gaps are visible, you decide what they mean. For paid spend, the daily average comes out differently depending on that choice:

    • Skip them (the default for mean() and sum()): average $814.64 over the 1,091 recorded days.
    • fillna(0): “nothing was spent”. Average $810.93 over 1,096 days. Wrong here: the money was spent, only the tracking failed.
    • ffill(): carry the last known value forward. The total rises from $888,774.13 to $892,327.94.
    • interpolate(): a straight line between the neighbours, total $892,420.97.

    Zero is right when a missing day really means zero (no orders on a closed day). Forward fill or interpolation is right when the value existed but wasn’t recorded. Say which one you used.

    Common mistakes

    • Running rolling(7) on a series with missing days, so the window is longer than a week.
    • Using fillna(0) for an outage, which understates spend and overstates return on ad spend.
    • Using asfreq when gaps may sit at the very start or end of the range; reindex with an explicit date_range catches those.
    • Forgetting that sum() and mean() skip NaN, so a table with gaps still “adds up”, just to the wrong number.

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