from:"Joseph Collins"

Re: AdWords Express Data Discrepancies

2017-11-14 Thread Joseph Collins

Josh,

Any update to this issue? I read the blog post about the AWX campaign 
migration, but there is no mention of when this migration begins (perhaps 
this issue is a symptom of an ongoing migration?) or when it is expected to 
be completed. Do we need a specific version of the AdWords API to see these 
additional campaigns in the campaign performance report? There is also no 
mention of a migration cutover delay to help explain the missing AWX 
performance as reported by our users.


On Monday, November 6, 2017 at 2:00:08 PM UTC-5, Josh Radcliff (AdWords API 
Team) wrote:
>
> Hi,
>
> We're aware of this issue and I'm actively looking into it. I'll provide 
> an update as soon as I have more information.
>
> Thanks,
> Josh, AdWords API Team
>
> On Sunday, November 5, 2017 at 1:36:16 PM UTC-5, Joseph Collins wrote:
>>
>> A user of our system is seeing a significant disagreement between our 
>> data and the AdWords Express interface. Below are user-provided screenshots 
>> of the AdWords Express CID in question, its dashboard and our API request / 
>> response.
>>
>>
>> The mismatch between the 'Hayworth Equipment AWX' account description and 
>> the 'Hayworth Equipment Sales' account label on the dashboard suggests that 
>> this issue is due to user error (navigating to the wrong Express 
>> dashboard), but the user is confident they are not making a mistake and 
>> they report that these issues affect several of their Express accounts.
>>
>>
>> For this specific account, you will notice that the API claims activity 
>> stopped on October 6th, yet the dashboard shows ongoing activity. On the 
>> days where both the dashboard and API show activity, the numbers do not 
>> come close to agreeing.
>>
>>
>> Any help in explaining or resolving this discrepancy would be greatly 
>> appreciated.
>>
>>
>>
>> 
>>
>>
>> *User-Provided Evidence*
>>
>>
>>
>> <https://lh3.googleusercontent.com/-lEfynuUWwxQ/Wf9V-2k-i6I/BlU/_Zs3wc2U6vEq4l407n_DTxWk1Aq8fTEzQCLcBGAs/s1600/CID.png>
>>
>>
>> <https://lh3.googleusercontent.com/-9OIS42wKucA/Wf9WA0BamEI/BlY/M_QAFWJdfaQ4FOrS9kD9Oj1YOOuL8p5lwCLcBGAs/s1600/UI.png>
>>
>>
>>
>> 
>>
>> *Request*
>>
>> Headers
>> (
>> [0] => Authorization: Bearer X
>> [1] => developerToken: X
>> [2] => clientCustomerId: 5571930852
>> [3] => includeZeroImpressions: true
>> )
>> 
>> 
>> Date
>> Impressions
>> Clicks
>> Ctr
>> Cost
>> ConversionValue
>> AverageCpc
>> Conversions
>> ConversionRate
>> CostPerConversion
>> ValuePerConversion
>> AveragePosition
>> 
>> 20170906
>> 20171104
>> 
>> 
>> Report
>> ACCOUNT_PERFORMANCE_REPORT
>> CUSTOM_DATE
>> GZIPPED_CSV
>> 
>>
>>
>> 
>>
>> *Response*
>>
>> "Report (Sep 6, 2017-Nov 4, 2017)"
>> Day,Impressions,Clicks,CTR,Cost,Total conv. value,Avg. 
>> CPC,Conversions,Conv. rate,Cost / conv.,Value / conv.,Avg. position
>> 2017-10-01,25518,37,0.14%,3182,0.00,86,0.00,0.00%,0,0.00,1.9
>>
>> 2017-10-04,16918,37,0.22%,3336,0.00,901622,2.00,5.41%,1668,0.00,2.2
>> 2017-10-02,15028,37,0.25%,3424,0.00,925405,0.00,0.00%,0,0.00,2.0
>> 2017-10-06,0,0,0.00%,0,0.00,0,0.00,0.00%,0,0.00,0.0
>> 2017-10-13,0,0,0.00%,0,0.00,0,0.00,0.00%,0,0.00,0.0
>> 2017-09-17,0,0,0.00%,0,0.00,0,0.00,0.00%,0,0.00,0.0
>> 2017-11-03,0,0,0.00%,0,0.00,0,0.00,0.00%,0,0.00,0.0
>> 2017-11-02,0,0,0.00%,0,0.00,0,0.00,0.00%,0,0.00,0.0
>> 2017-10-26,0,0,0.00%,0,0.00,0,0.00,0.00%,0,0.00,0.0
>> 2017-10-03,20683,37,0.18%,3334,0.00,901081,0.00,0.00%,0,0.00,2.1
>> 2017-09-07,0,0,0.00%,0,0.00,0,0.00,0.00%,0,0.00,0.0
>> 2017-09-29,23472,34,0.14%,3607,0.00,1060882,0.00,0.00%,0,0.00,1.9
>> 2017-10-15,0,0,0.00%,0,0.00,0,0.00,0.00%,0,0.00,0.0
>> 2017-09-11,0,0,0.00%,0,0.00,0,0.00,0.00%,0,0.00,0.0
>> 2017-10-08,0,0,0.00%,0,0.00,0,0.00,0.00%,0,0.00,0.0
>> 2017-09-22,22885,38,0.17%,3438,0.00,904737,0.00,0.00%,0,0.00,2.1
>> 2017-09-08,0,0,0.00%,0,0.00,0,0.00,0.00%,0,0.00,0.0
>&g

