Re: After October 2 - Can not use the AdWords API any more

2017-10-01 Thread Nadav De Bruin
Thanks,
Downloaded the source project from GitHub and build it with v4.5.
Hope that will work for for a while until we'll upgrade framework to 4.5.2

On Thursday, September 28, 2017 at 1:50:53 PM UTC+3, Zweitze wrote:
>
> A few years ago I was in a similar situation, when Google moved the 
> framework from 2.0 to 4.0 - but my software was closely tied to SharePoint 
> v3 (2007) which is .NET 2.0.
>
> To stay on .NET 4.0 you have a few options:
>
>- Stop using the library, and add webservice references in Visual 
>Studio directly. VS will study the webservices itself and come up with 
>something. So you'll miss all the library stuff like ReportUtilities but 
> at 
>least you got something workable.
>- Build your own version of the library.
>
> I did the second. I downloaded the sources of the library from the OLD 
> framework. Then I downloaded the sources of the next version, on the newer 
> framework. I compared all sources and made up my own library, which 
> essentially was the old library plus handpicked improvements of the new 
> library.
> After that, I downloaded the sources of the oldest version of the library 
> that was supporting a newer AdWords API. I compared those sources with the 
> sources of what I call "next version" above, and applied the changes to my 
> library. Then I had a library supporting a newer version.
>
> This method only works when the library developers don't apply very big 
> changes. It bought me 18 months (!) and then we were finally ready to move 
> to the newer .NET version. You probably have less time because the library 
> developers are trying to have the library support .NET Core and other 
> things, which implies big changes.
>
> Oh, one more thing: On 2 October v201609 will not completely disappear. It 
> will keep working, but every now and then you get a sunset error. If you 
> retry you may get the right answer. This works for another few days, maybe 
> weeks. Disclaimer: this was the behavior about 2-3 years ago, I don't know 
> if it's still the case and I can't predict how Google will handle this on 
> October 2 and onwards.
>
>
> On Thursday, September 28, 2017 at 10:13:52 AM UTC+2, Nadav De Bruin wrote:
>>
>> As stated here 
>> <http://googleadsdeveloper.blogspot.co.il/2017/08/adwords-api-v201609-sunset-reminder.html>
>>  "*on October 2, 2017. After this date, all v201609 API requests will 
>> begin to fail.*"
>> The recommendation is to migrate to newer version.
>>
>> We use:
>> Google.AdWords v18.34
>> Google.Ads.Common v3.18
>> I've tried to migrate but get error that the .Net 4.5 Framework is not 
>> supported by the new version.
>>
>> We can not upgrade the framework for this project because other 
>> dependencies and it is very sensitive project in the production 
>> environment. 
>> So it seems that we are going to stop using the AdWords API.
>>
>> If someone can help here we'll be happy. 
>>
>
>

-- 
-- 
=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~
Also find us on our blog and Google+:
https://googleadsdeveloper.blogspot.com/
https://plus.google.com/+GoogleAdsDevelopers/posts
=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~

You received this message because you are subscribed to the Google
Groups "AdWords API Forum" group.
To post to this group, send email to adwords-api@googlegroups.com
To unsubscribe from this group, send email to
adwords-api+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/adwords-api?hl=en
--- 
You received this message because you are subscribed to the Google Groups 
"AdWords API Forum" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to adwords-api+unsubscr...@googlegroups.com.
Visit this group at https://groups.google.com/group/adwords-api.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/adwords-api/ee6162f9-4728-46ed-abdd-0158f1dc365c%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


Re: After October 2 - Can not use the AdWords API any more

2017-09-28 Thread Nadav De Bruin
This is a big scheduler project that hosts many integration APIs 
implementations for many systems not just to AdWords.
No one will take the risk here to upgrade to v4.5.2 

