Skip to content

Guide 144 · Setup · GA4 + Tag Manager

Set a property's time zone and currency: the two choices that shape every report date

Checked 11 November 2026 · Verification: time zone change limit checked (no more than once per day = 7 changes a week at most) · Steps traced to Analytics Help, read 11 November 2026 · 5-minute read

Two fields chosen during property creation shape every report the property ever produces: the reporting time zone, which decides which date a visit belongs to, and the currency, which decides what revenue numbers mean. Both are set on the property setup screen, and both can be changed later — but the time zone change only affects data going forward, so a wrong choice leaves a flat spot or a spike in the reports. This guide sets them right the first time.

Expected signal

After step 3, the property settings show the business's time zone and currency, and the reports date visits on the business's calendar, not the visitor's.

Download the reference: the property time zone and currency reference (JSON) (923 bytes, MD5 7cb52ec352ff3fc9ef9069df9b25b610). The time zone rules from Google's setup page, with the change limit recomputed: at most 1 change a day = 7 a week.

What you need

  • A GA4 property being created, or an existing one. The fields are set during property creation and can be changed in Property settings afterwards.
  • The Editor role on the account for a new property. Adding a property needs the Editor role; changing settings on an existing property needs Editor or above at the property level.
  • The business's time zone and currency, decided in advance. Not the developer's, not the biggest market's — the business's.

The trace

  1. Set them during property creation. When creating a property, enter the property name, then select the reporting time zone and currency on the same screen. If a visitor comes to the website on a Tuesday in their time zone but it is Monday in the property's time zone, the visit is recorded as having occurred on Monday.
  2. Pick a time zone that matches the business. If the business is in Toronto, the property belongs in America/Toronto. If the chosen time zone honours daylight saving time, Analytics automatically adjusts for the time changes. Use Greenwich Mean Time if you do not want to adjust for daylight saving time at all.
  3. Pick the currency the business reports revenue in. The currency is set on the same screen as the time zone. Revenue in the reports is shown in this currency, so a Canadian shop reporting in Canadian dollars sets CAD, not USD.
  4. Change them later only when needed. The time zone and currency can be changed in Property settings after creation. Changing the time zone only affects data going forward: report data may refer to the old time zone for a short period after the update, until Analytics servers have processed the change.
  5. Limit time zone changes to one a day. Google recommends changing a property's time zone no more than once per day so Analytics can process the change. One change a day means at most 1 × 7 = 7 changes in a week, and even that pace is a sign the choice was never settled. A single well-chosen time zone needs no changes at all.
  6. Watch for the flat spot or spike. Changing the time zone can leave a flat spot or a spike in the data, caused by the time shift forwards or backwards. If a day's numbers look wrong right after a time zone change, the shift is the first suspect, not the tag.

Dead ends

DEAD END — SETTING THE TIME ZONE TO THE BIGGEST TRAFFIC SOURCE. The reporting time zone is the business's clock. A Toronto business whose visitors are mostly in Vancouver still reports on Toronto dates, because the business's day — its sales day, its reporting day — runs on Toronto time.

DEAD END — CHANGING THE TIME ZONE TO FIX A YESTERDAY PROBLEM. A time zone change only affects data going forward. It cannot re-date visits already recorded, and the shift can make the next day's numbers look wrong. The past stays on the old time zone.

DEAD END — CHANGING THE CURRENCY EXPECTING OLD REVENUE TO CONVERT. Revenue is recorded in the property's currency at the time it arrives. Changing the currency setting does not convert historical revenue figures — the old numbers stay in the old currency.

End state

The property's reporting time zone and currency match the business, set at creation and changed at most once a day since. Visits are dated on the business's calendar, revenue reads in the business's currency, and no flat spot or spike from a time shift is hiding in the reports.

Sources

Checked 11 November 2026. The time zone and currency rules above are the ones in Google's setup page, opened 11 November 2026. No step in this guide was run inside a live Analytics property, because that needs a Google sign-in and this site does not sign in as anyone. The reference file was checked in Python: its figures were recomputed from the documentation values and match the numbers on this page. Google moves menu items without warning; if a path on this page no longer matches, the linked help page is the current map.