Date range control
Stay organized with collections
Save and categorize content based on your preferences.
If you are working with a data source that requires a date range when fetching
data, you can take advantage of the Looker Studio date range features.
To enable the date range control feature for your Community Connector, set
dateRangeRequired to true in your
getConfig response. Then,
Looker Studio will include a start and end date with every
getData request made to your
connector.
getData behavior when dateRangeRequired is true
When dateRangeRequired is set to true in your getConfig response, each
getData request will contain a
dateRange object with startDate and endDate parameters. The date
parameters will be in YYYY-MM-DD format. You can use these values in data
fetch requests to third-party services.
- By default, the date range provided will be the last 28 days, excluding
today.
- If a user applies a date range filter for a report then the date range
provided will reflect the user selection.
- When Looker Studio is attempting to detect
semantic types,
sampleExtraction is set to
true in getData requests. For these requests, the date provided for the
start and the end date is two days earlier than today.
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 2024-09-18 UTC.
[null,null,["Last updated 2024-09-18 UTC."],[[["\u003cp\u003eWhen fetching data requiring a date range, leverage Looker Studio's date range features by setting \u003ccode\u003edateRangeRequired\u003c/code\u003e to \u003ccode\u003etrue\u003c/code\u003e in your connector's \u003ccode\u003egetConfig\u003c/code\u003e response.\u003c/p\u003e\n"],["\u003cp\u003eThis enables Looker Studio to include start and end dates with every \u003ccode\u003egetData\u003c/code\u003e request, allowing you to filter data from external sources.\u003c/p\u003e\n"],["\u003cp\u003eThe default date range is the last 28 days excluding today, but users can apply custom ranges, and semantic type detection uses a two-day offset.\u003c/p\u003e\n"]]],[],null,["# Date range control\n\nIf you are working with a data source that requires a date range when fetching\ndata, you can take advantage of the [Looker Studio date range features](https://support.google.com/looker-studio/answer/6291067).\n\nTo enable the date range control feature for your Community Connector, set\n`dateRangeRequired` to `true` in your\n[`getConfig`](/looker-studio/connector/reference#getconfig) response. Then,\nLooker Studio will include a start and end date with every\n[`getData`](/looker-studio/connector/reference#getdata) request made to your\nconnector.\n\n`getData` behavior when `dateRangeRequired` is `true`\n-----------------------------------------------------\n\nWhen `dateRangeRequired` is set to `true` in your `getConfig` response, each\n[`getData`](/looker-studio/connector/reference#getdata) request will contain a\n`dateRange` object with `startDate` and `endDate` parameters. The date\nparameters will be in `YYYY-MM-DD` format. You can use these values in data\nfetch requests to third-party services.\n\n- By default, the date range provided will be the last 28 days, excluding today.\n- If a user applies a date range filter for a report then the date range provided will reflect the user selection.\n- When Looker Studio is attempting to detect [semantic types](/looker-studio/connector/semantics), [`sampleExtraction`](/looker-studio/connector/reference#request_3) is set to `true` in `getData` requests. For these requests, the date provided for the start and the end date is two days earlier than today."]]