On Thursday, September 28, 2017 at 12:05:33 PM UTC+3, Peter Oliquino wrote:
>
> Hi Nadav,
>
> Could you tell me more about the dependencies that you are considering 
> that might be affected when you migrate to the latest version? Our release 
> notes 
> 
>  and migration guide 
>  
> should 
> provide you with the information you need regarding the changes that have 
> been applied in the latest version so you can also make the necessary 
> adjustments in your code if applicable.
>
> As for the the configuration of your .NET client library, you may get in 
> touch with the library owners via this link 
>  as they are 
> more equipped to assist you with this concern.
>
> Thanks and regards,
> Peter
> AdWords API Team
>

-- 
-- 
=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~
Also find us on our blog and Google+:
https://googleadsdeveloper.blogspot.com/
https://plus.google.com/+GoogleAdsDevelopers/posts
=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~

You received this message because you are subscribed to the Google
Groups "AdWords API Forum" group.
To post to this group, send email to adwords-api@googlegroups.com
To unsubscribe from this group, send email to
adwords-api+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/adwords-api?hl=en
--- 
You received this message because you are subscribed to the Google Groups 
"AdWords API Forum" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to adwords-api+unsubscr...@googlegroups.com.
Visit this group at https://groups.google.com/group/adwords-api.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/adwords-api/6e7d4ae5-96b5-4a0d-bbfc-a8c6a59b107b%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


After October 2 - Can not use the AdWords API any more

2017-09-28 Thread Nadav De Bruin
As stated here 

 "*on October 2, 2017. After this date, all v201609 API requests will begin 
to fail.*"
The recommendation is to migrate to newer version.

We use:
Google.AdWords v18.34
Google.Ads.Common v3.18
I've tried to migrate but get error that the .Net 4.5 Framework is not 
supported by the new version.

We can not upgrade the framework for this project because other 
dependencies and it is very sensitive project in the production 
environment. 
So it seems that we are going to stop using the AdWords API.

If someone can help here we'll be happy. 

-- 
-- 
=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~
Also find us on our blog and Google+:
https://googleadsdeveloper.blogspot.com/
https://plus.google.com/+GoogleAdsDevelopers/posts
=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~

You received this message because you are subscribed to the Google
Groups "AdWords API Forum" group.
To post to this group, send email to adwords-api@googlegroups.com
To unsubscribe from this group, send email to
adwords-api+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/adwords-api?hl=en
--- 
You received this message because you are subscribed to the Google Groups 
"AdWords API Forum" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to adwords-api+unsubscr...@googlegroups.com.
Visit this group at https://groups.google.com/group/adwords-api.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/adwords-api/605c6ce7-285d-409a-b9c0-cbda4dbb60fb%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


Large Miss-Match Between Offline Conversion Feeds Send and What is Reported

2017-08-02 Thread Nadav De Bruin
For a month from now we send once a day all the new conversions to AdWords 
using the API.
Each after OfflineConversionFeedOperation (Operator.ADD) is sent with not 
returning error we log all the feed attributes to our DB.
So we can track for each conversion date how many feeds and the total value 
sent to AdWords.
Unfortunately, in a the AdWords reports for a conversion date the results 
do not match at all,
some days there is close to 80% gap in value and about 30% in the total 
reported.

Is there any report we can see which OfflineConversionFeedOperation where 
accepted by AdWords for a given date?

Thanks,
Nadav

-- 
-- 
=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~
Also find us on our blog and Google+:
https://googleadsdeveloper.blogspot.com/
https://plus.google.com/+GoogleAdsDevelopers/posts
=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~

You received this message because you are subscribed to the Google
Groups "AdWords API Forum" group.
To post to this group, send email to adwords-api@googlegroups.com
To unsubscribe from this group, send email to
adwords-api+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/adwords-api?hl=en
--- 
You received this message because you are subscribed to the Google Groups 
"AdWords API Forum" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to adwords-api+unsubscr...@googlegroups.com.
Visit this group at https://groups.google.com/group/adwords-api.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/adwords-api/d4090803-f094-4ba6-8de5-af37ab06b7fe%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


Re: Lowercase GCLID Requests Problem

