> For the complete documentation index, see [llms.txt](https://docs.pentaho.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.pentaho.com/pdia-data-integration/10.2-data-integration/pdi-transformation-steps-reference-overview/google-analytics-v4/google-analytics-v4-options/google-analytics-v4-date-ranges-tab.md).

# Date ranges tab

The Google Analytics Data API allows up to [four date ranges](https://developers.google.com/analytics/devguides/reporting/data/v1/rest/v1beta/DateRange) to be specified per report request. A minimum of one date range is always required. If more than one date range is used, a special dimension called `DateRange` must be added as an output field in order to separate stacked output rows.

![Google Analytics v4 Date ranges tab](https://2745965000-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FvZoINBz5C5WnDZQlbOJQ%2Fuploads%2Fgit-blob-43c5f8dbd9867c952921516bdf357957875ca0ed%2FPDI%20Google%20Analytics%20step%20Date%20ranges%20tab.png?alt=media)

| Field          | Description                                                                                                                                    |
| -------------- | ---------------------------------------------------------------------------------------------------------------------------------------------- |
| **Range name** | Specifies the optional name of the date range. This name displays in the **DateRange** dimension of an output report.                          |
| **Start spec** | Specifies the starting day of the date range. Value formats can be provided in `YYYY-MM-DD`, `NdaysAgo`, or values of `today` and `yesterday`. |
| **End spec**   | Specifies the ending day of the date range. Value formats can be provided in `YYYY-MM-DD`, `NdaysAgo`, or values of `today` and `yesterday`.   |


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.pentaho.com/pdia-data-integration/10.2-data-integration/pdi-transformation-steps-reference-overview/google-analytics-v4/google-analytics-v4-options/google-analytics-v4-date-ranges-tab.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
