性能数据的有效日期范围? [英] Valid date ranges for performance data?

查看:83
本文介绍了性能数据的有效日期范围?的处理方法,对大家解决问题具有一定的参考价值,需要的朋友们下面随着小编来一起学习吧!

问题描述

您好,

我正在使用从昨天到今天的自定义日期范围进行的DownloadCampaignsByAccountIdsRequest。如果我在4点执行该请求,我会收到错误  3215
"
性能统计的自定义日期范围应设置为有效的开始和结束日期。 "。
如果我在当天晚些时候(例如12点)做同样的请求,报告会成功。

I am doing a DownloadCampaignsByAccountIdsRequest with a custom date range from yesterday to today. If I execute that request at 4 o'clock, I get error 3215 "The custom date range for performance statistics should be set to a valid start and end date.". If I am doing the same request later that day (e.g. 12 o'clock) the report succeeds.

我设置了帐户和广告系列的时区to  AmsterdamBerlinBernRomeStockholmVienna。上面提到的时间是
时区。那么为什么日期范围被拒绝为无效?

I set the time zones of the accounts and campaigns to AmsterdamBerlinBernRomeStockholmVienna. The above mentioned times are in that timezone. So why is the date range rejected as invalid?

Markus

推荐答案

马库斯嗨。我确认我们的团队在确定日期范围时该服务使用太平洋时区。当您在太平洋之前的时区中运行报表时,请指定一天,例如12月9日(在太平洋时区尚未生效),
服务会引发您观察到的错误。我已经要求我们的团队重新评估是否应该使用Pacific或UTC,因为我们使用"LastSyncTimeInUTC"。用于下载批量实体例如广告系列数据至少现在,请使用该服务使用太平洋时间作为性能统计日期范围的

Hi Markus. I confirmed with our team that the service uses Pacific time zone when determining the date range. When you run a report in a time zone that is ahead of Pacific, and specify a day e.g. December 9th (which is not yet valid in Pacific time zone), the service throws the error you observed. I have asked our team to reevaluate whether Pacific or UTC should be used instead, since we use "LastSyncTimeInUTC" for downloading bulk entities e.g. Campaign data. At least for now though, please take in account that the service uses Pacific time for performance stats date range.

我希望这有帮助!


这篇关于性能数据的有效日期范围?的文章就介绍到这了,希望我们推荐的答案对大家有所帮助,也希望大家多多支持IT屋!

查看全文
登录 关闭
扫码关注1秒登录
发送“验证码”获取 | 15天全站免登陆