On the dates when Daylight Saving changes occur, date parameters in a report definition will return results with an offset as a result of UTC conversion. This only affects the dates of the DST transition, which occur twice a year.
On the date that Daylight Saving Time begins in the Spring you will see your date parameters returning results for two hours later beginning at 2am and lasting until 7am (example: if you filter on transactions completed between 5:00 AM and 6:00 AM, you will receive data for transactions completed between 7:00 AM and 8:00 AM). Starting at 7am, your date parameters will return results for one hour later (example: filtering on transactions completed between 10:00 AM and 11:00 AM will return results for transactions completed during 11:00 AM and 12:00 PM). This is resolved by 12 AM when the next day begins.
Additionally, when filtering on a single date, transactions that occur the following day during the 12:00 AM hour will be pulled into your results. To avoid this, adjust your date parameters to end at 10:59 PM rather than 11:59 PM.
On the date that Daylight Saving Time ends in the Fall you will see your date parameters returning results for an hour earlier beginning at 2am (example: if you filter on transactions completed between 10:00 AM and 11:00 AM, you will receive data for transactions completed between 9:00 AM and 10:00 PM). This is resolved by 12 AM when the next day begins.
Additionally, when filtering on a single date, transactions that occurred in the 11:00 PM hour will not be included in the results, due to this being the 25th hour of the day, which our system does not handle. As a workaround, we recommend manually stretching your date parameters into the following day (example: 11:00 PM to 12:01 AM), which will return the results for the 11:00 PM hour.