Budgets with different time zones

If your budget contains ad accounts that operate in different time zones, it can affect when certain updates occur in Adpulse.

This mainly impacts budgets that use AutoPacing or Budget Rollovers, particularly when one schedule ends (typically at the end of the month) and a new schedule begins.

Each ad platform determines its time zone slightly differently.

This behaviour mainly affects budgets using AutoPacing or Rollovers when a schedule ends and a new one begins.

Adpulse must wait until the day has ended for all ad accounts in the budget before it can:

If the ad accounts in the budget operate in different time zones, the system must wait until the latest time zone reaches the end of the day before performing these calculations.

Imagine a budget with three ad accounts:

If the budget schedule ends on the 31st, the rollover cannot be calculated until the 31st has ended in the latest time zone used by the accounts in that budget.

In this case, the latest time zone is UTC.

Although the Google and Meta accounts are already in the next day in Sydney, Adpulse must wait until midnight UTC before it can complete the rollover calculation.

Midnight UTC occurs at 11:00 AM Sydney time.

After the day ends, it typically takes up to three hours for platform data to finalise and for Adpulse to complete its calculations.

This means the new schedule would typically become active around 2:00 PM Sydney time on the 1st.