7 messages in com.googlegroups.adwords-apiRe: TextAd getAdStats API data does n...| Subject: | Re: TextAd getAdStats API data does not match AdWords UI data |
|---|---|
| From: | Bobby (bobb...@gmail.com) |
| Date: | 05/20/2007 08:36:18 PM |
| List: | com.googlegroups.adwords-api |
Daniel,
Thank you very much for your insightful post! I pushed my dates on the getStats call forward 1 day and now they match the AdWords UI. If you could verify my assumptions on how to code this adjustment, I would very much appreciate it.
Our My Client Center is in Pacific Time (GMT-08:00). The client account for which I was retrieving stats is in Mountain Time (GMT-07:00)
When I asked for date 2007/05/11, because our MCC is 1 hour behind the client, 1 hour was subtracted from midnight on 5/11 and it became 5/10. So the rule would be if the client account's timezone is greater than our MCC's timezone, we should add 1 day to our start/end dates for stats requests. Is this correct?
As far as getting the account timezone, I see that the AccountInfo, timeZoneId returns values such as "America/Los_Angeles ", "America/ Denver", etc. Do you have a list of the values that will be returned for this field so I can convert them into codes for programmatic comparison?
Thanks again! Bobby
On May 16, 3:19 pm, AdWords API Advisor <adwo...@google.com> wrote:
Hi Bobby,
Something else to try is shifting your start and end date forward and back by one day, and seeing if the stats align with what you're seeing in the web interface.
We only store full days worth of stats. As a result, timezone mismatches can result in us returning stats for the previous or next day's results. Simply shifting your start and end date is easier in diagnosing such cases, if only because it dodges around the error you've seen.
If you continue to have difficulty, email me directly with the ad group ID where these text ads exist, along with the date range you're analyzing.
- Daniel AdWords API Team
On May 16, 10:40 am, Bobby <bobb...@gmail.com> wrote:
Chris,
I tried specifying the timezone in the startDay and endDay (eg. 2007-05-11-07:00), but the v10 API returned an error:
<adWordsApiError> <code>70</code> <message>The timezone specified doesn't match the expected timezone, either your Account's local timezone, or PST depending on the call. It is also acceptable to omit the timezone information.</message> <trigger>2007-05-11-07:00</trigger> <faultOrigin>dumpGoogleStats.php:getAdStats()</faultOrigin> <soapParameters> <getAdStats><adGroupId>992942432</adGroupId><adIds>234234234</ adIds><startDay>2007-05-11-07:00</startDay><endDay>2007-05-11-07:00</ endDay></getAdStats> </soapParameters> </adWordsApiError>
Bobby
On May 16, 10:24 am, Bobby <bobb...@gmail.com> wrote:
Chris,
I think you are on to something as the client that is showing this
behavior is in GMT-07:00 while I am in GMT-08:00. The getAdStats API
call parameters are startDay, endDay and don't allow me to specify thetimezone.
I am wondering how I can reconcile this difference. Is
there some way for me to tell the API to return the data in the
account'stimezone?
Thanks so much for your help!
Cheers, Bobby
On May 16, 7:46 am, Chris <goo...@drg1.com> wrote:
I don't know for sure, but is it possible that the API and web interface are running on different time zones? If they are, that would explain why you get different data for the "same" date range.
Log in via the UI and look at your settings... see if there is one for time zone and what that setting is. Then check the API for the same. One of the other guys here handled that for the Yahoo API... may be the same thing here.
- Chris
On May 15, 3:20 pm, Bobby <bobb...@gmail.com> wrote:
I am seeing discrepancies between the AdWords UI and AdWords API when retrieving statistics for text ads. The Clicks, Impressions, and Cost shown in the UI does not match the values returned by the API. I am using the v10 API.
For Text Ads, I have cases where UI shows:
Clicks Impressions Cost 7 1,322 $4.57 2 378 $3.94 1 766 $0.84 1 668 $0.41
API getStatistics for the same ads returns:
Clicks Impressions Cost 9 1,085 $5.20 0 0 $0.00 2 727 $1.34 1 718 $0.51
The stats for campaigns, ad groups, and keywords do not exhibit this problem.
I hope this is a bug that can be fixed. I need confidence in the stats I am retrieving.
Thanks, Bobby