Every analytics dashboard—Google Analytics, Plausible, Fathom, WordPress stats—drops you into a default date range the moment you open it. Most offer the same list of presets: Last 7 Days, Last 30 Days, This Month, Last Month, Quarter to Date, Year to Date.
These shortcuts exist to save clicks. But they also shape what you see—and what you miss. A preset that works for one question will bury the answer to another. Here’s how to match the range to the question, and when to ignore the dropdown entirely.
Rolling windows vs. calendar blocks
Presets fall into two families: rolling windows (Last 7 Days, Last 30 Days) and calendar blocks (This Month, Last Quarter).
Rolling windows always include today (or yesterday, depending on when the tool refreshes). They slide forward every day. Last 7 Days on a Tuesday covers the prior Tuesday through Monday. On Wednesday, it shifts to cover Wednesday through Tuesday.
Calendar blocks snap to the first and last day of a period. This Month runs from the 1st to today. Last Month is the full prior month, start to finish.
Rolling windows smooth out weekly spikes—paydays, weekends, batch-send days. Calendar blocks make month-over-month comparisons clean, but they break mid-month: comparing This Month (9 days) to Last Month (31 days) produces noise, not signal.
If you want to spot a traffic drop or a spike in unsubscribes, use a rolling window. If you’re preparing a report or reconciling revenue, use a calendar block after the period closes.
When Last 30 Days hides a two-week slump
Last 30 Days is the most common default. It’s long enough to dampen daily noise but short enough to feel recent. The problem: it averages over a full month, so a bad week gets diluted by three good ones.
Say traffic tanks on November 1st because a hosting issue takes your site offline for six hours. By November 9th, Last 30 Days still includes October 10th–31st—three weeks of normal performance. The total looks fine. The trend chart shows a dip, but the summary metric undersells it.
If you suspect a recent change, shrink the window. Last 7 Days or Last 14 Days will surface the drop faster. Then compare that range to the same span one cycle earlier (week-over-week or fortnight-over-fortnight) to confirm it’s not seasonal.
Quarter to Date and the mid-quarter blind spot
Quarter to Date runs from the first day of the current quarter (January 1st, April 1st, July 1st, October 1st) to today. It’s useful if you report quarterly or run campaigns that reset every three months.
But early in a quarter—say, the first two weeks of October—you’re comparing 14 days of data to 90 days last quarter. The percentage-change figure is meaningless. Wait until at least six weeks in, or compare the first N days of this quarter to the first N days of the prior quarter using a custom range.
Most dashboards let you set two custom ranges side by side. In Google Analytics, click the date picker, choose your range, then toggle Compare and pick “Previous period” or manually enter the matching span from the prior quarter (checked November 2026, Google Analytics Help: Date comparisons).
When to build a custom range
Presets fail when your question doesn’t match a calendar or a round number of days. A few scenarios where custom ranges win:
- Campaign attribution: You ran a seven-day promotion that started on a Thursday and ended the following Wednesday. Last 7 Days won’t line up unless you check on exactly the right day. Set the range to match the campaign start and end.
- Platform migration: You moved from one newsletter platform to another on a specific date. Compare the 30 days before the switch to the 30 days after, using that migration date as the boundary.
- Seasonal comparison: You want to know if November 2026 traffic is up year-over-year. Set the range to November 1st–30th, 2026, then compare it to November 1st–30th, 2025.
- Partial-week data: It’s Saturday, and you want to see Monday–Friday performance without weekend noise. Custom range: last Monday to yesterday.
The extra two clicks pay off when the default range would mix apples and oranges.
One rule: always compare to something
A single number—4,203 visitors, 18.2% open rate—means nothing without context. Presets make it easy to add a comparison: most tools let you toggle “Compare to previous period” or “Compare to previous year.”
But “previous period” isn’t always apples-to-apples. If you’re looking at Last 30 Days on a Monday, the comparison period ends on a different day of the week, and day-of-week effects (newsletter sends, weekend dips) can skew the delta.
When precision matters, set both ranges manually so they cover the same days of the week. That way, a Monday-to-Sunday span compares to another Monday-to-Sunday span, not Monday-to-Saturday.
If your analytics tool doesn’t support dual custom ranges—some simpler dashboards don’t—export the data to a spreadsheet and calculate the comparison there.
Want more breakdowns like this? Subscribe to One Two Three Send for one operator-focused article every day—no fluff, no generic listicles, just the tooling details that matter when you’re running the show solo.