Date ranges and comparison
One picker above every report changes the range for all of them. The thing to know first: day boundaries are evaluated in your property's time zone — not your browser's, and not UTC.
Where the picker is and what it controls#
At the top of every report page, on the trailing edge, sits a button with a calendar icon showing the active range — for example Last 30 days. When comparison is on, a smaller line beneath it names the second window, prefixed with vs.
The picker applies to every report, not only the page you opened it from. Selecting Apply reloads the page once so that every card re-reads with the new range.
Three things worth knowing early:
- Your selection lives in that browser, not on your account. It follows you across pages and across properties and survives closing the browser — but it does not travel to a second browser or to your teammates.
- The button is not rendered at all on the Realtime screens. Realtime reports run on their own fixed window and ignore the selected range.
- Heatmaps carry their own period and do not follow this picker.
The default: last 30 days#
Until you choose otherwise, every report shows Last 30 days — today plus the 29 days before it, from midnight on the first day through to the current moment.
The presets#
The left column of the panel offers eleven ready-made ranges. Those that run "to now" really do end at the current moment, not at the end of the day:
| Preset | Exactly what it means |
|---|---|
| Today | from midnight today to this moment |
| Yesterday | the whole previous day, midnight to midnight |
| Last 7 days | today and the 6 days before it |
| Last 28 days | today and the 27 days before it |
| Last 30 days | today and the 29 days before it — the default |
| Last 90 days | today and the 89 days before it |
| This week | from Sunday of this week to this moment |
| Last week | Sunday through Saturday of the previous week |
| This month | from the 1st of the Gregorian month to this moment |
| Last month | the whole previous Gregorian month |
| This year | from 1 January to this moment |
Two details that surprise people in the Persian console. Week presets start on Sunday, while the panel's calendar lays weeks out from Saturday. And This month, Last month and This year are computed on Gregorian boundaries, not Jalali ones. For a Jalali month or year, use the Custom range and click the days on the Jalali calendar — there you get exactly the days you clicked.
Custom ranges and the calendar#
Custom, at the bottom of the preset list, shows two months side by side. Click the start day, then the end day; if the second is earlier than the first, AdPix swaps them for you. The chosen range is also spelled out as text under the calendar so you can check it before selecting Apply.
In the Persian console this calendar is fully Jalali: month names, day numbers in Persian digits, and weeks starting on Saturday. What you pick is what you get; the conversion to Gregorian happens quietly behind the scenes.
The property time zone — the most important section here#
Every window boundary, and every day, hour and month bucket in the reports, is evaluated in the property's time zone.
The setting lives at Admin → Property details → Time zone. When nothing is set, or the value cannot be resolved, AdPix falls back to UTC.
Three consequences that land directly on your numbers:
- The day you select is your local day. For a property on
Asia/Tehran, "yesterday" runs Tehran-midnight to Tehran-midnight — not a window that starts at UTC midnight and sits three and a half hours off. - The daily chart is cut on the same boundaries. A 2 a.m. sale lands on the right day, not the day before.
- Everyone on the team sees one number. A colleague in Tehran and a colleague in Berlin opening "yesterday" get the identical window. The viewer's browser time zone plays no part in the calculation.
This is the single largest source of "your numbers are wrong" reports. If another dashboard closes its days in UTC or in a different zone, its daily figures will not match AdPix — and neither of them is wrong. The definition of a day differs. Make the two tools' time zones equal first, then pull identical ranges.
Two operational notes: a time-zone change takes up to about a minute to reach the reports, and once it does, the entire history is re-read on the new boundaries. Nothing is reprocessed — days are cut at read time — so last month's numbers can shift slightly too. The rest of the property settings are covered in Property settings.
The days you click on the calendar are resolved against your own device's clock and then read as days in the property's time zone. If your computer's clock or zone is set wrong, "today" can land a day early or late.
Comparing with a previous period#
At the bottom of the panel, the Compare checkbox adds a second window to every request. Ticking it opens a dropdown with four modes:
| Mode | How the second window is built |
|---|---|
| Previous period | the same length, ending the day before the primary range starts |
| Previous period (match day of week) | the same range shifted back by the nearest number of whole weeks, so Saturday lines up with Saturday |
| Previous year | the same dates one Gregorian year earlier |
| Custom | two dates you enter yourself |
Match-day-of-week exists for businesses with a weekly rhythm: comparing a 30-day range against the 30 days before it pairs a Thursday with a Tuesday and shuffles the weekday mix. The trade-off is that rounding the shift to whole weeks can leave the second window overlapping the primary range by a day or two — on a 30-day range, the shift is 28 days.
The two date boxes in the Custom comparison mode are the browser's own date inputs and show a Gregorian calendar — unlike the Jalali calendar above them in the same panel. If you would rather work in Jalali dates, build the second window with one of the other three modes.
Where comparison shows up#
- Under each headline tile, a percentage change: green with ▲ for growth, red with ▼ for a fall. When the previous value is zero and the current one is not, the change reads 100%.
- On the Home users chart, a second line for the previous period.
- On the acquisition chart, the previous period layered under the primary one.
- On the funnel, a dashed ghost bar for the previous period at each step, the percentage-point change above it, and the change in overall conversion at the end of the strip under the chart.
The screens that understand comparison: Home, Acquisition overview, Traffic acquisition, Engagement, Events, Funnel, Demographics and Tech. Other reports accept the second window and ignore it — nothing breaks, nothing changes.
Tables are never compared. To see how a country, a channel or a browser moved between two periods, select each range separately and export the CSV.
Home always computes the immediately preceding window of equal length, so the dashed trend line and the tile deltas are ready the moment you need them. Nothing is drawn until Compare is ticked, though — an unasked-for comparison used to leave readers unable to tell what a number was measured against. Tick Compare and pick another mode and that window replaces the automatic one.
The range in CSV exports#
Every Download CSV link in the reports carries the range and property selected on screen. There is nothing to edit in the download URL.
The comparison window is not included: an export always covers the primary range only. For a spreadsheet comparison, pull two files and put them side by side.
Frequently asked questions#
Why doesn't AdPix's "yesterday" match my other tool's?
Almost always the time zone. AdPix cuts days in the property's time zone; the other tool may cut them in UTC or its own account time zone. For a property on Asia/Tehran, a UTC-based report attaches the first three and a half hours of each local day to the previous one. Align both time zones first, then compare.
Does the range I pick change what my colleagues see?
No. Your selection is stored in that browser, not on your account. On another browser or device you pick again, and each colleague has their own. In exchange it stays put across pages and properties until you change it yourself.
Does "This month" follow a non-Gregorian calendar in the Persian console?
No. The custom-range calendar renders as Jalali in Persian, but the This month, Last month and This year presets are computed on Gregorian calendar boundaries. For a Jalali month, use Custom and click the first and last day on the Jalali calendar.
Why does comparison change nothing in the tables?
Comparison recomputes only the headline tiles over the second window, plus the previous-period line on the Home chart and the ghost bars on the funnel. Tables and the other charts always show the primary range; for a row-by-row comparison, export CSV twice.
Thanks — your feedback helps us improve the docs.