Try the MCP server for Google Analytics. Install from
GitHub, and see the
announcement for more details.
AccessDateRange
Stay organized with collections
Save and categorize content based on your preferences.
A contiguous range of days: startDate, startDate + 1, ..., endDate.
| JSON representation |
{
"startDate": string,
"endDate": string
} |
| Fields |
startDate |
string
The inclusive start date for the query in the format YYYY-MM-DD. Cannot be after endDate. The format NdaysAgo, yesterday, or today is also accepted, and in that case, the date is inferred based on the current time in the request's time zone.
|
endDate |
string
The inclusive end date for the query in the format YYYY-MM-DD. Cannot be before startDate. The format NdaysAgo, yesterday, or today is also accepted, and in that case, the date is inferred based on the current time in the request's time zone.
|
Except as otherwise noted, the content of this page is licensed under the Creative Commons Attribution 4.0 License, and code samples are licensed under the Apache 2.0 License. For details, see the Google Developers Site Policies. Java is a registered trademark of Oracle and/or its affiliates.
Last updated 2025-04-02 UTC.
[null,null,["Last updated 2025-04-02 UTC."],[[["\u003cp\u003eDefines a date range using a start date and an end date, inclusive of both.\u003c/p\u003e\n"],["\u003cp\u003eDates are represented in \u003ccode\u003eYYYY-MM-DD\u003c/code\u003e format or using relative terms like \u003ccode\u003eNdaysAgo\u003c/code\u003e, \u003ccode\u003eyesterday\u003c/code\u003e, or \u003ccode\u003etoday\u003c/code\u003e.\u003c/p\u003e\n"],["\u003cp\u003e\u003ccode\u003estartDate\u003c/code\u003e cannot be after \u003ccode\u003eendDate\u003c/code\u003e, and \u003ccode\u003eendDate\u003c/code\u003e cannot be before \u003ccode\u003estartDate\u003c/code\u003e.\u003c/p\u003e\n"],["\u003cp\u003eThe date values are interpreted based on the request's time zone.\u003c/p\u003e\n"]]],["The core content describes a JSON structure for representing a date range. The JSON object contains `startDate` and `endDate` fields, both strings. These fields define an inclusive range of days. The format `YYYY-MM-DD` is required, but `NdaysAgo`, `yesterday`, and `today` are also valid and will infer the date from the request's time zone. `endDate` must not be before `startDate`, and `startDate` must not be after `endDate`.\n"],null,["# AccessDateRange\n\n- [JSON representation](#SCHEMA_REPRESENTATION)\n\nA contiguous range of days: startDate, startDate + 1, ..., endDate.\n\n| JSON representation |\n|----------------------------------------------------|\n| ``` { \"startDate\": string, \"endDate\": string } ``` |\n\n| Fields ||\n|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|\n| `startDate` | `string` The inclusive start date for the query in the format `YYYY-MM-DD`. Cannot be after `endDate`. The format `NdaysAgo`, `yesterday`, or `today` is also accepted, and in that case, the date is inferred based on the current time in the request's time zone. |\n| `endDate` | `string` The inclusive end date for the query in the format `YYYY-MM-DD`. Cannot be before `startDate`. The format `NdaysAgo`, `yesterday`, or `today` is also accepted, and in that case, the date is inferred based on the current time in the request's time zone. |"]]