AdWords Express Data Discrepancies

2017-11-05 Thread Joseph Collins



A user of our system is seeing a significant disagreement between our data 
and the AdWords Express interface. Below are user-provided screenshots of 
the AdWords Express CID in question, its dashboard and our API request / 
response.


The mismatch between the 'Hayworth Equipment AWX' account description and 
the 'Hayworth Equipment Sales' account label on the dashboard suggests that 
this issue is due to user error (navigating to the wrong Express 
dashboard), but the user is confident they are not making a mistake and 
they report that these issues affect several of their Express accounts.


For this specific account, you will notice that the API claims activity 
stopped on October 6th, yet the dashboard shows ongoing activity. On the 
days where both the dashboard and API show activity, the numbers do not 
come close to agreeing.


Any help in explaining or resolving this discrepancy would be greatly 
appreciated.





*User-Provided Evidence*









*Request*

Headers
(
[0] => Authorization: Bearer X
[1] => developerToken: X
[2] => clientCustomerId: 5571930852
[3] => includeZeroImpressions: true
)


Date
Impressions
Clicks
Ctr
Cost
ConversionValue
AverageCpc
Conversions
ConversionRate
CostPerConversion
ValuePerConversion
AveragePosition

20170906
20171104


Report
ACCOUNT_PERFORMANCE_REPORT
CUSTOM_DATE
GZIPPED_CSV




*Response*

