> For the complete documentation index, see [llms.txt](https://helpcenter.channable.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://helpcenter.channable.com/changelog/2026/july/offset-date-ranges-for-insights-google-ads.md).

# Offset date ranges for Insights (Google Ads)

July 22, 2026

### What's new?

Before this release, rolling date ranges in **Google Ads Insights** always ended today.

You could use a fixed date range to view earlier dates. However, fixed ranges stay on the same dates.

Now, you can choose an earlier end date for a rolling range. The range still moves forward automatically.

This lets you exclude recent data while keeping your view up to date.

{% hint style="info" %}

#### Example use cases

* **Wait for data to settle:** View three weeks ending one week ago. This leaves out the newest week, when results can still change.
* **Compare seasonal performance:** View 30 days ending one year ago. Compare those results with your current 30-day period.
* **Review performance before a promotion:** View a period before a recent sale. This shows results without the promotion's impact.
  {% endhint %}

### Availability

This feature is currently available for **Google Ads Insights** only.

Learn more about how to use [Insights for Google Ads](/manage-improve-product-data/insights/insights-for-ads/insights-for-google-ads.md).


---

# 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://helpcenter.channable.com/changelog/2026/july/offset-date-ranges-for-insights-google-ads.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.