So this isn't an issue with the API, it's how GA works.
Data is processed in the timezone of the configured account. GA stores
data by day. If a session crosses a day boundary, the session is split
into 2 and a session is saved for the previous day. The current day
continues to persist. Also when data is processed and stored, the
timezone is used to compute the hour for each hit. After this happens,
since the data is stored by day, and hour is calculated, timezone
So if you play with your timezone settings a lot, the impact is that
some sessions might might be reported in different days (depending on
cross over) and hourly reports might be off.
Unfortunately, there is no change history with configuration data to
determine when this setting has changed.
On Feb 27, 8:30 am, J <ja...@sumall.com
> Can someone from GA respond to this?
> On Tuesday, February 21, 2012 4:43:27 PM UTC-5, J wrote:
> > Anyone have additional insight into this timezone issue?
> > Based on the information here: