Re: TargetingIdeaService Error: Google API Ads Common Lib Auth Token Exception: The remote server returned an error (404) . I am getting this error when I tried the adwords function in Excel

[Tejas Rane]

>
> 
>
> 
>
>  
>
> "System.Configuration.DictionarySectionHandler"/>
>
>  
>
>  
>
>
>
>
>
>
>
>
>
>
>
>
>
> 
>
>
>
>
>
>
>
>
>
> 
>
>
>
> 
>
>
>
> 
>
> "ENTER_YOUR_COMPANY_OR_APPLICATION_NAME_HERE"/>
>
>
>
>
>
>
>
>
>
>
>
> 
>
>
>
> 
>
>
>
> 
>
>
>
> 
>
>
>
>  
>
>  
>
>
>
>  
>
>
> priority="1" group="0"/>
>
>  
>
>
>
>  
>
>  
>
>
>
>  
>
>
>
>  
>
> 
>
>
> Hi,
>

I have now access to the basic developer token as well. I have a config.php 
file in the excel sheet where I am using.

What should be filled here. ? Little confused. I have added developer 
token, company name, email id and password. 

Still Getting TargetingIdeaService.get Error: 
Google.Api.Ads.Common.Lib.AuthTokenException- The remote server returned an 
error :(404) Not found.

 

-- 
-- 
=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~
Also find us on our blog:
https://googleadsdeveloper.blogspot.com/
=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~

You received this message because you are subscribed to the Google
Groups "AdWords API and Google Ads 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 and Google Ads API Forum" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to adwords-api+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/adwords-api/a1cd1716-4631-43dd-8137-3d6d192c3753%40googlegroups.com.

Start index too high - Ads

[tejas]

We're getting an error that start index is too high when fetching all ads 
for some customers. What's the recommended way of retrieving all ads for 
customers with more than 100,000?

-- 
-- 
=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~
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/46e37aad-086a-4608-a43e-8cf18288f295%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Elevated rate of ERROR_GETTING_RESPONSE_FROM_BACKEND

[tejas]

Hey! We're seeing elevated rates of 
*ReportDownloadError.ERROR_GETTING_RESPONSE_FROM_BACKEND* and 
*urllib.error.HTTPError: 
HTTP Error 500: Internal Server Error*. We retry 5 times with an initial 
delay of 1 minute, exponential backoff factor of 2 minutes, and jitter of 
1. Some days this retry policy solves the issue, but other days, it's 
consistent. Who can I reach out to with more details (preferably privately)?

-- 
-- 
=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~
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/6ecd59bd-4ef1-4a66-8cb6-b906cf70b48b%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: ManagedCustomerService vs CustomerService

[tejas]

What's the actual difference b/w Managed Customer Service .get() and 
Customer Service .get()? I read 
here- 
https://developers.google.com/adwords/api/docs/reference/v201607/ManagedCustomerService
 
that 
>Client Customer Id is required if CustomerIdMode is set to 
CLIENT_EXTERNAL_CUSTOMER_ID. Starting version V201409 ClientCustomerId will 
be required for all requests except for CustomerService.get 
<https://developers.google.com/adwords/api/docs/reference/v201607/CustomerService.html#get>

Doesn't that mean Customer Service .get() would be the best endpoint to use 
for our tool to show a list of AdWords accounts that we can connect to?

On Thursday, September 8, 2016 at 7:11:19 AM UTC-7, Shwetha Vastrad 
(AdWords API Team) wrote:
>
> Hi Tejas,
>
> Here are the production WSDLs for CustomerService and 
> ManagedCustomerService:
>
>- CustomerService: 
>https://adwords.google.com/api/adwords/mcm/v201607/CustomerService?wsdl
>- ManagedCustomerService: 
>
> https://adwords.google.com/api/adwords/mcm/v201607/ManagedCustomerService?wsdl
>
> Regards,
> Shwetha, 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/ed7181ce-6dcc-4d61-b323-ec1948682adf%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: ManagedCustomerService vs CustomerService

[tejas]

Ah, I see. Why 
does https://adwords.google.com/api/adwords/cm/v201607/CustomerService?wsdl 
and 
https://adwords.google.com/api/adwords/cm/v201607/ManagedCustomerService?wsdl 
give a 404, not found 
when https://adwords.google.com/api/adwords/cm/v201607/CampaignService?wsdl 
seems to work. I am just opening in my browser.

On Wednesday, September 7, 2016 at 7:01:42 AM UTC-7, Shwetha Vastrad 
(AdWords API Team) wrote:
>
> Hi Tejas,
>
> Yes, you can use the get 
> <https://developers.google.com/adwords/api/docs/reference/v201607/ManagedCustomerService#get>
>  method 
> on ManagedCustomerService, which will return a list of Customers identified 
> by the selector. This is the method used in the example 
> <https://github.com/googleads/googleads-java-lib/blob/master/examples/adwords_axis/src/main/java/adwords/axis/v201607/accountmanagement/GetAccountHierarchy.java#L91>
>  I 
> provided earlier to get account hierarchy.
>
> Regards,
> Shwetha, 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/3a65054b-2bb8-4ef7-a795-dd7e4ef52535%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: ManagedCustomerService vs CustomerService

[Tejas Manohar]

Can you use *get()* on *ManagedCustomerService* w/ a selector that just
asks for certain *Fields[]* to get all accounts?
On Tue, Sep 6, 2016 at 2:47 PM Tejas Manohar <te...@segment.com> wrote:

> What's the actual method being used to get account hierarchy? I don't see
> it listed here-
> https://developers.google.com/adwords/api/docs/reference/v201607/ManagedCustomerService
>
> On Tue, Sep 6, 2016 at 2:43 PM 'Shwetha Vastrad (AdWords API Team)' via
> AdWords API Forum <adwords-api@googlegroups.com> wrote:
>
>> Hi Tejas,
>>
>> I would recommend that you use ManagedCustomerService
>> <https://developers.google.com/adwords/api/docs/reference/v201607/ManagedCustomerService>
>>  to
>> get all the accounts accessible by the user authenticated in the request.
>> You could use the GetAccountHierarchy
>> <https://github.com/googleads/googleads-java-lib/blob/master/examples/adwords_axis/src/main/java/adwords/axis/v201607/accountmanagement/GetAccountHierarchy.java>
>>  Java
>> example to get the account hierarchy under the current account. Example
>> code in other languages is available here
>> <https://developers.google.com/adwords/api/docs/clientlibraries>.
>>
>> Regards,
>> Shwetha, 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 a topic in the
>> Google Groups "AdWords API Forum" group.
>> To unsubscribe from this topic, visit
>> https://groups.google.com/d/topic/adwords-api/uhbsu9rbTIM/unsubscribe.
>> To unsubscribe from this group and all its topics, 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/55da0517-d25e-4c61-8699-7add7dae1eca%40googlegroups.com
>> <https://groups.google.com/d/msgid/adwords-api/55da0517-d25e-4c61-8699-7add7dae1eca%40googlegroups.com?utm_medium=email_source=footer>
>> .
>> For more options, visit https://groups.google.com/d/optout.
>>
> --
>
> Best regards,
>
> Tejas Manohar
>
-- 

Best regards,

Tejas Manohar

-- 
-- 
=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~
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/CAJU0XY5FGQSf04MDN44vibdP9d0Cpsr79Xfhy79uFC-Fm1pUeQ%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: ManagedCustomerService vs CustomerService

[Tejas Manohar]

What's the actual method being used to get account hierarchy? I don't see
it listed here-
https://developers.google.com/adwords/api/docs/reference/v201607/ManagedCustomerService

On Tue, Sep 6, 2016 at 2:43 PM 'Shwetha Vastrad (AdWords API Team)' via
AdWords API Forum <adwords-api@googlegroups.com> wrote:

> Hi Tejas,
>
> I would recommend that you use ManagedCustomerService
> <https://developers.google.com/adwords/api/docs/reference/v201607/ManagedCustomerService>
>  to
> get all the accounts accessible by the user authenticated in the request.
> You could use the GetAccountHierarchy
> <https://github.com/googleads/googleads-java-lib/blob/master/examples/adwords_axis/src/main/java/adwords/axis/v201607/accountmanagement/GetAccountHierarchy.java>
>  Java
> example to get the account hierarchy under the current account. Example
> code in other languages is available here
> <https://developers.google.com/adwords/api/docs/clientlibraries>.
>
> Regards,
> Shwetha, 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 a topic in the
> Google Groups "AdWords API Forum" group.
> To unsubscribe from this topic, visit
> https://groups.google.com/d/topic/adwords-api/uhbsu9rbTIM/unsubscribe.
> To unsubscribe from this group and all its topics, 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/55da0517-d25e-4c61-8699-7add7dae1eca%40googlegroups.com
> <https://groups.google.com/d/msgid/adwords-api/55da0517-d25e-4c61-8699-7add7dae1eca%40googlegroups.com?utm_medium=email_source=footer>
> .
> For more options, visit https://groups.google.com/d/optout.
>
-- 

Best regards,

Tejas Manohar

-- 
-- 
=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~
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/CAJU0XY4nu7VJ1GQayDqfDAVhVXTVwV_WvdjyoyZfGs9S-eQcEA%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

ManagedCustomerService vs CustomerService

[tejas]

If I want to get all customers / AdWords accounts accessible to the Google 
user currently authenticated, should I use ManagedCustomerService or 
CustomerService?

-- 
-- 
=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~
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/f66dc47c-05bd-4b47-ae8d-2d08f43fe069%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Get Ad Performance Report for Lifetime of Ad

[tejas]

So I was looking into the results of *ALL_TIME* queries, and it seems like 
they actually start at the start time of the Ad. Is this a feature of them? 
I don't see dates dating back to the creation time of the AdWords account 
or anything extremely far back like that.

On Wednesday, August 24, 2016 at 7:26:04 PM UTC-7, Tejas Manohar wrote:
>
> Alrighty. I'll write a process to handle this, but it'd be great if AWQL 
> gets SORT someday :D
>
> On Tue, Aug 23, 2016 at 7:11 AM 'Anthony Madrigal' via AdWords API Forum <
> adwords-api@googlegroups.com> wrote:
>
>> Hi,
>>
>> There is a preset for that date range. It is called ALL_TIME 
>> <https://developers.google.com/adwords/api/docs/guides/reporting#date_ranges>.
>>  
>> However, this date range cannot be used when using AWQL for reports 
>> <https://developers.google.com/adwords/api/docs/guides/awql#using_awql_with_reports>.
>>  
>> There have been instances where data is not sorted chronologically 
>> properly. Unfortunately, the only way to enforce this would be to sort it 
>> after you run the report.
>>
>> Regards,
>> Anthony
>> 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 a topic in the 
>> Google Groups "AdWords API Forum" group.
>> To unsubscribe from this topic, visit 
>> https://groups.google.com/d/topic/adwords-api/QTMNdaamOvY/unsubscribe.
>> To unsubscribe from this group and all its topics, 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/60d6c6e4-ff06-468d-9759-1874b7f66cd2%40googlegroups.com
>>  
>> <https://groups.google.com/d/msgid/adwords-api/60d6c6e4-ff06-468d-9759-1874b7f66cd2%40googlegroups.com?utm_medium=email_source=footer>
>> .
>> For more options, visit https://groups.google.com/d/optout.
>>
> -- 
>
> Best regards,
>
> Tejas Manohar
>

-- 
-- 
=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~
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/390f0b72-0bba-405e-8d6a-33c3aca5b9c6%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Date ranges Adwords Reports

[tejas]

Do clicks take some time to show up in the Click Performance Reports? Is 
date range exclusive or inclusive?

-- 
-- 
=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~
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/217daa0e-1869-4120-80a1-5ead678f2565%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Suggestion: Go library

[Tejas Manohar]

Thanks! Right now, we've been using Python internally, but it would be nice
to be able to use the same technology throughout (but also seems like a lot
of work to maintain an external client).

On Tue, Aug 30, 2016 at 2:23 PM 'Vishal Vinayak (Adwords API Team)' via
AdWords API Forum <adwords-api@googlegroups.com> wrote:

> Hi Tejas,
>
> Appreciate your suggestion. I have conveyed the same to the team.
>
> Regards,
> Vishal, 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 a topic in the
> Google Groups "AdWords API Forum" group.
> To unsubscribe from this topic, visit
> https://groups.google.com/d/topic/adwords-api/qNuy68tIBx0/unsubscribe.
> To unsubscribe from this group and all its topics, 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/200591ad-bcdf-4562-966c-b7ece3eb6d8e%40googlegroups.com
> <https://groups.google.com/d/msgid/adwords-api/200591ad-bcdf-4562-966c-b7ece3eb6d8e%40googlegroups.com?utm_medium=email_source=footer>
> .
> For more options, visit https://groups.google.com/d/optout.
>
-- 

Best regards,

Tejas Manohar

-- 
-- 
=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~
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/CAJU0XY7agXbF-Lr9wcxQj0nRYV_BV2ctNm9sh1_-9E2qGhzToQ%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Suggestion: Go library

[tejas]

There's no Go client for the AdWords API at the moment. It would be nice to 
have one (sorta ironic since Google maintains Go :P).

-- 
-- 
=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~
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/334111ae-53a7-4de0-993f-9602da39b99f%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: AdWords API Python - Internal Error or Parsing Error

[Tejas Manohar]

Ah yes, i tried utf8 yesterday and t worked. Thanks a lot Mark! :)
On Fri, Aug 26, 2016 at 10:55 AM Mark Saniscalchi <
msanis88.adxbuyerapiadvi...@gmail.com> wrote:

