Date ranges, timezones, currency
Date picker, timezone (workspace default), currency (workspace default with FX conversion). Late attribution caveat 24-72h.
Written By Salvatore Sinigaglia
Last updated About 5 hours ago
Date picker, timezone (workspace default), currency (workspace default with FX conversion). Late attribution caveat 24-72h.
Date ranges, timezones, currency
Date picker: Today, Yesterday, Last 7d, Last 30d, This month, Last month, Custom. Timezone: workspace default (team-106); per-user can override personal display. Currency: workspace currency default; cross-platform rollups auto-convert via daily FX. Late attribution caveat: data settles 24-72h. Boundary issues at midnight TZ.
Who is this for
Mediabuyers reading any Ads Manager / Reports view. Anyone confused about why numbers differ between Wevion and native platform UIs.
Date range picker
Available shortcuts:
Date selection persists across pages (set once, applies until you change).
Timezone
Workspace timezone (computational)
Set in team-106 Workspace Defaults. Affects:
- Daily rule evaluation (rules fire at midnight workspace TZ)
- Daily digest delivery (cron uses workspace TZ)
- "Today" / "Yesterday" boundary for reports
- Scheduled report fire times
- Audit log display (default; toggle to UTC available)
Set once per workspace; don't change frequently (causes data boundary discontinuities).
Personal timezone (display)
Set per-user at team-117 personal profile. Affects:
- Your in-app clock display (header)
- Your "now" reference for relative timestamps
- Your dashboard's "Today" filter interpretation (some users may see different "today" depending on personal TZ)
Doesn't affect underlying data (computational).
Cross-team timezone reality
When teams are distributed across TZs:
- Pick workspace TZ where decisions get made (usually owner's TZ)
- Each member sees their personal clock in header
- Reports use workspace TZ consistently
- Some confusion possible: "your morning report shows yesterday" if you're in different TZ
Accept this as part of distributed-team workflow.
Timezone vs platform native
Ad platforms (Meta, Google, etc.) have their own timezone settings:
- Meta: default Pacific Time
- Google Ads: per-customer (Customer-set)
- TikTok: per-advertiser
When comparing Wevion vs platform native:
- Same metric, different TZ boundaries = different totals
- Example: "Last 7 days" in workspace TZ Europe/Rome vs platform Pacific Time = 7-9 hour offset means different day boundaries
- For reconciliation: set platform's UI to match workspace TZ OR accept the discrepancy
Wevion's data is correct for workspace TZ. Platform's native UI is correct for platform TZ. Both can be "right" simultaneously.
Currency
Per-account native currency
Each ad account has its own currency (set at account creation, immutable):
- Meta ad account: e.g. USD or EUR or GBP
- Google Ads customer: same
- TikTok advertiser: same
- Taboola Backstage: same
- Snapchat: same
Wevion respects each account's native currency in per-account views.
Workspace currency (for rollups)
Set in Workspace Defaults. Used for:
- Cross-account aggregation (dashboard KPI strip total spend)
- Cross-channel reports (Cross-Channel Analytics)
- Multi-platform totals (mixing Meta USD + Google EUR)
Wevion auto-converts via daily FX rate (from ExchangeRate-API.com).
FX conversion implications
For dollar-perfect reconciliation: use per-account native currency in Wevion + match platform's native UI.
For trend / strategic analysis: workspace currency rollup is fine.
Late attribution
Conversion data settles over time:
- Hour 0-24: rapid (most events arrive within 1h)
- Hour 24-72: late attribution (Meta credits view-through up to attribution window)
- Day 3-7: trickle (some apps' install events delayed)
- Day 7-28: Meta view-through window can complete
So Day 1 ROAS may settle higher by Day 7 as more conversions attributed.
Don't make permanent decisions on Day 1 data. Wait 3 days minimum. 7 days ideal.
Boundary issues at midnight
At midnight workspace TZ:
- "Today" filter rolls over to next day
- Daily reports cover yesterday
- Some users may see brief inconsistency during the rollover minute
If you're working at exactly midnight: refresh after a minute.
Default + persistence
Date range persists across page navigation within a session:
- Set "Last 7 days" on Ads Manager → also Last 7 days on Reports
- Refresh page: persists
- Log out + back in: defaults to Last 7 days again
To set different defaults per page: not currently supported; same default everywhere.
What you'll see
Date picker:
- Top of Ads Manager + Reports
- Default: Last 7 days
- Active range shown as chip + click to change
Timezone hint:
- Some reports show "Times in workspace TZ Europe/Rome" footer
- Audit log timestamps in workspace TZ
Currency:
- Per-row in account's native currency (typical)
- Total / aggregated in workspace currency
- Conversion notation if cross-currency
Common questions
- "Why is my ROAS 2x in Wevion but 2.5x in Meta?": timezone or attribution window. Verify both match.
- "Why is total spend $X in Wevion + $Y in Stripe?": FX timing or platform-side fees vs gross spend.
- "Can I see per-day breakdown?": yes, in Reports → Per-day aggregation OR custom date range "today" to see only today.
- "Late attribution affecting my decisions": wait 3-7 days for conversion-driven decisions.
- "Workspace TZ wrong": admin updates via Settings → Workspace Defaults. Takes effect on next sync cycle.
Best practices
Set workspace TZ at the start
Get the TZ right at workspace creation. Changing later causes data discontinuities.
Use "Last 7 days" default
Better than "Today" for daily decisions (more stable, accounts for late attribution).
Reconcile with platform monthly
Once a month: compare Wevion totals vs platform native UIs. Investigate discrepancies > 5%.
Use workspace currency for strategic, native for tactical
- Strategic (cross-platform allocation): workspace currency
- Tactical (per-platform optimization): native currency
FAQ
Which timezone does Wevion use for reports?
Wevion uses the workspace default timezone for computational purposes, which drives the Today and Yesterday boundary for reports, daily rule evaluation, digest delivery, and scheduled report fire times. Each user can also set a personal timezone that affects only their in-app clock display and relative timestamps, not the underlying data.
Why do Wevion numbers differ from the native platform UI?
Differences usually come from timezone boundaries and attribution windows. Platforms like Meta, Google Ads, and TikTok have their own timezone settings, so the same metric over "Last 7 days" spans different day boundaries. Wevion is correct for the workspace timezone and the platform is correct for its own timezone, so both can be right at once.
How does Wevion convert currency across platforms?
Each ad account keeps its own native currency in per-account views. For cross-account and cross-channel rollups, Wevion converts into the workspace currency using a daily FX rate (from ExchangeRate-API.com), applying that day's rate to the whole day's data. Historical data keeps its original rate and is not re-converted later.
Why does my Day 1 ROAS change later in Wevion?
Conversion data settles over time due to late attribution. Most events arrive within the first 24 hours, but late attribution continues from hour 24-72 and Meta's view-through window can complete over 7-28 days, so Day 1 ROAS may settle higher by Day 7. Wevion advises waiting at least 3 days, ideally 7, before permanent decisions.
What date ranges can I pick in Wevion?
Wevion's date picker offers Today, Yesterday, Last 7 days, Last 30 days, This month, Last month, This quarter, and Custom for arbitrary windows. The selected range defaults to Last 7 days and persists across pages within a session, resetting to Last 7 days after you log out and back in.