2017-08-02 Thread Nadav De Bruin
Thanks Josh,
The 2 hyphens,  as you wrote, are cause the gclid to change in our site.
We'll search our  proxies, load balancers, any rewrite engines etc.. to fix 
it.

On Monday, July 31, 2017 at 7:44:09 PM UTC+3, Josh Radcliff (AdWords API 
Team) wrote:
>
> Hi Nadav,
>
> Thanks for sending that over. I ran a *CLICK_PERFORMANCE_REPORT* for that 
> customer and noticed that it contained a row that matched the GCLID if I: 
> a) ignore case, and b) add an additional hyphen (-).
>
> GCLID you sent over:
>
> cjwkeajwhrzlbrc35-f9ssh0fasjad5obj1kylnrwqus0vztbm1qkc7lapsc6cxnsvraz7__9a5wrocaqdw_wcb
>  
>
> GCLID in the report for July 19 2017:
> CjwKEAjwhrzLBRC35-*-*
> F9sSH0FASJAD5obJ1KYLnRWQuS0VzTBM1QKc7LaPsc6CxNsVRaZ7__9A5wRoCaqDw_wcB 
>
> Are the requests going through a proxy or load balancer on your side that 
> is changing the case of parameters and removing double hyphens?
>
> Thanks,
> Josh, AdWords API Team
>
> On Monday, July 31, 2017 at 10:06:47 AM UTC-4, Nadav De Bruin wrote:
>>
>> *Click date:* 19-07-2017
>> *Client Customer ID:* 272-772-9533
>>
>> On Monday, July 31, 2017 at 3:48:20 PM UTC+3, Josh Radcliff (AdWords API 
>> Team) wrote:
>>>
>>> Hi Nadav,
>>>
>>> Could you send me the click date and client customer ID for the GCLID 
>>> below?
>>>
>>> Thanks,
>>> Josh, AdWords API Team
>>>
>>> On Monday, July 31, 2017 at 3:14:03 AM UTC-4, Nadav De Bruin wrote:
>>>>
>>>> Some of the AdWords redirections we get on our site comes with 
>>>> lower-case gclid value.
>>>>
>>>> When we report offline to AdWords by AdWords API with this lower-case 
>>>> gclid we get an error back saying: 
>>>> “OfflineConversionError.UNPARSEABLE_GCLID”.
>>>>
>>>> From the start of the implementation 2 month ago, we get about 1-5 
>>>> lower-cased gclids requests each day. All the other requests are OK.
>>>>
>>>>
>>>> All adds are defined to link directly to our site – www.daka90.co.il 
>>>> so there is not a possibility that the lower-case behavior is caused by 
>>>> some other redirection than Google.
>>>>
>>>> And there are any changes in URL rewriting engine in their website.
>>>>
>>>>
>>>> View this one of the lower-cased  gclid request info we get in our 
>>>> ASP.NET global.asax file using 
>>>> System.Web.HttpApplication.Request.ToRaw(),
>>>>
>>>> The Referer property marked with yellow points that the request came 
>>>> directly from Google.
>>>>
>>>>  
>>>>
>>>> GET http://www.daka90.co.il/packages?
>>>> gclid=cjwkeajwhrzlbrc35-f9ssh0fasjad5obj1kylnrwqus0vztbm1qkc7lapsc6cxnsvraz7__9a5wrocaqdw_wcb
>>>>  
>>>> HTTP/1.1
>>>>
>>>> Connection: keep-alive
>>>>
>>>> Accept: 
>>>> text/html,application/xhtml+xml,application/xml;q=0.9,image/webp,image/apng,*/*;q=0.8
>>>>
>>>> Accept-Language: he-IL,he;q=0.8,en-US;q=0.6,en;q=0.4
>>>>
>>>> Host: www.daka90.co.il
>>>>
>>>> Referer: https://www.google.co.il/
>>>>
>>>> User-Agent: Mozilla/5.0 (Windows NT 6.1; Win64; x64) AppleWebKit/537.36 
>>>> (KHTML, like Gecko) Chrome/59.0.3071.115 Safari/537.36
>>>>
>>>> X-Forwarded-For: 89.237.74.37
>>>>
>>>> Upgrade-Insecure-Requests: 1
>>>>
>>>> X-Chrome-UMA-Enabled: 1
>>>>
>>>> X-Client-Data: CJW2yQEIpLbJAQjDtskBCPucygEIqZ3KAQi1nsoB
>>>>
>>>>
>>>> When we look for those lower-cased gclids in the CLICK_PERFORMANCE_REPORT 
>>>> we can not find then there.
>>>>
>>>> We can find all the other not lower-cased gclids there.
>>>>
>>>>
>>>> Please help,
>>>>
>>>> Nadav
>>>>
>>>

-- 
-- 
=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~
Also find us on our blog and Google+:
https://googleadsdeveloper.blogspot.com/
https://plus.google.com/+GoogleAdsDevelopers/posts
=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~

You received this message because you are subscribed to the Google
Groups "AdWords API Forum" group.
To post to this group, send email to adwords-api@googlegroups.com
To unsubscribe from this group, send email to
adwords-api+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/adwords-api?hl=en
--- 
You received this message because you are subscribed to the Google Groups 
"AdWords API Forum" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to adwords-api+unsubscr...@googlegroups.com.
Visit this group at https://groups.google.com/group/adwords-api.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/adwords-api/24ddc415-da9b-4cc8-bbaa-414a4dfd4a6e%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


Re: Lowercase GCLID Requests Problem

2017-07-31 Thread Nadav De Bruin
*Click date:* 19-07-2017
*Client Customer ID:* 272-772-9533

On Monday, July 31, 2017 at 3:48:20 PM UTC+3, Josh Radcliff (AdWords API 
Team) wrote:
>
> Hi Nadav,
>
> Could you send me the click date and client customer ID for the GCLID 
> below?
>
> Thanks,
> Josh, AdWords API Team
>
> On Monday, July 31, 2017 at 3:14:03 AM UTC-4, Nadav De Bruin wrote:
>>
>> Some of the AdWords redirections we get on our site comes with lower-case 
>> gclid value.
>>
>> When we report offline to AdWords by AdWords API with this lower-case 
>> gclid we get an error back saying: 
>> “OfflineConversionError.UNPARSEABLE_GCLID”.
>>
>> From the start of the implementation 2 month ago, we get about 1-5 
>> lower-cased gclids requests each day. All the other requests are OK.
>>
>>
>> All adds are defined to link directly to our site – www.daka90.co.il so 
>> there is not a possibility that the lower-case behavior is caused by some 
>> other redirection than Google.
>>
>> And there are any changes in URL rewriting engine in their website.
>>
>>
>> View this one of the lower-cased  gclid request info we get in our 
>> ASP.NET global.asax file using 
>> System.Web.HttpApplication.Request.ToRaw(),
>>
>> The Referer property marked with yellow points that the request came 
>> directly from Google.
>>
>>  
>>
>> GET http://www.daka90.co.il/packages?
>> gclid=cjwkeajwhrzlbrc35-f9ssh0fasjad5obj1kylnrwqus0vztbm1qkc7lapsc6cxnsvraz7__9a5wrocaqdw_wcb
>>  
>> HTTP/1.1
>>
>> Connection: keep-alive
>>
>> Accept: 
>> text/html,application/xhtml+xml,application/xml;q=0.9,image/webp,image/apng,*/*;q=0.8
>>
>> Accept-Language: he-IL,he;q=0.8,en-US;q=0.6,en;q=0.4
>>
>> Host: www.daka90.co.il
>>
>> Referer: https://www.google.co.il/
>>
>> User-Agent: Mozilla/5.0 (Windows NT 6.1; Win64; x64) AppleWebKit/537.36 
>> (KHTML, like Gecko) Chrome/59.0.3071.115 Safari/537.36
>>
>> X-Forwarded-For: 89.237.74.37
>>
>> Upgrade-Insecure-Requests: 1
>>
>> X-Chrome-UMA-Enabled: 1
>>
>> X-Client-Data: CJW2yQEIpLbJAQjDtskBCPucygEIqZ3KAQi1nsoB
>>
>>
>> When we look for those lower-cased gclids in the CLICK_PERFORMANCE_REPORT 
>> we can not find then there.
>>
>> We can find all the other not lower-cased gclids there.
>>
>>
>> Please help,
>>
>> Nadav
>>
>