> Hello Tejas,
>
> The googleads library is compatible with Python 3, as indicated by the
> fact that the report data was successfully retrieved. However, if you're
> decoding the report output (containing non-ascii data) to ascii at some
> point, that will raise an Exception. Often times, the encoding will default
> to the system encoding, which could potentially be something other than
> utf-8. If an option to set the encoding is offered, try setting it to utf-8.
>
> Regards,
> Mark
>
>
> On Thursday, August 25, 2016 at 5:07:01 PM UTC-4, Tejas Manohar wrote:
>
>> Moreover, looks like TextIOWrapper accepts an encoding option...
>> https://docs.python.org/2/library/io.html#io.TextIOWrapper - what would
>> you suggest here (considering what sort of data the googleadwords lib /
>> AdWords API is returning)?
>>
>> On Thu, Aug 25, 2016 at 2:05 PM Tejas Manohar <te...@segment.com> wrote:
>>
> *from csv import DictReader as parse_csv*
>>> *from io import TextIOWrapper*
>>>
>>> Gotcha. Those are both standard library methods. Do you have an
>>> alternative way you'd suggest decoding in a Python 3 environment (given the
>>> Unicode changes)? I'd be happy to migrate. If really needed, I can move
>>> this service to Python 2 (fixing this error is top priority)... but that
>>> may require some widespread changes (though small ones). Thanks again!
>>>
>>> (Sorry if I've asked a stupid question. Python frankly isn't my strong
>>> point. Used it because maintaining an AdWords SOAP wrapper in Go or Node is
>>> quite a burden.)
>>>
>> On Thu, Aug 25, 2016 at 1:58 PM Mark Saniscalchi <
>>> msanis88.adxb...@gmail.com> wrote:
>>>
>> Hello Tejas,
>>>>
>>>> Based on the stacktrace, I can see that the root cause is that you're
>>>> decoding with ASCII specified as the encoding. That will produce a
>>>> UnicodeEncode error if non-ASCII text appears in the reporting data. It
>>>> appears that one of the libraries you're using is probably the culprit
>>>> here, but it's hard to tell which. I'm pretty confident this isn't caused
>>>> by the googleads library though. I suggest taking a closer look at
>>>> TextIOWrapper and the parse_csv method.
>>>>
>>>> Regards,
>>>> Mark
>>>>
>>>>
>>>> On Thursday, August 25, 2016 at 4:24:43 PM UTC-4, Tejas Manohar wrote:
>>>>
>>>>> Hey Mark,
>>>>>
>>>>> The issue is back and is not being solved by retries for our customer. 
>>>>> Here's
>>>>> code + logs-
>>>>> https://gist.github.com/tejasmanohar/24f15ddb830f8bc611e9e50fdf56f688.
>>>>> Let me know what other information I can provide to help you debug this.
>>>>> It's currently blocking syncs with our beta AdWords Source at Segment (
>>>>> https://segment.com/sources) for a subset of customers (launch date
>>>>> next week).
>>>>>
>>>>> On Tue, Aug 23, 2016 at 4:57 PM Tejas Manohar <te...@segment.com>
>>>>> wrote:
>>>>>
>>>> Got it. We have not seen the error today. I'll follow-up if it comes
>>>>>> back. Thanks!
>>>>>>
>>>>>> On Tue, Aug 23, 2016 at 4:21 PM Mark Saniscalchi <
>>>>>> msanis88.adxb...@gmail.com> wrote:
>>>>>>
>>>>> Hello Tejas,
>>>>>>>
>>>>>>> The stacktrace you linked to actually seems indicative of a separate
>>>>>>> issue, I suspect you're seeing this issue
>>>>>>> <https://groups.google.com/forum/#!topic/adwords-api/BXnAVhYe538>
>>>>>>> instead. I can tell because the UnicodeDecodeError you're receiving
>>>>>>> indicates that you're likely receiving something that was gzipped, but 
>>>>>>> your
>>>>>>> report definition indicates that you set the format to CSV.
>>>>>>>
>>>>>>> That said, I can't verify whether the original issue is still in
>>>>>>> effect. If you're still experiencing issues with new reports, can you 
>>>>>>> send
>>>>>>> another report definition / stacktrace?
>>>>>>>
>>>>

Re: AdWords API Python - Internal Error or Parsing Error

[Tejas Manohar]

Moreover, looks like TextIOWrapper accepts an encoding option...
https://docs.python.org/2/library/io.html#io.TextIOWrapper - what would you
suggest here (considering what sort of data the googleadwords lib / AdWords
API is returning)?

On Thu, Aug 25, 2016 at 2:05 PM Tejas Manohar <te...@segment.com> wrote:

> *from csv import DictReader as parse_csv*
> *from io import TextIOWrapper*
>
> Gotcha. Those are both standard library methods. Do you have an
> alternative way you'd suggest decoding in a Python 3 environment (given the
> Unicode changes)? I'd be happy to migrate. If really needed, I can move
> this service to Python 2 (fixing this error is top priority)... but that
> may require some widespread changes (though small ones). Thanks again!
>
> (Sorry if I've asked a stupid question. Python frankly isn't my strong
> point. Used it because maintaining an AdWords SOAP wrapper in Go or Node is
> quite a burden.)
>
> On Thu, Aug 25, 2016 at 1:58 PM Mark Saniscalchi <
> msanis88.adxbuyerapiadvi...@gmail.com> wrote:
>
>> Hello Tejas,
>>
>> Based on the stacktrace, I can see that the root cause is that you're
>> decoding with ASCII specified as the encoding. That will produce a
>> UnicodeEncode error if non-ASCII text appears in the reporting data. It
>> appears that one of the libraries you're using is probably the culprit
>> here, but it's hard to tell which. I'm pretty confident this isn't caused
>> by the googleads library though. I suggest taking a closer look at
>> TextIOWrapper and the parse_csv method.
>>
>> Regards,
>> Mark
>>
>>
>> On Thursday, August 25, 2016 at 4:24:43 PM UTC-4, Tejas Manohar wrote:
>>
>>> Hey Mark,
>>>
>>> The issue is back and is not being solved by retries for our customer. 
>>> Here's
>>> code + logs-
>>> https://gist.github.com/tejasmanohar/24f15ddb830f8bc611e9e50fdf56f688.
>>> Let me know what other information I can provide to help you debug this.
>>> It's currently blocking syncs with our beta AdWords Source at Segment (
>>> https://segment.com/sources) for a subset of customers (launch date
>>> next week).
>>>
>>> On Tue, Aug 23, 2016 at 4:57 PM Tejas Manohar <te...@segment.com> wrote:
>>>
>> Got it. We have not seen the error today. I'll follow-up if it comes
>>>> back. Thanks!
>>>>
>>>> On Tue, Aug 23, 2016 at 4:21 PM Mark Saniscalchi <
>>>> msanis88.adxb...@gmail.com> wrote:
>>>>
>>> Hello Tejas,
>>>>>
>>>>> The stacktrace you linked to actually seems indicative of a separate
>>>>> issue, I suspect you're seeing this issue
>>>>> <https://groups.google.com/forum/#!topic/adwords-api/BXnAVhYe538>
>>>>> instead. I can tell because the UnicodeDecodeError you're receiving
>>>>> indicates that you're likely receiving something that was gzipped, but 
>>>>> your
>>>>> report definition indicates that you set the format to CSV.
>>>>>
>>>>> That said, I can't verify whether the original issue is still in
>>>>> effect. If you're still experiencing issues with new reports, can you send
>>>>> another report definition / stacktrace?
>>>>>
>>>>> Regards,
>>>>> Mark
>>>>>
>>>>> On Friday, August 19, 2016 at 10:12:39 PM UTC-4, Tejas Manohar wrote:
>>>>>
>>>>>> Hey Mark,
>>>>>>
>>>>>> Sorry for the delay here. Here's report definition + error in logs-
>>>>>> https://gist.github.com/tejasmanohar/fd539957f8653a6c8375cd3b5a2cd7f5.
>>>>>> How can I determine the locale of customers? Btw, this error happens on
>>>>>> many reports for this customer, not just one, so I can provide more
>>>>>> examples, and retries are solving the problem for now, but it slows
>>>>>> everything down.
>>>>>>
>>>>>> Let me know what else I can provide to help. Thanks!
>>>>>>
>>>>>> On Fri, Jul 29, 2016 at 3:13 PM Tejas Manohar <te...@segment.com>
>>>>>> wrote:
>>>>>>
>>>>> Hey Mark,
>>>>>>>
>>>>>>> Thanks! I will get all this information to you on Monday.
>>>>>>>
>>>>>>> On Fri, Jul 29, 2016 at 3:05 PM Mark Saniscalchi <
>>>>>>> msanis88.adxb...@gmail.com> wrote:
>>>>>>>
>>>>>

Re: AdWords API Python - Internal Error or Parsing Error

[Tejas Manohar]

*from csv import DictReader as parse_csv*
*from io import TextIOWrapper*

Gotcha. Those are both standard library methods. Do you have an alternative
way you'd suggest decoding in a Python 3 environment (given the Unicode
changes)? I'd be happy to migrate. If really needed, I can move this
service to Python 2 (fixing this error is top priority)... but that may
require some widespread changes (though small ones). Thanks again!

(Sorry if I've asked a stupid question. Python frankly isn't my strong
point. Used it because maintaining an AdWords SOAP wrapper in Go or Node is
quite a burden.)

On Thu, Aug 25, 2016 at 1:58 PM Mark Saniscalchi <
msanis88.adxbuyerapiadvi...@gmail.com> wrote:

> Hello Tejas,
>
> Based on the stacktrace, I can see that the root cause is that you're
> decoding with ASCII specified as the encoding. That will produce a
> UnicodeEncode error if non-ASCII text appears in the reporting data. It
> appears that one of the libraries you're using is probably the culprit
> here, but it's hard to tell which. I'm pretty confident this isn't caused
> by the googleads library though. I suggest taking a closer look at
> TextIOWrapper and the parse_csv method.
>
> Regards,
> Mark
>
>
> On Thursday, August 25, 2016 at 4:24:43 PM UTC-4, Tejas Manohar wrote:
>
>> Hey Mark,
>>
>> The issue is back and is not being solved by retries for our customer. Here's
>> code + logs-
>> https://gist.github.com/tejasmanohar/24f15ddb830f8bc611e9e50fdf56f688.
>> Let me know what other information I can provide to help you debug this.
>> It's currently blocking syncs with our beta AdWords Source at Segment (
>> https://segment.com/sources) for a subset of customers (launch date next
>> week).
>>
>> On Tue, Aug 23, 2016 at 4:57 PM Tejas Manohar <te...@segment.com> wrote:
>>
> Got it. We have not seen the error today. I'll follow-up if it comes back.
>>> Thanks!
>>>
>>> On Tue, Aug 23, 2016 at 4:21 PM Mark Saniscalchi <
>>> msanis88.adxb...@gmail.com> wrote:
>>>
>> Hello Tejas,
>>>>
>>>> The stacktrace you linked to actually seems indicative of a separate
>>>> issue, I suspect you're seeing this issue
>>>> <https://groups.google.com/forum/#!topic/adwords-api/BXnAVhYe538>
>>>> instead. I can tell because the UnicodeDecodeError you're receiving
>>>> indicates that you're likely receiving something that was gzipped, but your
>>>> report definition indicates that you set the format to CSV.
>>>>
>>>> That said, I can't verify whether the original issue is still in
>>>> effect. If you're still experiencing issues with new reports, can you send
>>>> another report definition / stacktrace?
>>>>
>>>> Regards,
>>>> Mark
>>>>
>>>> On Friday, August 19, 2016 at 10:12:39 PM UTC-4, Tejas Manohar wrote:
>>>>
>>>>> Hey Mark,
>>>>>
>>>>> Sorry for the delay here. Here's report definition + error in logs-
>>>>> https://gist.github.com/tejasmanohar/fd539957f8653a6c8375cd3b5a2cd7f5.
>>>>> How can I determine the locale of customers? Btw, this error happens on
>>>>> many reports for this customer, not just one, so I can provide more
>>>>> examples, and retries are solving the problem for now, but it slows
>>>>> everything down.
>>>>>
>>>>> Let me know what else I can provide to help. Thanks!
>>>>>
>>>>> On Fri, Jul 29, 2016 at 3:13 PM Tejas Manohar <te...@segment.com>
>>>>> wrote:
>>>>>
>>>> Hey Mark,
>>>>>>
>>>>>> Thanks! I will get all this information to you on Monday.
>>>>>>
>>>>>> On Fri, Jul 29, 2016 at 3:05 PM Mark Saniscalchi <
>>>>>> msanis88.adxb...@gmail.com> wrote:
>>>>>>
>>>>> Hello Tejas,
>>>>>>>
>>>>>>> I'm the owner of the Python Client Library, and am taking a look at
>>>>>>> this issue. It's difficult to say for certain whether this is a client 
>>>>>>> or
>>>>>>> server-based issue because the snippet and stacktrace are incomplete, 
>>>>>>> but
>>>>>>> I'm leaning towards this being a server issue or a mixture of both.
>>>>>>> The AdWordsReportBadRequestError is raised when a reportDownloadError is
>>>>>>> detected in the response--this is usually the result of bad input.
>>>>&

Re: AdWords API Python - Internal Error or Parsing Error

[Tejas Manohar]

Hey Mark,

The issue is back and is not being solved by retries for our customer. Here's
code + logs-
https://gist.github.com/tejasmanohar/24f15ddb830f8bc611e9e50fdf56f688. Let
me know what other information I can provide to help you debug this. It's
currently blocking syncs with our beta AdWords Source at Segment (
https://segment.com/sources) for a subset of customers (launch date next
week).

On Tue, Aug 23, 2016 at 4:57 PM Tejas Manohar <te...@segment.com> wrote:

> Got it. We have not seen the error today. I'll follow-up if it comes back.
> Thanks!
>
> On Tue, Aug 23, 2016 at 4:21 PM Mark Saniscalchi <
> msanis88.adxbuyerapiadvi...@gmail.com> wrote:
>
>> Hello Tejas,
>>
>> The stacktrace you linked to actually seems indicative of a separate
>> issue, I suspect you're seeing this issue
>> <https://groups.google.com/forum/#!topic/adwords-api/BXnAVhYe538>
>> instead. I can tell because the UnicodeDecodeError you're receiving
>> indicates that you're likely receiving something that was gzipped, but your
>> report definition indicates that you set the format to CSV.
>>
>> That said, I can't verify whether the original issue is still in effect.
>> If you're still experiencing issues with new reports, can you send another
>> report definition / stacktrace?
>>
>> Regards,
>> Mark
>>
>> On Friday, August 19, 2016 at 10:12:39 PM UTC-4, Tejas Manohar wrote:
>>
>>> Hey Mark,
>>>
>>> Sorry for the delay here. Here's report definition + error in logs-
>>> https://gist.github.com/tejasmanohar/fd539957f8653a6c8375cd3b5a2cd7f5.
>>> How can I determine the locale of customers? Btw, this error happens on
>>> many reports for this customer, not just one, so I can provide more
>>> examples, and retries are solving the problem for now, but it slows
>>> everything down.
>>>
>>> Let me know what else I can provide to help. Thanks!
>>>
>>> On Fri, Jul 29, 2016 at 3:13 PM Tejas Manohar <te...@segment.com> wrote:
>>>
>> Hey Mark,
>>>>
>>>> Thanks! I will get all this information to you on Monday.
>>>>
>>>> On Fri, Jul 29, 2016 at 3:05 PM Mark Saniscalchi <
>>>> msanis88.adxb...@gmail.com> wrote:
>>>>
>>> Hello Tejas,
>>>>>
>>>>> I'm the owner of the Python Client Library, and am taking a look at
>>>>> this issue. It's difficult to say for certain whether this is a client or
>>>>> server-based issue because the snippet and stacktrace are incomplete, but
>>>>> I'm leaning towards this being a server issue or a mixture of both.
>>>>> The AdWordsReportBadRequestError is raised when a reportDownloadError is
>>>>> detected in the response--this is usually the result of bad input.
>>>>>
>>>>> The UnicodeDecodeError is a bit of a mystery at the moment, as I can't
>>>>> replicate it (also in Python 3) with a data source known to contain utf-8.
>>>>> The fact that it seems to be expecting ascii input is telling, and I'm
>>>>> wondering if something else in your program would be expecting ascii 
>>>>> input?
>>>>> It might be the TextIOWrapper, which will default to the system encoding
>>>>> (which may be ascii in your case).
>>>>>
>>>>> In short, I can't specifically point out what went wrong here because
>>>>> I don't have the full picture. I need to at least see what the report
>>>>> definition contains in order to attempt to reproduce
>>>>> theAdWordsReportBadRequestError; it'd also be helpful if I knew what 
>>>>> locale
>>>>> settings are.
>>>>>
>>>>> Regards,
>>>>> Mark
>>>>>
>>>>> On Tuesday, July 26, 2016 at 9:18:17 PM UTC-4, Tejas Manohar wrote:
>>>>>
>>>>>> Hey Shwetha,
>>>>>>
>>>>>> I've confirmed that this issue is resolved by retrying, but it
>>>>>> happens very consistently. Since it's resolved by retrying and I'm using
>>>>>> codecs#getreader which knows how to handle Python unicode in both v2 and
>>>>>> v3, I really believe this issue is due to malformed data sent back from 
>>>>>> the
>>>>>> API as a result of an error. Let me know what more info I could provide 
>>>>>> to
>>>>>> help. Thanks!
>>>>>>
>>>>>> On Wed, Jul 20, 2016 at 

