Sorgunun dahili başlangıç tarihi (YYYY-MM-DD biçiminde). endDate tarihinden sonra olamaz. NdaysAgo, yesterday veya today biçimi de kabul edilir. Bu durumda tarih, tesisin raporlama saat dilimine göre belirlenir.
endDate
string
Sorgunun dahili bitiş tarihi (YYYY-MM-DD biçiminde). startDate tarihinden önce olamaz. NdaysAgo, yesterday veya today biçimi de kabul edilir. Bu durumda tarih, tesisin raporlama saat dilimine göre belirlenir.
name
string
Bu tarih aralığına bir ad atar. dateRange boyutu, rapor yanıtında bu adla değerlenir. Ayarlanırsa date_range_ veya RESERVED_ ile başlayamaz. Ayarlanmamışsa tarih aralıkları, istekteki sıfır tabanlı dizinlerine göre adlandırılır: date_range_0, date_range_1 vb.
[[["Anlaması kolay","easyToUnderstand","thumb-up"],["Sorunumu çözdü","solvedMyProblem","thumb-up"],["Diğer","otherUp","thumb-up"]],[["İhtiyacım olan bilgiler yok","missingTheInformationINeed","thumb-down"],["Çok karmaşık / çok fazla adım var","tooComplicatedTooManySteps","thumb-down"],["Güncel değil","outOfDate","thumb-down"],["Çeviri sorunu","translationIssue","thumb-down"],["Örnek veya kod sorunu","samplesCodeIssue","thumb-down"],["Diğer","otherDown","thumb-down"]],["Son güncelleme tarihi: 2025-07-26 UTC."],[[["\u003cp\u003eDefines a contiguous set of days using \u003ccode\u003estartDate\u003c/code\u003e and \u003ccode\u003eendDate\u003c/code\u003e for querying data within a specific timeframe.\u003c/p\u003e\n"],["\u003cp\u003eAllows requests for up to 4 date ranges, providing flexibility in data retrieval.\u003c/p\u003e\n"],["\u003cp\u003eUses a JSON representation with fields for \u003ccode\u003estartDate\u003c/code\u003e, \u003ccode\u003eendDate\u003c/code\u003e, and an optional \u003ccode\u003ename\u003c/code\u003e for the date range.\u003c/p\u003e\n"],["\u003cp\u003eAccepts date formats in \u003ccode\u003eYYYY-MM-DD\u003c/code\u003e or relative formats like \u003ccode\u003eNdaysAgo\u003c/code\u003e, \u003ccode\u003eyesterday\u003c/code\u003e, or \u003ccode\u003etoday\u003c/code\u003e.\u003c/p\u003e\n"],["\u003cp\u003eEnables assigning custom names to date ranges or uses default naming based on their index in the request.\u003c/p\u003e\n"]]],["The core content describes defining date ranges for queries. Each date range is specified by a `startDate` and `endDate` in `YYYY-MM-DD` format or using relative terms like `NdaysAgo`, `yesterday`, or `today`. A `name` can be assigned to each range, which will be used in the response; otherwise, ranges are indexed. Up to four date ranges can be requested. The `startDate` cannot be after `endDate`, and the `name` cannot begin with `date_range_` or `RESERVED_`.\n"],null,["# DateRange\n\n- [JSON representation](#SCHEMA_REPRESENTATION)\n\nA contiguous set of days: `startDate`, `startDate + 1`, ..., `endDate`. Requests are allowed up to 4 date ranges.\n\n| JSON representation |\n|--------------------------------------------------------------------|\n| ``` { \"startDate\": string, \"endDate\": string, \"name\": string } ``` |\n\n| Fields ||\n|---------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|\n| `start``Date` | `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 property's reporting time zone. |\n| `end``Date` | `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 property's reporting time zone. |\n| `name` | `string` Assigns a name to this date range. The dimension `dateRange` is valued to this name in a report response. If set, cannot begin with `date_range_` or `RESERVED_`. If not set, date ranges are named by their zero based index in the request: `date_range_0`, `date_range_1`, etc. |"]]
