LinkedIn Marketing API UTC-only aggregation in reporting

The LinkedIn Marketing API v2 consistently returns and requires timestamps in UTC using ISO 8601 format. While the member profile provides an IANA timezone identifier via the r_liteprofile scope, this context is not propagated to analytics or campaign management endpoints.

This creates day-boundary discrepancies when fetching daily performance metrics for advertisers in non-UTC zones. Because the reporting endpoints aggregate data by UTC midnight-to-midnight windows, a single local campaign day is often split across two UTC days. There is currently no server-side configuration or query parameter to shift these aggregation windows to match the user's local timezone.

Is there a documented method to force the API to respect a specific timezone for date-based aggregation? If not, how should client-side integrations handle the re-alignment of metrics to account for daylight saving transitions that shift UTC boundaries?