Regarding the `gam report usage user` command

[Lora Lei 雷雨萌]

I am writing to request clarification regarding the consistency of the definition and data for the date and last login timestamp fields returned by the `gam report usage user` command.

I recently exported a user report and found some discrepancies, which I would like to understand better:

Observations:
Report Date: 2025-12-07 (PST)
Last Login Timestamp: 2025-12-08T10:48:41Z (UTC)

Issue: When converting the UTC timestamp 2025-12-08T10:48:41Z to Pacific Standard Time (PST, UTC-8), the time is displayed as 2025-12-08 02:48:41 AM.

Since this login event occurred on the morning of December 8th (Pacific Standard Time), I expected it to be categorized in the report for December 8th, not the report for December 7th.

My questions:

Could you please provide the exact definition of the date field? Does it represent a strict data cutoff time in Pacific Standard Time (PST)?

Why does a login event on December 8th (Pacific Standard Time) appear in a report entry tagged as December 7th? Is there a known delay or overlap between the update of timestamp_last_login and the report generation date?

Thank you very much.

Please consider the environment before printing this email or attachment

This email and any attachments are confidential and may also be privileged. If you are not the addressee, do not disclose, copy, circulate or in any other way use or rely on the information contained in this email or any attachments. If received in error, notify the sender immediately and delete this email and any attachments from your system. Emails cannot be guaranteed to be secure or error free as the message and any attachments could be intercepted, corrupted, lost, delayed, incomplete or amended. Master Concept Group and its subsidiaries do not accept liability for damage caused by this email or any attachments and may monitor email traffic.

[Ross Scroggs]

Here is a bit of debug output; GAM calls the API with a date (2026-01-05) in this case and Google responds with data.

Here is the API documentation:

https://developers.google.com/workspace/admin/reports/reference/rest/v1/userUsageReport/get

Notice that it's interpreting the date as PST.

send: GET /admin/reports/v1/usage/users/user%40domain.com/dates/2026-01-05?customerId=my_customer&parameters=accounts%3Alast_login_time&prettyPrint=true&alt=json HTTP/1.1

reply: 'HTTP/1.1 200 OK\r\n'

...

Got 1 Report for us...@domain.com on 2026-01-05...

This is a question for Google as GAM is simple reporting the data returned by them.

Send me a private Meet/Zoom invitation to discuss if you'd like.

Ross

----

Ross Scroggs

Ross.S...@gmail.com

On Jan 7, 2026, at 9:56 PM, 'Lora Lei 雷雨萌' via GAM for Google Workspace <google-ap...@googlegroups.com> wrote:

I am writing to request clarification regarding the consistency of the definition and data for the date and last login timestamp fields returned by the `gam report usage user` command.

I recently exported a user report and found some discrepancies, which I would like to understand better:

Observations:
Report Date: 2025-12-07 (PST)
Last Login Timestamp: 2025-12-08T10:48:41Z (UTC)

Issue: When converting the UTC timestamp 2025-12-08T10:48:41Z to Pacific Standard Time (PST, UTC-8), the time is displayed as 2025-12-08 02:48:41 AM.

Since this login event occurred on the morning of December 8th (Pacific Standard Time), I expected it to be categorized in the report for December 8th, not the report for December 7th.

My questions:

Could you please provide the exact definition of the date field? Does it represent a strict data cutoff time in Pacific Standard Time (PST)?

Why does a login event on December 8th (Pacific Standard Time) appear in a report entry tagged as December 7th? Is there a known delay or overlap between the update of timestamp_last_login and the report generation date?<usage report.png>

Thank you very much.

Please consider the environment before printing this email or attachment

This email and any attachments are confidential and may also be privileged. If you are not the addressee, do not disclose, copy, circulate or in any other way use or rely on the information contained in this email or any attachments. If received in error, notify the sender immediately and delete this email and any attachments from your system. Emails cannot be guaranteed to be secure or error free as the message and any attachments could be intercepted, corrupted, lost, delayed, incomplete or amended. Master Concept Group and its subsidiaries do not accept liability for damage caused by this email or any attachments and may monitor email traffic.

--
You received this message because you are subscribed to the Google Groups "GAM for Google Workspace" group.
To unsubscribe from this group and stop receiving emails from it, send an email to google-apps-man...@googlegroups.com.
To view this discussion visit https://groups.google.com/d/msgid/google-apps-manager/8d9f5c0d-4930-4b99-be3a-9a88ec094b89n%40googlegroups.com.
<usage report.png>