"Report (Sep 6, 2017-Nov 4, 2017)"
Day,Impressions,Clicks,CTR,Cost,Total conv. value,Avg. 
CPC,Conversions,Conv. rate,Cost / conv.,Value / conv.,Avg. position
2017-10-01,25518,37,0.14%,3182,0.00,86,0.00,0.00%,0,0.00,1.9
2017-10-04,16918,37,0.22%,3336,0.00,901622,2.00,5.41%,1668,0.00,2.2
2017-10-02,15028,37,0.25%,3424,0.00,925405,0.00,0.00%,0,0.00,2.0
2017-10-06,0,0,0.00%,0,0.00,0,0.00,0.00%,0,0.00,0.0
2017-10-13,0,0,0.00%,0,0.00,0,0.00,0.00%,0,0.00,0.0
2017-09-17,0,0,0.00%,0,0.00,0,0.00,0.00%,0,0.00,0.0
2017-11-03,0,0,0.00%,0,0.00,0,0.00,0.00%,0,0.00,0.0
2017-11-02,0,0,0.00%,0,0.00,0,0.00,0.00%,0,0.00,0.0
2017-10-26,0,0,0.00%,0,0.00,0,0.00,0.00%,0,0.00,0.0
2017-10-03,20683,37,0.18%,3334,0.00,901081,0.00,0.00%,0,0.00,2.1
2017-09-07,0,0,0.00%,0,0.00,0,0.00,0.00%,0,0.00,0.0
2017-09-29,23472,34,0.14%,3607,0.00,1060882,0.00,0.00%,0,0.00,1.9
2017-10-15,0,0,0.00%,0,0.00,0,0.00,0.00%,0,0.00,0.0
2017-09-11,0,0,0.00%,0,0.00,0,0.00,0.00%,0,0.00,0.0
2017-10-08,0,0,0.00%,0,0.00,0,0.00,0.00%,0,0.00,0.0
2017-09-22,22885,38,0.17%,3438,0.00,904737,0.00,0.00%,0,0.00,2.1
2017-09-08,0,0,0.00%,0,0.00,0,0.00,0.00%,0,0.00,0.0
2017-09-14,0,0,0.00%,0,0.00,0,0.00,0.00%,0,0.00,0.0
2017-09-06,0,0,0.00%,0,0.00,0,0.00,0.00%,0,0.00,0.0
2017-10-05,436,1,0.23%,85,0.00,85,0.00,0.00%,0,0.00,2.2
2017-09-27,25856,28,0.11%,2321,0.00,828929,0.00,0.00%,0,0.00,1.8
2017-10-27,0,0,0.00%,0,0.00,0,0.00,0.00%,0,0.00,0.0
2017-10-30,0,0,0.00%,0,0.00,0,0.00,0.00%,0,0.00,0.0
2017-10-25,0,0,0.00%,0,0.00,0,0.00,0.00%,0,0.00,0.0
2017-10-14,0,0,0.00%,0,0.00,0,0.00,0.00%,0,0.00,0.0
2017-09-15,0,0,0.00%,0,0.00,0,0.00,0.00%,0,0.00,0.0
2017-10-09,0,0,0.00%,0,0.00,0,0.00,0.00%,0,0.00,0.0
2017-09-13,0,0,0.00%,0,0.00,0,0.00,0.00%,0,0.00,0.0
2017-10-12,0,0,0.00%,0,0.00,0,0.00,0.00%,0,0.00,0.0
2017-10-20,0,0,0.00%,0,0.00,0,0.00,0.00%,0,0.00,0.0
2017-09-24,25445,40,0.16%,3339,0.00,834750,0.00,0.00%,0,0.00,2.1
2017-09-23,19092,23,0.12%,3387,0.00,1472609,0.00,0.00%,0,0.00,1.7
2017-09-26,24668,39,0.16%,3186,0.00,816923,0.00,0.00%,0,0.00,2.0
2017-10-10,0,0,0.00%,0,0.00,0,0.00,0.00%,0,0.00,0.0
2017-10-11,0,0,0.00%,0,0.00,0,0.00,0.00%,0,0.00,0.0
2017-10-24,0,0,0.00%,0,0.00,0,0.00,0.00%,0,0.00,0.0
2017-10-22,0,0,0.00%,0,0.00,0,0.00,0.00%,0,0.00,0.0
2017-11-01,0,0,0.00%,0,0.00,0,0.00,0.00%,0,0.00,0.0
2017-10-23,0,0,0.00%,0,0.00,0,0.00,0.00%,0,0.00,0.0
2017-09-10,0,0,0.00%,0,0.00,0,0.00,0.00%,0,0.00,0.0
2017-10-28,0,0,0.00%,0,0.00,0,0.00,0.00%,0,0.00,0.0
2017-09-12,0,0,0.00%,0,0.00,0,0.00,0.00%,0,0.00,0.0
2017-09-09,0,0,0.00%,0,0.00,0,0.00,0.00%,0,0.00,0.0
2017-09-21,23395,20,0.09%,3376,0.00,1688000,0.00,0.00%,0,0.00,1.3
2017-09-30,21889,31,0.14%,3158,0.00,1018710,0.00,0.00%,0,0.00,1.8
2017-09-25,22151,36,0.16%,2940,0.00,816667,0.00,0.00%,0,0.00,2.2
2017-10-19,0,0,0.00%,0,0.00,0,0.00,0.00%,0,0.00,0.0
2017-10-31,0,0,0.00%,0,0.00,0,0.00,0.00%,0,0.00,0.0

Re: SOAP-ERROR: Parsing WSDL: Couldn't load from 'https://adwords.google.com/api/adwords/cm/v201309/CampaignService?wsdl' : failed to load external entity

2014-03-10 Thread Joseph Collins

I can only reproduce this issue on Windows Server 2012; all requests to
173.194.115.0/24http://www.google.com/url?q=http%3A%2F%2F173.194.115.0%2F24sa=Dsntz=1usg=AFQjCNHP6tysKvLsSEisPB-qo2K2J0cpcgin
Linux work fine.

