Google Ads Account Time Zone and Currency: The Two Settings You Can Never Change
Two settings in Google Ads get chosen in ten seconds while creating an account, and then govern everything: how you read reports, when the day ends for daily budget purposes, which currency the invoice arrives in, and why your numbers never reconcile with analytics. Those settings are the Google Ads account time zone and the account currency. Neither can be changed afterwards — not “difficult”, genuinely not possible.
Below: what is locked permanently, what can still be adjusted, how these two settings show up in day-to-day work, what your options are if the choice was already made badly, and the checklist to run before creating the next account.
What is permanent and what is not
| Setting | Changeable? | Details |
|---|---|---|
| Interface language | Yes, any time | Affects what you see only — nothing about how ads serve |
| Number format | Yes | Thousands and decimal separators; options depend on the chosen language |
| Time zone | Effectively no | Not supported in standard serving accounts. A manager account can have its time zone reset once, and only eastward |
| Currency | No | It determines how you are billed. The only path to a different currency is a new account |
One more technical constraint on time zones: every available zone sits at a full-hour or half-hour offset from GMT. And if you do fall into the manager-account scenario, the shift is only ever available in one direction — eastward. There is no way back.
Which leads to the point worth stating outright: time zone and currency are not configuration, they are architecture. They belong in the pre-launch decision set alongside account structure, not in the rush to click “create”.
Where the Google Ads account time zone shows up in real work
Day boundaries and daily budget
Daily budget is spent within a day defined by the account time zone. If the account sits in a different zone from the market you advertise to, the campaign “day” starts and ends out of step with when your audience wakes up and goes to bed. The practical effect: an evening demand peak can be cut in half by the day boundary, with the back half spending tomorrow’s budget.
Layer on top of that how spend is actually paced — the system may exceed the daily figure on individual days and compensate across the month. The mechanics are in the piece on Google Ads budget pacing, which also explains why a badly chosen time zone makes overspend look more chaotic than it is.
Ad scheduling
Dayparting is expressed in the account time zone, not the user’s local time. “Run from 9 to 18” means 9 to 18 by account clock. For an account in the same zone as the audience, no difference. For an account created elsewhere, every interval needs recalculating — and daylight-saving transitions land on different dates in different countries, so the offset is not even constant. The scheduling logic itself is covered in the article on ad scheduling and dayparting.
Conversion dates
A conversion is recorded on the date in account time. The click happened at 11pm local on the 31st, the conversion fired after midnight — and in your report it may land in the following month. On monthly views that produces a systematic gap against finance and CRM records, which teams often write off for years as “attribution noise”.
Billing always runs on Pacific time
A separate trap: billing pages and documents display in Pacific time regardless of the account’s own zone. Campaign spend and billed spend are therefore counted across different days. For daily reconciliation that means the two figures are not obliged to match — and that is not a bug. How charges and thresholds actually work is in the piece on Google Ads billing.
Why Google Ads never matches GA4
The perennial argument between the media buyer and the analyst. In most cases it is not one cause but a stack of four, and the time zone is the most overlooked of them.
| Cause | How it looks | What to do |
|---|---|---|
| Account and GA4 property in different time zones | Data shifts around the day boundary; most visible on daily views | Align the GA4 property zone with the ad account where possible, otherwise compare weekly rather than daily |
| Different attribution models | Google Ads reports more conversions than GA4 shows for paid | Compare like-for-like reports, not “conversions in the account” against “sessions in analytics” |
| Different counting windows | The conversion sits on the click date in the account and the event date in GA4 | Understand the difference; do not try to drive it to zero |
| Signal lost browser-side | GA4 sees less than the ad account does | Server-side collection and correct tagging |
The core point: reconciling the two systems exactly is neither possible nor necessary. The job is to know where the gap comes from and to nominate one system as the source of truth for decisions. Which model to trust for paid traffic is unpacked in the piece on GA4 attribution for media buyers.
Currency: what it sets beyond the invoice
Currency determines how you are billed and cannot be changed without a new account. But its reach goes well past the invoice.
- Conversion value. When the site sends value in the shop’s currency and the account runs in another, values are converted at an exchange rate. Fine, as long as you remember the conversion exists when reconciling with finance. How to structure conversion value in the first place is in the article on conversion value and value rules.
- Target ROAS. The target is a dimensionless ratio, but the amounts feeding it are already converted. Under a meaningful currency move, a target set six months ago now represents a different real margin in your reporting currency.
- Product feed. Feed prices must match site prices, and feed currency is a separate object from account currency. A mismatch produces product disapprovals, not a gentle warning.
- Cross-account reporting. A manager account converts everything into its own currency at a rate. For financial reconciliation that figure is always approximate. How the hierarchy and shared resources work is in the breakdown of the Google Ads manager account.
Daylight saving: where it breaks
The offset between your account zone and your market is not constant. Countries shift their clocks on different dates, some never shift at all, and twice a year the gap between your account and your audience moves by an hour. For anyone running on dayparting and hourly analysis, that means two weeks a year when the schedule is quietly wrong.
What to do about it:
- put both transition dates in the team calendar and review ad schedules by hand on those days;
- do not draw conclusions from hourly breakdowns in a week containing a clock change;
- if the business genuinely depends on time of day, pick the account zone by market rather than by office — that removes the problem entirely.
Time zones in exports and BI
A separate story is data leaving the account for reporting. API and interface exports return dates in the account time zone, while your warehouse may interpret them as UTC or in the server’s zone. At daily granularity that produces the classic one-day shift people then hunt for in formulas for weeks.
Minimum hygiene: pin the time zone explicitly on the warehouse side instead of relying on a default, and document in the report itself which clock its dates are on. When a report merges several sources — ad account, analytics, CRM, finance — align their zones before joining, not after.
Multi-country structure: one account or several
“Should we split markets across accounts?” is usually debated in terms of convenience. In practice time zone and currency decide it, because everything else can be fixed later and these two cannot.
| Situation | Sensible answer |
|---|---|
| Neighbouring time zones, one billing currency | One account, separated by campaign |
| Markets 6+ hours apart, still one currency | One account is workable, but scheduling needs recalculating; if dayparting is central to performance, split |
| Separate legal entity with its own billing currency | Separate account — the currency will never change anyway |
| Different teams with separate budgets and reporting lines | Separate accounts under one manager account |
If you are entering a new market and facing this for the first time, work through the full decision set — structure, localisation, measurement — in the piece on an international campaign launch.
One account is easier to manage; several are more honest in reporting. You get to make that choice once, because migrating later costs more than it looks.
If the choice was already made wrong
There is exactly one remedy: a new account. Which surfaces the part nobody plans for — structure can be carried across, history cannot. Campaigns, ad groups, keywords and ads copy over via the editor or in-interface copy. Statistics, trained bidding strategies, accumulated audiences and conversion history stay behind.
Practically, the new account starts as a new account: strategies have to re-accumulate data, and the first weeks after the move cost more. A sequence that limits the damage:
- Create the new account with the correct zone and currency, and verify both before launching anything.
- Set up conversions and analytics links in the new account before moving campaigns.
- Move the structure but launch in waves: the most stable campaigns first, the rest after.
- Keep the old account live through the transition so you do not zero out impressions entirely.
- Do not change bidding strategies and structure at the same time — one migration at a time.
- Export historical reporting from the old account while access is still convenient.
Audiences deserve a specific warning: they do not travel with campaigns, and the new account starts collecting from scratch. The thresholds and durations you will be working against are covered in the piece on the Google Ads Audience Manager. The same applies to offline uploads if you run them — mechanics in the article on store sales via the Data Manager API.
Currency and unit economics
For a team that reports in one currency and pays for media in another, the exchange rate becomes a silent participant in the model. Spend is recorded in account currency, revenue arrives in settlement currency, and the gap between them has a life of its own.
Three practical consequences:
- ROI is computed at the rate on the date, not at the rate today. When a month passes between spend and payout, the rate moves — and that is a real profit factor, not an accounting artefact.
- Strategy targets age. A target CPA set in account currency six months ago corresponds to a different amount in your reporting currency now. Targets deserve a review when the rate moves materially, not only when the economics change.
- Period comparisons need a caveat. Spend up 10% while the rate moved 8% is barely growth at all. Year-on-year comparisons without normalising for currency are actively misleading.
If your economics are seasonal and budgets are planned ahead, fold the rate into planning alongside bids and demand — the planning logic is in the piece on seasonality and budget planning.
A checklist before creating an account
- Identify the primary market. The time zone follows the market, not where the team sits.
- Decide who pays and in what currency. Account currency should match the entity’s billing currency, or every reconciliation becomes a conversion exercise.
- Align with the GA4 property zone if analytics already exists — better to resolve the mismatch before launch.
- Ask whether dayparting matters. If it does, the zone must match the market.
- Confirm invoicing requirements — entity details, tax data, payment method.
- Settle the structure question — one account for all markets, or several under a manager.
- Write the decision down. In a year nobody will remember why that zone was chosen, and the question will come up.
The special case: agency and rented accounts
When you work in an account handed to you ready-made, the time zone and currency are already fixed, and arguing about them is pointless — they are inputs to the problem. What matters is what you do with them:
- establish the zone and currency before launch, not after the first weekly reconciliation;
- recalculate ad scheduling against the account’s actual zone;
- agree which system is the source of truth for spend — the account or billing;
- build currency conversion into the unit-economics model when account currency differs from your payout currency.
That is exactly why “which zone, which currency” belongs in the questions you ask at handover. At PPC Rebels it is part of the input parameters when issuing agency Google Ads accounts, alongside business verification. And if you are assembling your own launch playbook and would rather not learn this the expensive way, the base decision sequence is laid out in the Google Ads guide.
FAQ
Can I change the time zone in Google Ads?
Not in a standard serving account — the change is not supported. A manager account can be reset once, and only eastward. In every other case the answer is a new account.
Can I change the account currency?
No. Currency defines how you are billed and is fixed at account creation. A different currency means a different account.
Which clock does the daily budget follow?
The account time zone. The campaign day begins and ends on that clock, not on the audience’s local time.
Why doesn’t reported spend match my invoice?
Billing pages display in Pacific time regardless of the account’s zone, so campaign reports and invoices count spend across different days.
Does ad scheduling follow the user’s local time?
No, it follows account time. When account and market sit in different zones, every interval needs recalculating — and daylight-saving dates differ by country, so the offset is not constant.
Why don’t Google Ads and GA4 agree?
Typically four causes stack up: different time zones, different attribution models, different counting windows, and signal lost in the browser. You cannot reconcile them to zero; pick a source of truth instead.
What happens to history if I create a new account?
Campaign structure can be copied; history cannot. Statistics, trained bidding strategies and accumulated audiences stay in the old account, and the new one starts cold.
One account for several countries, or separate ones?
Close time zones and a single billing currency are fine in one account split by campaign. Different billing currencies, widely separated zones, or separate reporting lines justify separate accounts under one manager.
How does currency affect conversion value?
Values sent in another currency are converted at a rate. That affects reconciliation with finance, and it means a target ROAS set long ago represents a different real margin once the rate has moved.
Which time zone should I pick if the team and the market are in different countries?
Follow the market. The zone drives day boundaries, ad scheduling and conversion dates — that is, how the advertising behaves, not how convenient your reports feel.
Does the time zone affect where ads are shown?
No. It is an administrative setting: it defines the day boundary and report timestamps, not geographic targeting.
What should I check first in an account I inherited?
Time zone and currency — before reconciling any numbers or building a schedule. They are the inputs that explain half of the reporting discrepancies you are about to find.
Time zone and currency are the only Google Ads settings that cannot be fixed retroactively. Ten seconds of attention at account creation saves a migration that costs months of accumulated history.