Re: Get Ad Performance Report for Lifetime of Ad

[Tejas Manohar]

Alrighty. I'll write a process to handle this, but it'd be great if AWQL
gets SORT someday :D

On Tue, Aug 23, 2016 at 7:11 AM 'Anthony Madrigal' via AdWords API Forum <
adwords-api@googlegroups.com> wrote:

> Hi,
>
> There is a preset for that date range. It is called ALL_TIME
> <https://developers.google.com/adwords/api/docs/guides/reporting#date_ranges>.
> However, this date range cannot be used when using AWQL for reports
> <https://developers.google.com/adwords/api/docs/guides/awql#using_awql_with_reports>.
> There have been instances where data is not sorted chronologically
> properly. Unfortunately, the only way to enforce this would be to sort it
> after you run the report.
>
> Regards,
> Anthony
> 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 a topic in the
> Google Groups "AdWords API Forum" group.
> To unsubscribe from this topic, visit
> https://groups.google.com/d/topic/adwords-api/QTMNdaamOvY/unsubscribe.
> To unsubscribe from this group and all its topics, 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/60d6c6e4-ff06-468d-9759-1874b7f66cd2%40googlegroups.com
> <https://groups.google.com/d/msgid/adwords-api/60d6c6e4-ff06-468d-9759-1874b7f66cd2%40googlegroups.com?utm_medium=email_source=footer>
> .
> For more options, visit https://groups.google.com/d/optout.
>
-- 

Best regards,

Tejas Manohar

-- 
-- 
=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~
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/CAJU0XY6GPhpQ5RYaY%3D%2BAe085%3DyCwf%3D%3DVjVRvBKMt4T_Nmjp5Nw%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: AdWords API Python - Internal Error or Parsing Error

[Tejas Manohar]

Got it. We have not seen the error today. I'll follow-up if it comes back.
Thanks!

On Tue, Aug 23, 2016 at 4:21 PM Mark Saniscalchi <
msanis88.adxbuyerapiadvi...@gmail.com> wrote:

> Hello Tejas,
>
> The stacktrace you linked to actually seems indicative of a separate
> issue, I suspect you're seeing this issue
> <https://groups.google.com/forum/#!topic/adwords-api/BXnAVhYe538>
> instead. I can tell because the UnicodeDecodeError you're receiving
> indicates that you're likely receiving something that was gzipped, but your
> report definition indicates that you set the format to CSV.
>
> That said, I can't verify whether the original issue is still in effect.
> If you're still experiencing issues with new reports, can you send another
> report definition / stacktrace?
>
> Regards,
> Mark
>
> On Friday, August 19, 2016 at 10:12:39 PM UTC-4, Tejas Manohar wrote:
>
>> Hey Mark,
>>
>> Sorry for the delay here. Here's report definition + error in logs-
>> https://gist.github.com/tejasmanohar/fd539957f8653a6c8375cd3b5a2cd7f5.
>> How can I determine the locale of customers? Btw, this error happens on
>> many reports for this customer, not just one, so I can provide more
>> examples, and retries are solving the problem for now, but it slows
>> everything down.
>>
>> Let me know what else I can provide to help. Thanks!
>>
>> On Fri, Jul 29, 2016 at 3:13 PM Tejas Manohar <te...@segment.com> wrote:
>>
> Hey Mark,
>>>
>>> Thanks! I will get all this information to you on Monday.
>>>
>>> On Fri, Jul 29, 2016 at 3:05 PM Mark Saniscalchi <
>>> msanis88.adxb...@gmail.com> wrote:
>>>
>> Hello Tejas,
>>>>
>>>> I'm the owner of the Python Client Library, and am taking a look at
>>>> this issue. It's difficult to say for certain whether this is a client or
>>>> server-based issue because the snippet and stacktrace are incomplete, but
>>>> I'm leaning towards this being a server issue or a mixture of both.
>>>> The AdWordsReportBadRequestError is raised when a reportDownloadError is
>>>> detected in the response--this is usually the result of bad input.
>>>>
>>>> The UnicodeDecodeError is a bit of a mystery at the moment, as I can't
>>>> replicate it (also in Python 3) with a data source known to contain utf-8.
>>>> The fact that it seems to be expecting ascii input is telling, and I'm
>>>> wondering if something else in your program would be expecting ascii input?
>>>> It might be the TextIOWrapper, which will default to the system encoding
>>>> (which may be ascii in your case).
>>>>
>>>> In short, I can't specifically point out what went wrong here because I
>>>> don't have the full picture. I need to at least see what the report
>>>> definition contains in order to attempt to reproduce
>>>> theAdWordsReportBadRequestError; it'd also be helpful if I knew what locale
>>>> settings are.
>>>>
>>>> Regards,
>>>> Mark
>>>>
>>>> On Tuesday, July 26, 2016 at 9:18:17 PM UTC-4, Tejas Manohar wrote:
>>>>
>>>>> Hey Shwetha,
>>>>>
>>>>> I've confirmed that this issue is resolved by retrying, but it happens
>>>>> very consistently. Since it's resolved by retrying and I'm using
>>>>> codecs#getreader which knows how to handle Python unicode in both v2 and
>>>>> v3, I really believe this issue is due to malformed data sent back from 
>>>>> the
>>>>> API as a result of an error. Let me know what more info I could provide to
>>>>> help. Thanks!
>>>>>
>>>>> On Wed, Jul 20, 2016 at 1:56 PM 'Shwetha Vastrad (AdWords API Team)'
>>>>> via AdWords API Forum <adwor...@googlegroups.com> wrote:
>>>>>
>>>> Hi Tejas,
>>>>>>
>>>>>> This issue is related to how Python handles data streams and not
>>>>>> specific to AdWords API. I suggest that you post your query in the 
>>>>>> AdWords
>>>>>> API Python library repository
>>>>>> <https://github.com/googleads/googleads-python-lib> as they are
>>>>>> better equipped to help you out.
>>>>>>
>>>>>> Regards,
>>>>>> Shwetha, AdWords API Team.
>>>>>>
>>>>>> --
>>>>>> --
>>>>>> =~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~