-- 
-- 
=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~
Also find us on our blog and Google+:
https://googleadsdeveloper.blogspot.com/
https://plus.google.com/+GoogleAdsDevelopers/posts
=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~

You received this message because you are subscribed to the Google
Groups "AdWords API Forum" group.
To post to this group, send email to adwords-api@googlegroups.com
To unsubscribe from this group, send email to
adwords-api+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/adwords-api?hl=en
--- 
You received this message because you are subscribed to the Google Groups 
"AdWords API Forum" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to adwords-api+unsubscr...@googlegroups.com.
Visit this group at https://groups.google.com/group/adwords-api.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/adwords-api/49c39563-3e2b-41fe-98bc-3dcab5606092%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


Lowercase GCLID Requests Problem

2017-07-31 Thread Nadav De Bruin


Some of the AdWords redirections we get on our site comes with lower-case 
gclid value.

When we report offline to AdWords by AdWords API with this lower-case gclid 
we get an error back saying: “OfflineConversionError.UNPARSEABLE_GCLID”.

>From the start of the implementation 2 month ago, we get about 1-5 
lower-cased gclids requests each day. All the other requests are OK.


All adds are defined to link directly to our site – www.daka90.co.il so 
there is not a possibility that the lower-case behavior is caused by some 
other redirection than Google.