For those affected by these errors, I have had success using a static host
address for adwords.google.com (http://en.wikipedia.org/wiki/Hosts_(file))
that is not contained in
173.194.115.0/24http://www.google.com/url?q=http%3A%2F%2F173.194.115.0%2F24sa=Dsntz=1usg=AFQjCNHP6tysKvLsSEisPB-qo2K2J0cpcg(keeping
pinging adwords.google.com until you receive one).

On Friday, March 7, 2014 1:18:10 PM UTC-5, Joseph Collins wrote:

Ray,

I have only seen this issue appear when Google's load balancer directs
traffic to
173.194.115.0/24http://www.google.com/url?q=http%3A%2F%2F173.194.115.0%2F24sa=Dsntz=1usg=AFQjCNHP6tysKvLsSEisPB-qo2K2J0cpcg.

This issue affects adwords.google.com, google.com, gmail.com, youtube.com,
etc. with both HTTP (cURL feedback: *Recv failure: Connection was reset*)
and HTTPS (cURL feedback: *Unknown SSL protocol error in connection*)
requests via cURL, Telnet and Google Chrome.

The issue has been consistently reproduced in every big network (Comcast,
Limestone Networks, Amazon AWS and several unknowns via VPN) accessible to
me.

The failure rate on 173.194.115.0/24 was roughly 70% over ~200 requests.

On Wednesday, March 5, 2014 5:09:40 PM UTC-5, Ray Tsang (AdWords API Team)
wrote:

Mathis,

Following up on your private thread -

Machine A: even though curl works, it appears you may have additional
environmental issues that's behind my expertise. Please make sure both
machines are setup with the same versions and configurations of PHP, etc.

Machine B: did you use a developer token from a production MCC? Please
send me the MCC CID.

Thanks,

On Tuesday, March 4, 2014 2:30:20 PM UTC-5, Ray Tsang (AdWords API Team)
wrote:

Mathis,

This is great:

Machine A: there is a bigger issue here w/ the machine setup if curl
doesn't work at all. It could be caused by many many factors that's
outside of my expertise.

Machine B: regarding the date function error, please make sure you have
set a default
timezonehttp://us3.php.net/manual/en/datetime.configuration.php#ini.date.timezone
.

For INCOMPLETE_SIGNUP_ERROR, please send me your MCC's CID and the AW
CID that you are accessing in private (respond to author).

Thanks!

--
Ray Tsang (AdWords API Advisor)

On Tuesday, March 4, 2014 9:53:03 AM UTC-5, Mathis Lübbers wrote:

Hey Ray,
thank your for your response!
I think, I have you to tell the whole problem again, because I've made
a mistake in the discription of the problem, sorry therefore!

We have installed the API with it's configurations on two different
machines (A,B) using these steps:

download the current php library
create MCC production account (developer token in auth.ini)
create MCC test account (creat client -- client costumer ID in
auth.ini)
create Project at Google Developers Console (client ID , clientSecret
in auth.ini)
get RefreshToken -- insert in auth.ini
uncomment extension=php_openssl.dll
extension=php_curl.dll
extension=php_soap.dllin php.ini (on
Machine A in php.ini-developement and php.ini-production, too)

tried GetCampaigns on two different machines and got two different
errors.

Machine A :

An error has occurred: SOAP-ERROR: Parsing WSDL: Couldn't load from '
https://adw
ords.google.com/api/adwords//api/adwords/cm/v201309/CampaignService?wsdl'
: fail
ed to load external entity
https://adwords.google.com/api/adwords//api/adwords/
cm/v201309/CampaignService?wsdl

Machine B:

Warning: date(): It is not safe to rely on the system's timezone
settings. You are *required* to use the date.timezone setting or the
date_default_timezone_set() function. In case you used any of those
methods
and you are still getting this warning, you most likely misspelled the
timezone identifier. We selected the timezone 'UTC' for now, but please
set
date.timezone to select your timezone. in
/Applications/XAMPP/xamppfiles/htdocs/adwordsapi/src/Google/Api/Ads/Common/Util/Logger.php

on line 236

on line 236
An error has occurred: [QuotaCheckError.INCOMPLETE_SIGNUP @ ;
trigger:'null']

In both cases we got no soap_xml.log files in the Basic_Operations
folder.

On machine

Re: AdWords Express Data Discrepancies

AdWords Express Data Discrepancies

Re: SOAP-ERROR: Parsing WSDL: Couldn't load from 'https://adwords.google.com/api/adwords/cm/v201309/CampaignService?wsdl' : failed to load external entity

3 matches

Site Navigation

Mail list logo

Footer information