Re: Get Ad Performance Report for Lifetime of Ad

[tejas]

Gotcha. Is there a preset all time date range, or were you just suggesting 
I set some unreasonably old start date and end date of today? Also, is the 
report data returned sorted chronologically by Day/Date? Is there any way 
to enforce this? It'd help to be able to assume this rather than having to 
pull all the data down into files, sort, etc. since the results can be too 
big to fit in memory.

On Monday, August 22, 2016 at 3:26:54 PM UTC-7, Anthony Madrigal wrote:
>
> Hi,
>
> There is no start date field for ads available in AdWords API. The best 
> workaround would be to include an all time date range and include a Date 
> field in the report. You can safely assume that the date when the ad 
> started receiving impressions is around the time it was created.
>
> Regards,
> Anthony
> 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/070709b1-6de5-49bb-a6a9-c5e5b18076c4%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Get Ad Performance Report for Lifetime of Ad

[tejas]

My program needs to fetch ad performance report(s) for the lifetime of an 
ad. It looks like you need to provide a dateRange to request a report, but 
I don't see a way to find out when the ad started 
(https://developers.google.com/adwords/api/docs/reference/v201607/AdGroupAdService).
 
I do see Start/EndDate fields on campaign and ad group, but if I request a 
report for the range of one of those, how would I differentiate days with 
zero impressions and days when the ad simply wasn't running?

-- 
-- 
=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~
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/0b20955b-dd85-4025-8833-cc9f0e43df79%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: AdWords API Python - Internal Error or Parsing Error

[Tejas Manohar]

Hey Mark,

Sorry for the delay here. Here's report definition + error in logs-
https://gist.github.com/tejasmanohar/fd539957f8653a6c8375cd3b5a2cd7f5. How
can I determine the locale of customers? Btw, this error happens on many
reports for this customer, not just one, so I can provide more examples,
and retries are solving the problem for now, but it slows everything down.

Let me know what else I can provide to help. Thanks!

On Fri, Jul 29, 2016 at 3:13 PM Tejas Manohar <te...@segment.com> wrote:

> Hey Mark,
>
> Thanks! I will get all this information to you on Monday.
>
> On Fri, Jul 29, 2016 at 3:05 PM Mark Saniscalchi <
> msanis88.adxbuyerapiadvi...@gmail.com> wrote:
>
>> Hello Tejas,
>>
>> I'm the owner of the Python Client Library, and am taking a look at this
>> issue. It's difficult to say for certain whether this is a client or
>> server-based issue because the snippet and stacktrace are incomplete, but
>> I'm leaning towards this being a server issue or a mixture of both.
>> The AdWordsReportBadRequestError is raised when a reportDownloadError is
>> detected in the response--this is usually the result of bad input.
>>
>> The UnicodeDecodeError is a bit of a mystery at the moment, as I can't
>> replicate it (also in Python 3) with a data source known to contain utf-8.
>> The fact that it seems to be expecting ascii input is telling, and I'm
>> wondering if something else in your program would be expecting ascii input?
>> It might be the TextIOWrapper, which will default to the system encoding
>> (which may be ascii in your case).
>>
>> In short, I can't specifically point out what went wrong here because I
>> don't have the full picture. I need to at least see what the report
>> definition contains in order to attempt to reproduce
>> theAdWordsReportBadRequestError; it'd also be helpful if I knew what locale
>> settings are.
>>
>> Regards,
>> Mark
>>
>> On Tuesday, July 26, 2016 at 9:18:17 PM UTC-4, Tejas Manohar wrote:
>>
>>> Hey Shwetha,
>>>
>>> I've confirmed that this issue is resolved by retrying, but it happens
>>> very consistently. Since it's resolved by retrying and I'm using
>>> codecs#getreader which knows how to handle Python unicode in both v2 and
>>> v3, I really believe this issue is due to malformed data sent back from the
>>> API as a result of an error. Let me know what more info I could provide to
>>> help. Thanks!
>>>
>>> On Wed, Jul 20, 2016 at 1:56 PM 'Shwetha Vastrad (AdWords API Team)' via
>>> AdWords API Forum <adwor...@googlegroups.com> wrote:
>>>
>> Hi Tejas,
>>>>
>>>> This issue is related to how Python handles data streams and not
>>>> specific to AdWords API. I suggest that you post your query in the AdWords
>>>> API Python library repository
>>>> <https://github.com/googleads/googleads-python-lib> as they are better
>>>> equipped to help you out.
>>>>
>>>> Regards,
>>>> Shwetha, 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 adwor...@googlegroups.com
>>>
>>>
>>>> To unsubscribe from this group, send email to
>>>>
>>> adwords-api...@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 a topic in the
>>>> Google Groups "AdWords API Forum" group.
>>>> To unsubscribe from this topic, visit
>>>> https://groups.google.com/d/topic/adwords-api/Jmbqifyr_Ro/unsubscribe.
>>>>
>>> To unsubscribe from this group and all its topics, send an email to
>>>> adwords-api...@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/780b5d92-b91a-41d5-9467-246325408472%40googlegroups.com
&

Re: AdWords API Python - Internal Error or Parsing Error

[Tejas Manohar]

Hey Mark,

Thanks! I will get all this information to you on Monday.

On Fri, Jul 29, 2016 at 3:05 PM Mark Saniscalchi <
msanis88.adxbuyerapiadvi...@gmail.com> wrote:

> Hello Tejas,
>
> I'm the owner of the Python Client Library, and am taking a look at this
> issue. It's difficult to say for certain whether this is a client or
> server-based issue because the snippet and stacktrace are incomplete, but
> I'm leaning towards this being a server issue or a mixture of both.
> The AdWordsReportBadRequestError is raised when a reportDownloadError is
> detected in the response--this is usually the result of bad input.
>
> The UnicodeDecodeError is a bit of a mystery at the moment, as I can't
> replicate it (also in Python 3) with a data source known to contain utf-8.
> The fact that it seems to be expecting ascii input is telling, and I'm
> wondering if something else in your program would be expecting ascii input?
> It might be the TextIOWrapper, which will default to the system encoding
> (which may be ascii in your case).
>
> In short, I can't specifically point out what went wrong here because I
> don't have the full picture. I need to at least see what the report
> definition contains in order to attempt to reproduce
> theAdWordsReportBadRequestError; it'd also be helpful if I knew what locale
> settings are.
>
> Regards,
> Mark
>
> On Tuesday, July 26, 2016 at 9:18:17 PM UTC-4, Tejas Manohar wrote:
>
>> Hey Shwetha,
>>
>> I've confirmed that this issue is resolved by retrying, but it happens
>> very consistently. Since it's resolved by retrying and I'm using
>> codecs#getreader which knows how to handle Python unicode in both v2 and
>> v3, I really believe this issue is due to malformed data sent back from the
>> API as a result of an error. Let me know what more info I could provide to
>> help. Thanks!
>>
>> On Wed, Jul 20, 2016 at 1:56 PM 'Shwetha Vastrad (AdWords API Team)' via
>> AdWords API Forum <adwor...@googlegroups.com> wrote:
>>
> Hi Tejas,
>>>
>>> This issue is related to how Python handles data streams and not
>>> specific to AdWords API. I suggest that you post your query in the AdWords
>>> API Python library repository
>>> <https://github.com/googleads/googleads-python-lib> as they are better
>>> equipped to help you out.
>>>
>>> Regards,
>>> Shwetha, 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 adwor...@googlegroups.com
>>
>>
>>> To unsubscribe from this group, send email to
>>>
>> adwords-api...@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 a topic in the
>>> Google Groups "AdWords API Forum" group.
>>> To unsubscribe from this topic, visit
>>> https://groups.google.com/d/topic/adwords-api/Jmbqifyr_Ro/unsubscribe.
>>>
>> To unsubscribe from this group and all its topics, send an email to
>>> adwords-api...@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/780b5d92-b91a-41d5-9467-246325408472%40googlegroups.com
>>> <https://groups.google.com/d/msgid/adwords-api/780b5d92-b91a-41d5-9467-246325408472%40googlegroups.com?utm_medium=email_source=footer>
>>> .
>>> For more options, visit https://groups.google.com/d/optout.
>>>
>> --
>> Best regards,
>>
>> Tejas Manohar
>>
> --
> --
> =~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~
> 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+unsubsc

Re: AdWords API Python - Internal Error or Parsing Error

[Tejas Manohar]

Hey Shwetha,

I've confirmed that this issue is resolved by retrying, but it happens very
consistently. Since it's resolved by retrying and I'm using
codecs#getreader which knows how to handle Python unicode in both v2 and
v3, I really believe this issue is due to malformed data sent back from the
API as a result of an error. Let me know what more info I could provide to
help. Thanks!

On Wed, Jul 20, 2016 at 1:56 PM 'Shwetha Vastrad (AdWords API Team)' via
AdWords API Forum <adwords-api@googlegroups.com> wrote:

> Hi Tejas,
>
> This issue is related to how Python handles data streams and not specific
> to AdWords API. I suggest that you post your query in the AdWords API
> Python library repository
> <https://github.com/googleads/googleads-python-lib> as they are better
> equipped to help you out.
>
> Regards,
> Shwetha, 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 a topic in the
> Google Groups "AdWords API Forum" group.
> To unsubscribe from this topic, visit
> https://groups.google.com/d/topic/adwords-api/Jmbqifyr_Ro/unsubscribe.
> To unsubscribe from this group and all its topics, 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/780b5d92-b91a-41d5-9467-246325408472%40googlegroups.com
> <https://groups.google.com/d/msgid/adwords-api/780b5d92-b91a-41d5-9467-246325408472%40googlegroups.com?utm_medium=email_source=footer>
> .
> For more options, visit https://groups.google.com/d/optout.
>
-- 
Best regards,

Tejas Manohar

-- 
-- 
=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~
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/CAJU0XY5bU1d66y8-5SDgMwALTDupnXAq7KKtePiikdLQwGxDnA%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: AdWords API Python - Internal Error or Parsing Error

[tejas]

Hm, that does not parse the CSV though. Other than that, it's practically 
the same, no?

On Monday, July 18, 2016 at 2:10:00 PM UTC-7, Shwetha Vastrad (AdWords API 
Team) wrote:
>
> Hi Tejas,
>
> Have you tried using the download_criteria_report_as_stream.py 
> <https://github.com/googleads/googleads-python-lib/blob/master/examples/adwords/v201605/reporting/download_criteria_report_as_stream.py>
>  example 
> to stream AdWords reports? Could you use the below code snippet to process 
> *stream_data*?
>
>
>  try:
>while True: 
>   chunk = stream_data.read(CHUNK_SIZE) 
>   if not chunk: break 
>   report_data.write(chunk.decode() if sys.version_info[0] 
>   == 3 and getattr(report_data, 'mode', 'w') 
> == 'w' else chunk) 
>print report_data.getvalue() 
> finally: 
>report_data.close() 
>stream_data.close()
>
> If this doesn't work, please provide the complete report definition used 
> and any error message received along with your clientCustomerID. Please use 
> *Reply 
> privately to author* when responding. 
>
> Regards,
> Shwetha, 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/e945f2a9-aac3-47e1-9d48-bbdc3c70a369%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: AdWords API Python - Internal Error or Parsing Error

[Tejas Manohar]

Hm, that doesn't parse the CSV though.

On Mon, Jul 18, 2016 at 2:10 PM 'Shwetha Vastrad (AdWords API Team)' via
AdWords API Forum <adwords-api@googlegroups.com> wrote:

> Hi Tejas,
>
> Have you tried using the download_criteria_report_as_stream.py
> <https://github.com/googleads/googleads-python-lib/blob/master/examples/adwords/v201605/reporting/download_criteria_report_as_stream.py>
>  example
> to stream AdWords reports? Could you use the below code snippet to process
> *stream_data*?
>
>
>  try:
>while True:
>   chunk = stream_data.read(CHUNK_SIZE)
>   if not chunk: break
>   report_data.write(chunk.decode() if sys.version_info[0]
>   == 3 and getattr(report_data, 'mode', 'w')
> == 'w' else chunk)
>print report_data.getvalue()
> finally:
>report_data.close()
>stream_data.close()
>
> If this doesn't work, please provide the complete report definition used
> and any error message received along with your clientCustomerID. Please use 
> *Reply
> privately to author* when responding.
>
> Regards,
> Shwetha, 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 a topic in the
> Google Groups "AdWords API Forum" group.
> To unsubscribe from this topic, visit
> https://groups.google.com/d/topic/adwords-api/Jmbqifyr_Ro/unsubscribe.
> To unsubscribe from this group and all its topics, 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/7dd4adad-b8bd-4825-8639-5bef60ccd42c%40googlegroups.com
> <https://groups.google.com/d/msgid/adwords-api/7dd4adad-b8bd-4825-8639-5bef60ccd42c%40googlegroups.com?utm_medium=email_source=footer>
> .
> For more options, visit https://groups.google.com/d/optout.
>
-- 
Best regards,

Tejas Manohar

-- 
-- 
=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~
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/CAJU0XY4CZmeSFtXWnm-q3yEJg_n7m9N6TUuNPR0Z-UHKsyWQ4A%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

AdWords API Python - Internal Error or Parsing Error

[tejas]

See code with commented errors here- 
https://gist.github.com/tejasmanohar/bff2fe3360673a823d31484a130d4bd8 


We're seeing this error consistently (every single run) for one customer 
when fetching their Campaign Performance Reports. We stream 1 report per 
campaign so that we can filter from the campaign's start time onwards. I 
feel as though both errors are from the same source and the CSV parsing one 
is just occurring because some sort of non-CSV error is returned.

Could it be a load issue? How should we proceed? Given an email address of 
someone from the AdWords API team, I can send over additional information 
about the customer / request that's failing to narrow things down.

-- 
-- 
=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~
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/522f3d3c-cde1-47cc-8a61-b11328cf5052%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Retrieve account creation date

[Tejas Manohar]

> Please note that if this value has been changed after campaign creation,
this will no longer indicate the date on which the campaign was created.

What value? Shouldn't StartDate be immutable?

On Fri, Jun 24, 2016 at 1:30 PM 'Shwetha Vastrad (AdWords API Team)' via
AdWords API Forum <adwords-api@googlegroups.com> wrote:

> Hi Tejas,
>
> You could query for StartDate
> <https://developers.google.com/adwords/api/docs/appendix/reports/campaign-performance-report#startdate>
>  in
> the Campaign Performance Report
> <https://developers.google.com/adwords/api/docs/appendix/reports/campaign-performance-report>.
> When you add a campaign
> <https://developers.google.com/adwords/api/docs/reference/v201605/CampaignService.Campaign#startdate>,
> this field defaults to the current day in the parent account's local
> timezone. Please note that if this value has been changed after campaign
> creation, this will no longer indicate the date on which the campaign was
> created.
>
> Regards,
> Shwetha, 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 a topic in the
> Google Groups "AdWords API Forum" group.
> To unsubscribe from this topic, visit
> https://groups.google.com/d/topic/adwords-api/cynjFINbqao/unsubscribe.
> To unsubscribe from this group and all its topics, 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/a3d19dae-3608-4b41-90d7-cf34cbaa82dd%40googlegroups.com
> <https://groups.google.com/d/msgid/adwords-api/a3d19dae-3608-4b41-90d7-cf34cbaa82dd%40googlegroups.com?utm_medium=email_source=footer>
> .
> For more options, visit https://groups.google.com/d/optout.
>
-- 
Best regards,

Tejas Manohar

-- 
-- 
=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~
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/CAJU0XY4PpKxGH-aLA-20BtbQjBEoDcFQvc%3D84fe87sRTGX%3DjGg%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: Retrieve account creation date

[tejas]

If it's not possible to get the account created date, is it possible to get 
the creation date of a campaign or ad? I could just make the report fetch 
data after that date for each ad.

On Friday, June 24, 2016 at 12:59:00 PM UTC-7, te...@segment.com wrote:
>
> Awesome!! My bad. I was confused initially how that could be represented 
> as a single value for a DateRange but it makes sense now.
>
> On Friday, June 24, 2016 at 12:10:54 PM UTC-7, Shwetha Vastrad (AdWords 
> API Team) wrote:
>>
>> Hi Tejas,
>>
>> Yes, if you add the field "Date 
>> <https://developers.google.com/adwords/api/docs/appendix/reports/all-reports#date>"
>>  
>> in the report query, the report data will be segmented by day within the 
>> given DateRange. The field "HourOfDay 
>> <https://developers.google.com/adwords/api/docs/appendix/reports/all-reports#hourofday>"
>>  
>> will segment the report based on the time on a given day if used along with 
>> the "Date" field. Please note that these fields will not be available in 
>> all report types and may be incompatible with other fields. For a more 
>> detailed description of report types and available fields, please refer 
>> this document 
>> <https://developers.google.com/adwords/api/docs/appendix/reports>. 
>>
>> An example query to get campaign performance for last week would look 
>> like this:
>> SELECT Date, HourOfDay, CampaignName, Impressions, Cost FROM 
>> CAMPAIGN_PERFORMANCE_REPORT DURING LAST_WEEK;
>>
>> Regards,
>> Shwetha, 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/ed4d358f-dbff-4aeb-8c9e-3262355ec008%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Retrieve account creation date

[tejas]

Awesome!! My bad. I was confused initially how that could be represented as 
a single value for a DateRange but it makes sense now.

On Friday, June 24, 2016 at 12:10:54 PM UTC-7, Shwetha Vastrad (AdWords API 
Team) wrote:
>
> Hi Tejas,
>
> Yes, if you add the field "Date 
> <https://developers.google.com/adwords/api/docs/appendix/reports/all-reports#date>"
>  
> in the report query, the report data will be segmented by day within the 
> given DateRange. The field "HourOfDay 
> <https://developers.google.com/adwords/api/docs/appendix/reports/all-reports#hourofday>"
>  
> will segment the report based on the time on a given day if used along with 
> the "Date" field. Please note that these fields will not be available in 
> all report types and may be incompatible with other fields. For a more 
> detailed description of report types and available fields, please refer 
> this document 
> <https://developers.google.com/adwords/api/docs/appendix/reports>. 
>
> An example query to get campaign performance for last week would look like 
> this:
> SELECT Date, HourOfDay, CampaignName, Impressions, Cost FROM 
> CAMPAIGN_PERFORMANCE_REPORT DURING LAST_WEEK;
>
> Regards,
> Shwetha, 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/950d3c8a-8f3c-427a-b1e8-79eacdcae7a2%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Retrieve account creation date

[tejas]

Hm, sorry- would you show an example query? Are you saying it's possible to 
get day-by-day data over a report using a multi-day DateRange? Or, are you 
saying to create multiple reports each with single-day ranges (what I'm 
doing now). If the former (multiple day breakdowns in 1 report), is there a 
way to do the same thing for hours within a day?

On Friday, June 24, 2016 at 6:57:30 AM UTC-7, Shwetha Vastrad (AdWords API 
Team) wrote:
>
> Hi,
>
> For the first question, I'm afraid that's the only workaround I could 
> think of using the API. 
>
> For the second one, you can segment 
> 
>  your 
> reports by Date 
> 
>  and 
> set the required DateRange in the report query to get the day-by-day data 
> in that range. You can also query for HourOfDay 
> 
>  in 
> some reports to segment the report further.
>
> Regards,
> Shwetha, 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/19b80d17-7938-4e6f-a66f-bd8ea160bae3%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Retrieve account creation date

[tejas]

Hi Shwetha,

Gotcha. That's unfortunate. Finding the account creation date via the UI is 
only viable if this is your own account- not for applications. Are you 
suggesting to find the creation date of the account via the *Date* field of 
the response of Account Performance Report? Not the best thing in the 
world, but I suppose that could work.

Also, is there a way to retrieve a single report that returns data for 
multiple time increments within a certain date range (e.g. every day 
separately within 6/20 - 6/23)? This is a common use case and one provided 
by Facebook Ads API. For example, if you want to get day-by-day data over a 
year, it seems you have to send a report per day.

On Thursday, June 23, 2016 at 3:09:24 PM UTC-7, Shwetha Vastrad (AdWords 
API Team) wrote:
>
> Hi Tejas,
>
> I'm afraid there is no field to provide the date on which the account was 
> created. You could use the Account Performance Report 
> <https://developers.google.com/adwords/api/docs/appendix/reports/account-performance-report>
>  as 
> suggested in the referred post. Be sure to query the report with the 
> includeZeroImpressions 
> header 
> <https://developers.google.com/adwords/api/docs/guides/reporting#request-headers>
>  set 
> to true so that you get data from the date on which the account was created 
> rather than the date on which the account started serving ads. Similarly, 
> you can find the account creation date by selecting *All time* in the 
> date selector available in the top right corner in the AdWords account tab. 
>
> Regards,
> Shwetha, 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/f5601084-e9d6-48d5-80db-ea99258b135f%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Retrieve account creation date

[tejas]

I've been trying to find the created date of the AdWords account so that I 
can fetch reports (using min / max date ranges) in increments so that users 
can see how stats grew over time. Without knowing the creation time of an 
account, I just have to set an arbitrary min time for the first increment. 
I saw this thread 
(https://groups.google.com/forum/#!topic/adwords-api/32TomWaxyd4) and it 
asked for a use case so I thought I'd repost because it's quite old. Do you 
have any recommendations for this use case?

-- 
-- 
=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~
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/277bbee5-c6ac-4d9c-b45a-67884b1a6506%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

How do you find available customer IDs?

[tejas]

What's the recommended approach to finding available customer IDs? I saw this 
example 
,
 
which seemed to do what I'm intending, but it keeps erroring 
"AuthenticationError.CLIENT_CUSTOMER_ID_IS_REQUIRED", which sounds to me 
like the chicken-and-egg problem (e.g. how to find customer IDs without a 
customer ID to start)?

-- 
-- 
=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~
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/5379cede-c902-43bd-8b02-e6eb0b434771%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.