And there are any changes in URL rewriting engine in their website.


View this one of the lower-cased  gclid request info we get in our ASP.NET 
global.asax file using System.Web.HttpApplication.Request.ToRaw(),

The Referer property marked with yellow points that the request came 
directly from Google.

 

GET http://www.daka90.co.il/packages?
gclid=cjwkeajwhrzlbrc35-f9ssh0fasjad5obj1kylnrwqus0vztbm1qkc7lapsc6cxnsvraz7__9a5wrocaqdw_wcb
 
HTTP/1.1

Connection: keep-alive

Accept: 
text/html,application/xhtml+xml,application/xml;q=0.9,image/webp,image/apng,*/*;q=0.8

Accept-Language: he-IL,he;q=0.8,en-US;q=0.6,en;q=0.4

Host: www.daka90.co.il

Referer: https://www.google.co.il/

User-Agent: Mozilla/5.0 (Windows NT 6.1; Win64; x64) AppleWebKit/537.36 
(KHTML, like Gecko) Chrome/59.0.3071.115 Safari/537.36

X-Forwarded-For: 89.237.74.37

Upgrade-Insecure-Requests: 1

X-Chrome-UMA-Enabled: 1

X-Client-Data: CJW2yQEIpLbJAQjDtskBCPucygEIqZ3KAQi1nsoB


When we look for those lower-cased gclids in the CLICK_PERFORMANCE_REPORT 
we can not find then there.

We can find all the other not lower-cased gclids there.


Please help,

Nadav

-- 
-- 
=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~
Also find us on our blog and Google+:
https://googleadsdeveloper.blogspot.com/
https://plus.google.com/+GoogleAdsDevelopers/posts
=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~

You received this message because you are subscribed to the Google
Groups "AdWords API Forum" group.
To post to this group, send email to adwords-api@googlegroups.com
To unsubscribe from this group, send email to
adwords-api+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/adwords-api?hl=en
--- 
You received this message because you are subscribed to the Google Groups 
"AdWords API Forum" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to adwords-api+unsubscr...@googlegroups.com.
Visit this group at https://groups.google.com/group/adwords-api.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/adwords-api/7a3b1630-6719-47ca-83da-26750729eb61%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.