Re: SOAP XML error for Chinese Names in ManagedCustomerService

[maxSonic Sun]

Hi Mark,

On my server machine, the locale is
ubuntu@ip-10-0-24-250:~$ locale -a
C
C.UTF-8
en_US.utf8
POSIX

But I still have the problem. The system I have is ubuntu 14.04 server on 
aws. That should not be the ANSII encoding problem. 
*And by the way, my problem is not caused by the logger as you pointed out 
in the previous post, it is caused by the decoding of the xml. *The 
scenario you pointed out happened nowhere on my machine.

As you can see, is a SAX parser problem.







On Saturday, February 20, 2016 at 12:44:58 AM UTC+8, Mark Saniscalchi wrote:
>
> Hello Sonic,
>
> Sorry for the delay. If you look to my initial response, I did run and 
> successfully retrieve an account name containing utf-8 characters using the 
> get_account_hierarchy.py example in v201509 using Python 2. This was on a 
> machine where the default encoding is utf-8. I provided the code above as a 
> potential work-around, but if that still fails to work, I would suggest 
> modifying the default encoding used by your VM to utf-8.
>
> You may recall earlier that I was able to replicate your issue on a VM 
> using ANSII encoding. I was also able to resolve the problem on that VM by 
> modifying the default encoding to utf-8. The suds-jurko library doesn't 
> seem to state this as a requirement, but it doesn't seem to handle utf-8 
> characters well otherwise. Going forward, we'll be suggesting in our 
> documentation that setting the default encoding to utf-8 is a requirement.
>
> Regards,
> Mark
>
> On Friday, February 19, 2016 at 9:42:16 AM UTC-5, maxSonic Sun wrote:
>>
>> Hi Mark, 
>>
>> Any update?
>>
>> Best Regards,
>> Sonic
>>
>> On Saturday, February 6, 2016 at 1:08:31 AM UTC+8, Mark Saniscalchi wrote:
>>>
>>> Hello Sonic,
>>>
>>> That looks correct, so you are using the right version of suds-jurko at 
>>> least.
>>>
>>> On my workstation, I created a campaign with the name that you're having 
>>> issues parsing and ran the get_campaigns.py example. I ran (sort of) 
>>> without issues:
>>>
>>> INFO:oauth2client.client:Refreshing access_token
 DEBUG:suds.transport.http:opening (
 https://adwords.google.com/api/adwords/cm/v201509/CampaignService?wsdl)
 DEBUG:suds.transport.http:sending:
 URL: https://adwords.google.com/api/adwords/cm/v201509/CampaignService
 HEADERS: {'Soapaction': '""', 'SOAPAction': '""', 'Content-Type': 
 'text/xml; charset=utf-8', 'Content-type': 'text/xml; charset=utf-8', 
 'Authorization': u'REDACTED'}
 MESSAGE:
 http://schemas.xmlsoap.org/soap/envelope/; xmlns:ns1="
 https://adwords.google.com/api/adwords/cm/v201509; xmlns:xsi="
 http://www.w3.org/2001/XMLSchema-instance; xmlns:tns="
 https://adwords.google.com/api/adwords/cm/v201509; xmlns:SOAP-ENV="
 http://schemas.xmlsoap.org/soap/envelope/
 ">REDACTEDREDACTEDREDACTEDfalsefalseIdNameStatus0100
 Traceback (most recent call last):
   File "/usr/local/lib/python2.7/logging/__init__.py", line 859, in emit
 msg = self.format(record)
   File "/usr/local/lib/python2.7/logging/__init__.py", line 732, in 
 format
 return fmt.format(record)
   File "/usr/local/lib/python2.7/logging/__init__.py", line 471, in 
 format
 record.message = record.getMessage()
   File "/usr/local/lib/python2.7/logging/__init__.py", line 335, in 
 getMessage
 msg = msg % self.args
   File "/usr/local/lib/python2.7/dist-packages/suds/__init__.py", line 
 168, in 
 __str__ = lambda x: unicode(x).encode('utf-8')
   File 
 "/usr/local/lib/python2.7/dist-packages/suds/transport/__init__.py", line 
 96, in __unicode__
 %s""" % (self.code, self.headers, self.message)
 UnicodeDecodeError: 'ascii' codec can't decode byte 0xe4 in position 
 577: ordinal not in range(128)
 Logged from file http.py, line 89
 Campaign with id '374649914', name '15-abc-1-mmep-中国－IOS', and status 
 'ENABLED' was found.
>>>
>>>
>>> The error you're seeing there is a known issue that the suds logger has 
>>> with unicode characters, but it doesn't prevent the sample from completing. 
>>> As you can see, the Campaign's name can be retrieved and printed without 
>>> issues. This definitely seems like an issue specific to the environment the 
>>> code is run on. I went a step further and ran this on a separate VM 
>>> instance, and was able to reproduce it in that case.
>>>
>>> The workstation has its default character encoding set to utf-8 and the 
>>> VM has it set to ANSIX3.4-1968, which is probably related. I think suds 
>>> might have some flaky behavior here depending on the environment used. In 
>>> the meantime, you can avoid this error by encoding the output of string 
>>> fields such as:
>>>
>>> # Display results.
>>> if 'entries' in page:
>>>   for campaign in page['entries']:
>>> print ('Campaign with 

Re: Customer Match Bulk uploads at Scale

['Yin Niu' via AdWords API Forum]

Hello, 

You can process up to 10,000 userlists in a single mutate 

 call 
and can add/remove a maximum of 10,000 email addresses for each user list.  

Thanks,
Yin, 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/c6e448e5-02aa-40f1-9562-a54388a4634d%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Remarketing List Error

['Josh Radcliff (AdWords API Team)' via AdWords API Forum]

Hi,

Thanks for the quick response. From what I and others have seen today, the 
new issue you described only occurs with ExpressionRuleUserList 

 objects 
created via the API. For DateSpecificRuleUserList 

 objects 
created via the API, the checkbox remains checked after saving.

I've passed this on to the team working on the user interface and will let 
you know as soon as I have more info.

Thanks,
Josh, AdWords API Team

On Friday, February 19, 2016 at 3:02:03 PM UTC-5, Akli Reguig wrote:
>
> Hi Josh,
> Thank you for the update.  
> The error message is gone now.  
> I can update all the properties except the 'include past users',  i can 
> save the update but when i get back to the list the box is unchecked... :-( 
>
> Envoyé depuis mon téléphone. 
> Le 19 févr. 2016 8:58 PM, "'Josh Radcliff (AdWords API Team)' via AdWords 
> API Forum"  a écrit :
>
>> Hi,
>>
>> The fix for the user interface *Too few elements in the collection* error 
>> is now in place. Please let me know if you still encounter this error when 
>> checking the *Include past users who match these rules* box.
>>
>> Cheers,
>> Josh, AdWords API Team
>>
>> On Friday, February 12, 2016 at 8:59:29 AM UTC-5, Josh Radcliff (AdWords 
>> API Team) wrote:
>>>
>>> Hi,
>>>
>>> Unfortunately, rule based lists created in the user interface are not 
>>> compatible with the AdWords API -- please see this section of the rule 
>>> based user list guide 
>>> 
>>> .
>>>
>>> The user interface team is still working on a fix for this issue. I'll 
>>> update this thread as soon as I have more information.
>>>
>>> Thanks,
>>> Josh, AdWords API Team
>>>
>>> On Wednesday, February 10, 2016 at 6:23:22 AM UTC-5, Akli Reguig wrote:

 Hi, 
 Ok i understand. 
 The work around you are providing is not possible for us... 

 By the way, the "bug" is not only on that property, but i am having the 
 same issue when i try to change the value of other properties like 
 Membership 
 duration or Membership status.

 I have another question linked to a work around i thought about: 
 Creating the list using the UI and adding the rules via the api using 
 its ID and the Operator SET. 
 I tried this and i have an error saying that the list type is not 
 compatible. What type should i use in the API to update the rules in a 
 remarketing list (Website rule based) created via the UI  ??

 Thanks.

 Le mercredi 10 février 2016 00:23:36 UTC+1, Josh Radcliff (AdWords API 
 Team) a écrit :
>
> Hi,
>
> My team does not maintain the AdWords user interface, but I passed 
> this along to the team that does and they are looking into a fix for 
> this. 
> In the meantime, a work around is to create and maintain the user lists 
> via 
> the user interface.
>
> Thanks,
> Josh, AdWords API Team
>
> On Tuesday, February 9, 2016 at 3:58:56 AM UTC-5, Akli Reguig wrote:
>>
>> Hi Josh, 
>> Thank you for answering. 
>> You mean the issue is not handled by your team (api) ?, cuz i reached 
>> the support and they said that you (your team) were in charge of that 
>> issue. 
>> Otherwise, i was wondering, if you or the support (or someone) could 
>> enable that property on my remarketing lists via your backoffice tools. 
>>
>> Thanks. 
>>
>> Le jeudi 4 février 2016 20:19:36 UTC+1, Josh Radcliff (AdWords API 
>> Team) a écrit :
>>>
>>> Hi,
>>>
>>> I've just asked the user interface team for an update. I'll post 
>>> back as soon as I have more information.
>>>
>>> Thanks,
>>> Josh, AdWords API Team
>>>
>>> On Thursday, February 4, 2016 at 9:05:27 AM UTC-5, Akli Reguig wrote:

 Hi, 

 I have the same issue with the same error message. 
 Any update from the team ? 

 Le vendredi 11 septembre 2015 15:44:23 UTC+2, Josh Radcliff 
 (AdWords API Team) a écrit :
>
> Hi,
>
> I've reported the issue in the user interface. I'll post back here 
> when I have an update.
>
> Thanks,
> Josh, AdWords API Team
>
> On Friday, September 11, 2015 at 12:51:28 AM UTC-4, Nir Keren 
> wrote:
>>
>> I am getting the same error when trying to save a list that was 
>> created by the API,
>> "Too few elements in the collection."
>>
>> Any updates ?
>>
>>
>>
>> On Thursday, March 19, 2015 at 

Customer Match Bulk uploads at Scale

[leonardmel via AdWords API Forum]

Are any outside API's  able to support the bulk upload of customer match 
email lists at this level?  400-500 customer lists  to bulk update them on 
a weekly basis?

-- 
-- 
=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~
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/46e770d0-1751-4d28-bfb1-ddd9c37c23a0%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Ad group type and other questions API

[Tex Russky]

According to the AdWords doc 
(https://support.google.com/adwords/answer/3481092?hl=en) an ad group can 
only have a single type of video ad format, in_stream or in_display. This 
constraint is enforced during creation on the AdWords Web page by forcing 
the user to specify which ad format it will be. At the very least reporting 
this for an ad_group would be very nice since many of our customers want to 
see various cost metrics separated for in-stream and in-display. Since no 
such attribute is exposed on the ad_group level it means we have to inspect 
ads under an ad group to discover which ad format is used by a given ad 
group. Adds complexity and degrades performance.
To create an ad group via the API is also would be nice if this were 
directly settable instead of relying on the fragile sequence exposed by the 
web UI.

On Friday, February 19, 2016 at 4:03:06 PM UTC-5, Josh Radcliff (AdWords 
API Team) wrote:
>
> Hi,
>
> Sorry - my mistake. I somehow missed the *Ad group type* column in the 
> user interface when I looked for it back on January 22.
>
> Could you provide some details as to why you need this column to be 
> visible and/or settable via the AdWords API? For example, is there certain 
> functionality you want to use that is not available to you because *Ad 
> group type* is not available?
>
> Thanks,
> Josh, AdWords API Team
>
> On Friday, February 19, 2016 at 12:22:09 PM UTC-5, Tex Russky wrote:
>>
>> That's not true. In the AdWords UI go to the "Ad Groups" tab, select 
>> "Columns", then "Attributes". AdGroupType is the last attribute listed.
>> It's also available if you download a csv.
>> It would be very nice if it were added to the api.
>>
>> On Thursday, January 22, 2015 at 5:24:45 PM UTC-5, Josh Radcliff (AdWords 
>> API Team) wrote:
>>>
>>> Hi Nick,
>>>
>>> The AdWords API does not have the concept of *ad group type* - that 
>>> appears to be an AdWords Editor feature. I don't see anything related to ad 
>>> group type in the AdWords UI either.
>>>
>>> The *targeting optimization* setting you mentioned is configurable in 
>>> the AdWords API by adding or removing an ExplorerAutoOptimizerSetting 
>>> 
>>>  in 
>>> your *AdGroup* object's settings collection 
>>> .
>>>  
>>> You can further configure the *ExplorerAutoOptimizerSetting* by setting 
>>> its optIn 
>>> 
>>>  field 
>>> as follows:
>>>
>>>- false -> This is equivalent to *Conservative* targeting in the UI
>>>- true -> This is equivalent to *Aggressive* targeting in the UI 
>>>(enabling *Display Campaign Optimizer*)
>>>
>>> Regarding finding objects in the API that correspond to AdWords UI 
>>> objects, the API services are organized by object type. For example, if you 
>>> are looking for attributes that you set on the *Campaigns* tab in the 
>>> UI, chances are they are on the Campaign object 
>>> 
>>>  in 
>>> the CampaignService 
>>> .
>>>  
>>> Similarly, *Ad groups* tab settings are mostly in the *AdGroupService*.
>>>
>>> Another good resource is the set of guides we have under Developer's 
>>> Guide . These are 
>>> grouped by Campaign, Ads, Reporting, etc., and each guide will contain 
>>> links to the relevant services and object types for the features covered in 
>>> the guide.
>>>
>>> Best regards,
>>> Josh, AdWords API Team
>>>
>>> On Thursday, January 22, 2015 at 5:10:20 AM UTC-5, Nikola Jordanovski 
>>> wrote:

 Hello, 
 so i am given a task to replicate the ad-words editor, and i am having 
 trouble making the replica using the API, because some of the features are 
 very hard to find.
 Can you help me with something?
 So i am trying to set the :

 *Ad group type -> Default*

 *Targeting optimization -> Disabled*


 but can't find the appropriate API methods to do so.

 Can you give me a hand?
 Also what is the best practice for finding the wanted functions , 
 because the API is endless :D


 Thank you,
 Nick 
  

>>>

-- 
-- 
=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~
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

Re: Ad group type and other questions API

['Josh Radcliff (AdWords API Team)' via AdWords API Forum]

Hi,

Sorry - my mistake. I somehow missed the *Ad group type* column in the user 
interface when I looked for it back on January 22.

Could you provide some details as to why you need this column to be visible 
and/or settable via the AdWords API? For example, is there certain 
functionality you want to use that is not available to you because *Ad 
group type* is not available?

Thanks,
Josh, AdWords API Team

On Friday, February 19, 2016 at 12:22:09 PM UTC-5, Tex Russky wrote:
>
> That's not true. In the AdWords UI go to the "Ad Groups" tab, select 
> "Columns", then "Attributes". AdGroupType is the last attribute listed.
> It's also available if you download a csv.
> It would be very nice if it were added to the api.
>
> On Thursday, January 22, 2015 at 5:24:45 PM UTC-5, Josh Radcliff (AdWords 
> API Team) wrote:
>>
>> Hi Nick,
>>
>> The AdWords API does not have the concept of *ad group type* - that 
>> appears to be an AdWords Editor feature. I don't see anything related to ad 
>> group type in the AdWords UI either.
>>
>> The *targeting optimization* setting you mentioned is configurable in 
>> the AdWords API by adding or removing an ExplorerAutoOptimizerSetting 
>> 
>>  in 
>> your *AdGroup* object's settings collection 
>> .
>>  
>> You can further configure the *ExplorerAutoOptimizerSetting* by setting 
>> its optIn 
>> 
>>  field 
>> as follows:
>>
>>- false -> This is equivalent to *Conservative* targeting in the UI
>>- true -> This is equivalent to *Aggressive* targeting in the UI 
>>(enabling *Display Campaign Optimizer*)
>>
>> Regarding finding objects in the API that correspond to AdWords UI 
>> objects, the API services are organized by object type. For example, if you 
>> are looking for attributes that you set on the *Campaigns* tab in the 
>> UI, chances are they are on the Campaign object 
>> 
>>  in 
>> the CampaignService 
>> .
>>  
>> Similarly, *Ad groups* tab settings are mostly in the *AdGroupService*.
>>
>> Another good resource is the set of guides we have under Developer's 
>> Guide . These are 
>> grouped by Campaign, Ads, Reporting, etc., and each guide will contain 
>> links to the relevant services and object types for the features covered in 
>> the guide.
>>
>> Best regards,
>> Josh, AdWords API Team
>>
>> On Thursday, January 22, 2015 at 5:10:20 AM UTC-5, Nikola Jordanovski 
>> wrote:
>>>
>>> Hello, 
>>> so i am given a task to replicate the ad-words editor, and i am having 
>>> trouble making the replica using the API, because some of the features are 
>>> very hard to find.
>>> Can you help me with something?
>>> So i am trying to set the :
>>>
>>> *Ad group type -> Default*
>>>
>>> *Targeting optimization -> Disabled*
>>>
>>>
>>> but can't find the appropriate API methods to do so.
>>>
>>> Can you give me a hand?
>>> Also what is the best practice for finding the wanted functions , 
>>> because the API is endless :D
>>>
>>>
>>> Thank you,
>>> Nick 
>>>  
>>>
>>

-- 
-- 
=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~
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/f5477a5c-6d54-4864-8f61-bca8ceff3a5a%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Remarketing List Error

[Akli Reguig]

Hi Josh,
Thank you for the update.
The error message is gone now.
I can update all the properties except the 'include past users',  i can
save the update but when i get back to the list the box is unchecked... :-(

Envoyé depuis mon téléphone.
Le 19 févr. 2016 8:58 PM, "'Josh Radcliff (AdWords API Team)' via AdWords
API Forum"  a écrit :

> Hi,
>
> The fix for the user interface *Too few elements in the collection* error
> is now in place. Please let me know if you still encounter this error when
> checking the *Include past users who match these rules* box.
>
> Cheers,
> Josh, AdWords API Team
>
> On Friday, February 12, 2016 at 8:59:29 AM UTC-5, Josh Radcliff (AdWords
> API Team) wrote:
>>
>> Hi,
>>
>> Unfortunately, rule based lists created in the user interface are not
>> compatible with the AdWords API -- please see this section of the rule
>> based user list guide
>> 
>> .
>>
>> The user interface team is still working on a fix for this issue. I'll
>> update this thread as soon as I have more information.
>>
>> Thanks,
>> Josh, AdWords API Team
>>
>> On Wednesday, February 10, 2016 at 6:23:22 AM UTC-5, Akli Reguig wrote:
>>>
>>> Hi,
>>> Ok i understand.
>>> The work around you are providing is not possible for us...
>>>
>>> By the way, the "bug" is not only on that property, but i am having the
>>> same issue when i try to change the value of other properties like 
>>> Membership
>>> duration or Membership status.
>>>
>>> I have another question linked to a work around i thought about:
>>> Creating the list using the UI and adding the rules via the api using
>>> its ID and the Operator SET.
>>> I tried this and i have an error saying that the list type is not
>>> compatible. What type should i use in the API to update the rules in a
>>> remarketing list (Website rule based) created via the UI  ??
>>>
>>> Thanks.
>>>
>>> Le mercredi 10 février 2016 00:23:36 UTC+1, Josh Radcliff (AdWords API
>>> Team) a écrit :

 Hi,

 My team does not maintain the AdWords user interface, but I passed this
 along to the team that does and they are looking into a fix for this. In
 the meantime, a work around is to create and maintain the user lists via
 the user interface.

 Thanks,
 Josh, AdWords API Team

 On Tuesday, February 9, 2016 at 3:58:56 AM UTC-5, Akli Reguig wrote:
>
> Hi Josh,
> Thank you for answering.
> You mean the issue is not handled by your team (api) ?, cuz i reached
> the support and they said that you (your team) were in charge of that
> issue.
> Otherwise, i was wondering, if you or the support (or someone) could
> enable that property on my remarketing lists via your backoffice tools.
>
> Thanks.
>
> Le jeudi 4 février 2016 20:19:36 UTC+1, Josh Radcliff (AdWords API
> Team) a écrit :
>>
>> Hi,
>>
>> I've just asked the user interface team for an update. I'll post back
>> as soon as I have more information.
>>
>> Thanks,
>> Josh, AdWords API Team
>>
>> On Thursday, February 4, 2016 at 9:05:27 AM UTC-5, Akli Reguig wrote:
>>>
>>> Hi,
>>>
>>> I have the same issue with the same error message.
>>> Any update from the team ?
>>>
>>> Le vendredi 11 septembre 2015 15:44:23 UTC+2, Josh Radcliff (AdWords
>>> API Team) a écrit :

 Hi,

 I've reported the issue in the user interface. I'll post back here
 when I have an update.

 Thanks,
 Josh, AdWords API Team

 On Friday, September 11, 2015 at 12:51:28 AM UTC-4, Nir Keren wrote:
>
> I am getting the same error when trying to save a list that was
> created by the API,
> "Too few elements in the collection."
>
> Any updates ?
>
>
>
> On Thursday, March 19, 2015 at 12:29:38 AM UTC+2, Josh Radcliff
> (AdWords API Team) wrote:
>>
>> Hi,
>>
>> We're aware that there's some interest in exposing that option in
>> the API, but it's not yet available.
>>
>> Regarding the UI error, please contact AdWords Help via the *Contact
>> us* link in the Help Center
>> .
>>
>> Thanks,
>> Josh, AdWords API Team
>>
>> On Wednesday, March 18, 2015 at 9:13:38 AM UTC-4, nikhil khemani
>> wrote:
>>>
>>> I have some remarketing lists which were created using the
>>> AdWords API. I need the option "Include past users who match these 
>>> rules"
>>> to checked. The API does not have this option, and doing it on the 
>>> AdWords
>>> GUI I get the error "Too few 

Re: Remarketing List Error

['Josh Radcliff (AdWords API Team)' via AdWords API Forum]

Hi,

The fix for the user interface *Too few elements in the collection* error 
is now in place. Please let me know if you still encounter this error when 
checking the *Include past users who match these rules* box.

Cheers,
Josh, AdWords API Team

On Friday, February 12, 2016 at 8:59:29 AM UTC-5, Josh Radcliff (AdWords 
API Team) wrote:
>
> Hi,
>
> Unfortunately, rule based lists created in the user interface are not 
> compatible with the AdWords API -- please see this section of the rule 
> based user list guide 
> 
> .
>
> The user interface team is still working on a fix for this issue. I'll 
> update this thread as soon as I have more information.
>
> Thanks,
> Josh, AdWords API Team
>
> On Wednesday, February 10, 2016 at 6:23:22 AM UTC-5, Akli Reguig wrote:
>>
>> Hi, 
>> Ok i understand. 
>> The work around you are providing is not possible for us... 
>>
>> By the way, the "bug" is not only on that property, but i am having the 
>> same issue when i try to change the value of other properties like 
>> Membership 
>> duration or Membership status.
>>
>> I have another question linked to a work around i thought about: 
>> Creating the list using the UI and adding the rules via the api using its 
>> ID and the Operator SET. 
>> I tried this and i have an error saying that the list type is not 
>> compatible. What type should i use in the API to update the rules in a 
>> remarketing list (Website rule based) created via the UI  ??
>>
>> Thanks.
>>
>> Le mercredi 10 février 2016 00:23:36 UTC+1, Josh Radcliff (AdWords API 
>> Team) a écrit :
>>>
>>> Hi,
>>>
>>> My team does not maintain the AdWords user interface, but I passed this 
>>> along to the team that does and they are looking into a fix for this. In 
>>> the meantime, a work around is to create and maintain the user lists via 
>>> the user interface.
>>>
>>> Thanks,
>>> Josh, AdWords API Team
>>>
>>> On Tuesday, February 9, 2016 at 3:58:56 AM UTC-5, Akli Reguig wrote:

 Hi Josh, 
 Thank you for answering. 
 You mean the issue is not handled by your team (api) ?, cuz i reached 
 the support and they said that you (your team) were in charge of that 
 issue. 
 Otherwise, i was wondering, if you or the support (or someone) could 
 enable that property on my remarketing lists via your backoffice tools. 

 Thanks. 

 Le jeudi 4 février 2016 20:19:36 UTC+1, Josh Radcliff (AdWords API 
 Team) a écrit :
>
> Hi,
>
> I've just asked the user interface team for an update. I'll post back 
> as soon as I have more information.
>
> Thanks,
> Josh, AdWords API Team
>
> On Thursday, February 4, 2016 at 9:05:27 AM UTC-5, Akli Reguig wrote:
>>
>> Hi, 
>>
>> I have the same issue with the same error message. 
>> Any update from the team ? 
>>
>> Le vendredi 11 septembre 2015 15:44:23 UTC+2, Josh Radcliff (AdWords 
>> API Team) a écrit :
>>>
>>> Hi,
>>>
>>> I've reported the issue in the user interface. I'll post back here 
>>> when I have an update.
>>>
>>> Thanks,
>>> Josh, AdWords API Team
>>>
>>> On Friday, September 11, 2015 at 12:51:28 AM UTC-4, Nir Keren wrote:

 I am getting the same error when trying to save a list that was 
 created by the API,
 "Too few elements in the collection."

 Any updates ?



 On Thursday, March 19, 2015 at 12:29:38 AM UTC+2, Josh Radcliff 
 (AdWords API Team) wrote:
>
> Hi,
>
> We're aware that there's some interest in exposing that option in 
> the API, but it's not yet available.
>
> Regarding the UI error, please contact AdWords Help via the *Contact 
> us* link in the Help Center 
> .
>
> Thanks,
> Josh, AdWords API Team
>
> On Wednesday, March 18, 2015 at 9:13:38 AM UTC-4, nikhil khemani 
> wrote:
>>
>> I have some remarketing lists which were created using the 
>> AdWords API. I need the option "Include past users who match these 
>> rules" 
>> to checked. The API does not have this option, and doing it on the 
>> AdWords 
>> GUI I get the error "Too few elements in the collection."
>>
>

-- 
-- 
=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~
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 

Re: Ad group type and other questions API

[Tex Russky]

That's not true. In the AdWords UI go to the "Ad Groups" tab, select 
"Columns", then "Attributes". AdGroupType is the last attribute listed.
It's also available if you download a csv.
It would be very nice if it were added to the api.

On Thursday, January 22, 2015 at 5:24:45 PM UTC-5, Josh Radcliff (AdWords 
API Team) wrote:
>
> Hi Nick,
>
> The AdWords API does not have the concept of *ad group type* - that 
> appears to be an AdWords Editor feature. I don't see anything related to ad 
> group type in the AdWords UI either.
>
> The *targeting optimization* setting you mentioned is configurable in the 
> AdWords API by adding or removing an ExplorerAutoOptimizerSetting 
> 
>  in 
> your *AdGroup* object's settings collection 
> .
>  
> You can further configure the *ExplorerAutoOptimizerSetting* by setting 
> its optIn 
> 
>  field 
> as follows:
>
>- false -> This is equivalent to *Conservative* targeting in the UI
>- true -> This is equivalent to *Aggressive* targeting in the UI 
>(enabling *Display Campaign Optimizer*)
>
> Regarding finding objects in the API that correspond to AdWords UI 
> objects, the API services are organized by object type. For example, if you 
> are looking for attributes that you set on the *Campaigns* tab in the UI, 
> chances are they are on the Campaign object 
> 
>  in 
> the CampaignService 
> .
>  
> Similarly, *Ad groups* tab settings are mostly in the *AdGroupService*.
>
> Another good resource is the set of guides we have under Developer's Guide 
> . These are grouped by 
> Campaign, Ads, Reporting, etc., and each guide will contain links to the 
> relevant services and object types for the features covered in the guide.
>
> Best regards,
> Josh, AdWords API Team
>
> On Thursday, January 22, 2015 at 5:10:20 AM UTC-5, Nikola Jordanovski 
> wrote:
>>
>> Hello, 
>> so i am given a task to replicate the ad-words editor, and i am having 
>> trouble making the replica using the API, because some of the features are 
>> very hard to find.
>> Can you help me with something?
>> So i am trying to set the :
>>
>> *Ad group type -> Default*
>>
>> *Targeting optimization -> Disabled*
>>
>>
>> but can't find the appropriate API methods to do so.
>>
>> Can you give me a hand?
>> Also what is the best practice for finding the wanted functions , because 
>> the API is endless :D
>>
>>
>> Thank you,
>> Nick 
>>  
>>
>

-- 
-- 
=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~
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/3bbca7d8-cd58-421f-90b2-d3b5577140a9%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Google Analytics does not display aquisition devices correctly

['Umesh Dengale' via AdWords API Forum]

Hello,

This forum supports the AdWords API related cases. Above case is related to 
the Google Analytics. Please post your question to the Google Analytics 
forum .

Thanks,
Umesh, 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/d2ba1a15-8b8e-47cb-9cd4-70196a0381c6%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Internal API Error with TargetingIdeaService

['Anthony Madrigal' via AdWords API Forum]

Hello Jansen,

Could you please provide me with the SOAP request and response that 
resulted in this error so that I could further investigate it? Please send 
it through *reply privately to author.*

Thanks,
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/d789514b-d455-4b82-a0c2-becfb8850af8%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: AdGroupAd status incorrect?

[James]

Great,

Thank you very much for your help!

James

On Friday, February 19, 2016 at 5:35:42 PM UTC+1, Yin Niu wrote:
>
> Hi James, 
>
> That is expected behavior. API only returns the requested object's status, 
> not it's serving status (which is "not serving, because campaign is 
> paused") If they retrieve the campaign's status, they will get it back as 
> PAUSED.
>
> Say if you want to filter out these ads in a report, then you could write 
> an AWQL like "Select CampaignId, AdGroupId, AdId from AD_PERFORMANCE_REPORT 
> where CampaignStatus = ENABLED and AdGroupStatus=ENABLED and 
> AdStatus=ENABLED".
>
> Thanks,
> Yin, 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/ad33ec1f-a7cb-4233-9a08-c2028e68ce33%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: SOAP XML error for Chinese Names in ManagedCustomerService

[Mark Saniscalchi]

Hello Sonic,

Sorry for the delay. If you look to my initial response, I did run and 
successfully retrieve an account name containing utf-8 characters using the 
get_account_hierarchy.py example in v201509 using Python 2. This was on a 
machine where the default encoding is utf-8. I provided the code above as a 
potential work-around, but if that still fails to work, I would suggest 
modifying the default encoding used by your VM to utf-8.

You may recall earlier that I was able to replicate your issue on a VM 
using ANSII encoding. I was also able to resolve the problem on that VM by 
modifying the default encoding to utf-8. The suds-jurko library doesn't 
seem to state this as a requirement, but it doesn't seem to handle utf-8 
characters well otherwise. Going forward, we'll be suggesting in our 
documentation that setting the default encoding to utf-8 is a requirement.

Regards,
Mark

On Friday, February 19, 2016 at 9:42:16 AM UTC-5, maxSonic Sun wrote:
>
> Hi Mark, 
>
> Any update?
>
> Best Regards,
> Sonic
>
> On Saturday, February 6, 2016 at 1:08:31 AM UTC+8, Mark Saniscalchi wrote:
>>
>> Hello Sonic,
>>
>> That looks correct, so you are using the right version of suds-jurko at 
>> least.
>>
>> On my workstation, I created a campaign with the name that you're having 
>> issues parsing and ran the get_campaigns.py example. I ran (sort of) 
>> without issues:
>>
>> INFO:oauth2client.client:Refreshing access_token
>>> DEBUG:suds.transport.http:opening (
>>> https://adwords.google.com/api/adwords/cm/v201509/CampaignService?wsdl)
>>> DEBUG:suds.transport.http:sending:
>>> URL: https://adwords.google.com/api/adwords/cm/v201509/CampaignService
>>> HEADERS: {'Soapaction': '""', 'SOAPAction': '""', 'Content-Type': 
>>> 'text/xml; charset=utf-8', 'Content-type': 'text/xml; charset=utf-8', 
>>> 'Authorization': u'REDACTED'}
>>> MESSAGE:
>>> http://schemas.xmlsoap.org/soap/envelope/; xmlns:ns1="
>>> https://adwords.google.com/api/adwords/cm/v201509; xmlns:xsi="
>>> http://www.w3.org/2001/XMLSchema-instance; xmlns:tns="
>>> https://adwords.google.com/api/adwords/cm/v201509; xmlns:SOAP-ENV="
>>> http://schemas.xmlsoap.org/soap/envelope/
>>> ">REDACTEDREDACTEDREDACTEDfalsefalseIdNameStatus0100
>>> Traceback (most recent call last):
>>>   File "/usr/local/lib/python2.7/logging/__init__.py", line 859, in emit
>>> msg = self.format(record)
>>>   File "/usr/local/lib/python2.7/logging/__init__.py", line 732, in 
>>> format
>>> return fmt.format(record)
>>>   File "/usr/local/lib/python2.7/logging/__init__.py", line 471, in 
>>> format
>>> record.message = record.getMessage()
>>>   File "/usr/local/lib/python2.7/logging/__init__.py", line 335, in 
>>> getMessage
>>> msg = msg % self.args
>>>   File "/usr/local/lib/python2.7/dist-packages/suds/__init__.py", line 
>>> 168, in 
>>> __str__ = lambda x: unicode(x).encode('utf-8')
>>>   File 
>>> "/usr/local/lib/python2.7/dist-packages/suds/transport/__init__.py", line 
>>> 96, in __unicode__
>>> %s""" % (self.code, self.headers, self.message)
>>> UnicodeDecodeError: 'ascii' codec can't decode byte 0xe4 in position 
>>> 577: ordinal not in range(128)
>>> Logged from file http.py, line 89
>>> Campaign with id '374649914', name '15-abc-1-mmep-中国－IOS', and status 
>>> 'ENABLED' was found.
>>
>>
>> The error you're seeing there is a known issue that the suds logger has 
>> with unicode characters, but it doesn't prevent the sample from completing. 
>> As you can see, the Campaign's name can be retrieved and printed without 
>> issues. This definitely seems like an issue specific to the environment the 
>> code is run on. I went a step further and ran this on a separate VM 
>> instance, and was able to reproduce it in that case.
>>
>> The workstation has its default character encoding set to utf-8 and the 
>> VM has it set to ANSIX3.4-1968, which is probably related. I think suds 
>> might have some flaky behavior here depending on the environment used. In 
>> the meantime, you can avoid this error by encoding the output of string 
>> fields such as:
>>
>> # Display results.
>> if 'entries' in page:
>>   for campaign in page['entries']:
>> print ('Campaign with id \'%s\', name \'%s\', and status \'%s\' 
>> was '
>>'found.' % (campaign['id'], 
>> campaign['name'].encode('utf-8'),
>>campaign['status'].encode('utf-8')))
>>
>> I'll continue investigating this, as a better fix may need to come 
>> upstream from the suds library.
>>
>> Regards,
>> Mark
>>
>> On Monday, February 1, 2016 at 9:12:24 PM UTC-5, maxSonic Sun wrote:
>>>
>>> Hi Mark,
>>>
>>> Here is the version:
>>> __version__ = "0.6"
>>> __build__ = ""
>>>
>>> Best Regards
>>> Sonic Sun
>>>
>>> On Monday, February 1, 2016 at 11:32:44 PM UTC+8, Mark Saniscalchi wrote:

 Hello Sonic,

 I'd just like to confirm, could you tell me what the version number is 
 in the following file:


 

Re: AdGroupAd status incorrect?

['Yin Niu' via AdWords API Forum]

Hi James, 

That is expected behavior. API only returns the requested object's status, 
not it's serving status (which is "not serving, because campaign is 
paused") If they retrieve the campaign's status, they will get it back as 
PAUSED.

Say if you want to filter out these ads in a report, then you could write 
an AWQL like "Select CampaignId, AdGroupId, AdId from AD_PERFORMANCE_REPORT 
where CampaignStatus = ENABLED and AdGroupStatus=ENABLED and 
AdStatus=ENABLED".

Thanks,
Yin, 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/99d261b6-26f5-4cf7-ac4e-7bfc8ecae01a%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Internal API Error with TargetingIdeaService

[Jansen Brewster]

Hello,

I hadn't seen any recent results that approached this subject.

When using the TargetingIdeaService, ideaType KEYWORDS, requestType STATS, 
and searchParameter RelatedToQuerySearchParameter, an 
InternalApiError.UNEXPECTED_INTERNAL_API_ERROR is thrown consistently. The 
program follows the AdWords limits 
( https://developers.google.com/adwords/api/docs/appendix/limits?hl=en ) 
with each keyword <= 80 characters (including xml escaped unicode) and no 
more than 800 keywords per request. It also waits at least 30 seconds 
between each request. It depends on v201509 AdWords API. This is for a test 
account.

The program had worked fine before with workable results, but lately this 
is the only result given.

Any help would be appreciated.


-- 
-- 
=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~
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/0c5ae2f7-7076-4cef-8e58-6cde73b897b1%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: AdGroupAd status incorrect?

[James]

I haven't been able to check them all, but one example is the ad with ID 
8840406794 (adgroup ID 2336016314).

Thanks again,
J

On Friday, February 19, 2016 at 4:58:16 PM UTC+1, Yin Niu wrote:
>
> Hi James, 
>
> I see that in the response, all returned ads have "ENABLED" status. Could 
> you point out to me which ad that was return as "ENABLED" but has actual 
> status not set to "ENABLED"? 
>
> Thanks,
> Yin, 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/82f7f837-38bc-45ba-b4d3-ef41c95434a7%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: AdGroupAd status incorrect?

['Yin Niu' via AdWords API Forum]

Hi James, 

I see that in the response, all returned ads have "ENABLED" status. Could 
you point out to me which ad that was return as "ENABLED" but has actual 
status not set to "ENABLED"? 

Thanks,
Yin, 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/9cb1c86b-8165-4145-8353-7c53ca4d8af2%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: AdServingOptimizationStatus Question

['Yin Niu' via AdWords API Forum]

Hello, 

If it's optional, you don't have to set that value and send to AdWords. 
Your users don't have to set those values. If the values are not set, 
AdWords will set default values.

The campaign reference page 

 has 
detailed description about what default values are. Campaigns created by 
API are all feature campaigns. 

Thanks,
Yin, 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/e50ae21f-d8a1-4226-bbea-0f2fe1332a59%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: AdGroupAd status incorrect?

['Yin Niu' via AdWords API Forum]

Hi James, 

I can not reproduce your problem. Please send the SOAP request and response 
so that I can investigate further. 

Thanks,
Yin, 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/0430389b-2076-487e-a51b-882ba3e2ce30%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: SOAP XML error for Chinese Names in ManagedCustomerService

[maxSonic Sun]

Hi Mark, 

Any update?

Best Regards,
Sonic

On Saturday, February 6, 2016 at 1:08:31 AM UTC+8, Mark Saniscalchi wrote:
>
> Hello Sonic,
>
> That looks correct, so you are using the right version of suds-jurko at 
> least.
>
> On my workstation, I created a campaign with the name that you're having 
> issues parsing and ran the get_campaigns.py example. I ran (sort of) 
> without issues:
>
> INFO:oauth2client.client:Refreshing access_token
>> DEBUG:suds.transport.http:opening (
>> https://adwords.google.com/api/adwords/cm/v201509/CampaignService?wsdl)
>> DEBUG:suds.transport.http:sending:
>> URL: https://adwords.google.com/api/adwords/cm/v201509/CampaignService
>> HEADERS: {'Soapaction': '""', 'SOAPAction': '""', 'Content-Type': 
>> 'text/xml; charset=utf-8', 'Content-type': 'text/xml; charset=utf-8', 
>> 'Authorization': u'REDACTED'}
>> MESSAGE:
>> http://schemas.xmlsoap.org/soap/envelope/; xmlns:ns1="
>> https://adwords.google.com/api/adwords/cm/v201509; xmlns:xsi="
>> http://www.w3.org/2001/XMLSchema-instance; xmlns:tns="
>> https://adwords.google.com/api/adwords/cm/v201509; xmlns:SOAP-ENV="
>> http://schemas.xmlsoap.org/soap/envelope/
>> ">REDACTEDREDACTEDREDACTEDfalsefalseIdNameStatus0100
>> Traceback (most recent call last):
>>   File "/usr/local/lib/python2.7/logging/__init__.py", line 859, in emit
>> msg = self.format(record)
>>   File "/usr/local/lib/python2.7/logging/__init__.py", line 732, in format
>> return fmt.format(record)
>>   File "/usr/local/lib/python2.7/logging/__init__.py", line 471, in format
>> record.message = record.getMessage()
>>   File "/usr/local/lib/python2.7/logging/__init__.py", line 335, in 
>> getMessage
>> msg = msg % self.args
>>   File "/usr/local/lib/python2.7/dist-packages/suds/__init__.py", line 
>> 168, in 
>> __str__ = lambda x: unicode(x).encode('utf-8')
>>   File 
>> "/usr/local/lib/python2.7/dist-packages/suds/transport/__init__.py", line 
>> 96, in __unicode__
>> %s""" % (self.code, self.headers, self.message)
>> UnicodeDecodeError: 'ascii' codec can't decode byte 0xe4 in position 577: 
>> ordinal not in range(128)
>> Logged from file http.py, line 89
>> Campaign with id '374649914', name '15-abc-1-mmep-中国－IOS', and status 
>> 'ENABLED' was found.
>
>
> The error you're seeing there is a known issue that the suds logger has 
> with unicode characters, but it doesn't prevent the sample from completing. 
> As you can see, the Campaign's name can be retrieved and printed without 
> issues. This definitely seems like an issue specific to the environment the 
> code is run on. I went a step further and ran this on a separate VM 
> instance, and was able to reproduce it in that case.
>
> The workstation has its default character encoding set to utf-8 and the VM 
> has it set to ANSIX3.4-1968, which is probably related. I think suds might 
> have some flaky behavior here depending on the environment used. In the 
> meantime, you can avoid this error by encoding the output of string fields 
> such as:
>
> # Display results.
> if 'entries' in page:
>   for campaign in page['entries']:
> print ('Campaign with id \'%s\', name \'%s\', and status \'%s\' 
> was '
>'found.' % (campaign['id'], 
> campaign['name'].encode('utf-8'),
>campaign['status'].encode('utf-8')))
>
> I'll continue investigating this, as a better fix may need to come 
> upstream from the suds library.
>
> Regards,
> Mark
>
> On Monday, February 1, 2016 at 9:12:24 PM UTC-5, maxSonic Sun wrote:
>>
>> Hi Mark,
>>
>> Here is the version:
>> __version__ = "0.6"
>> __build__ = ""
>>
>> Best Regards
>> Sonic Sun
>>
>> On Monday, February 1, 2016 at 11:32:44 PM UTC+8, Mark Saniscalchi wrote:
>>>
>>> Hello Sonic,
>>>
>>> I'd just like to confirm, could you tell me what the version number is 
>>> in the following file:
>>>
>>>
>>> /project/apiservice/venvdocker/local/lib/python2.7/site-packages/suds/version.py
>>>
>>> Thanks,
>>> Mark
>>>
>>>
>>> On Monday, February 1, 2016 at 2:51:27 AM UTC-5, maxSonic Sun wrote:

 Hi,

 There is something weird here, I am able to parsed some other unicode 
 characters and also other accounts of my customer. I have listed all the 
 pip lib in my machine, I think I have installed all the lib correctly. By 
 the way, I didn't change any of the import in the py file, how can it be 
 changed to other libs if I do nothing in the lib?

 This issue is also happened in the Java lib for the same account of our 
 customer.

 After some debugging, it seems like there will be noway to parsed the 
 id like: 15-abc-1-mmep-中国－IOS. Please notice that the － is different from 
 -.

 Best Regards,
 Sonic Sun

 On Friday, January 22, 2016 at 4:39:42 AM UTC+8, Mark Saniscalchi wrote:
>
> Hello,
>
> We aren't able to replicate this issue with account names containing 
> unicode characters. In my case, I ran the 

Looking for Developer

[Jamie Turnbull]

I want to develop an Adwords API application to help manage customer 
accounts. Basically I want the application to:

Pull the customers Search Query Report in Google Analytics

Filter queries based on conditions including: Impressions, Clicks, CTR, 
Conversions, Cost-per-conversion, Bounce rate, Pages per session, Time on 
site.

For queries that don’t meet a threshold: add them as negative exact match 
keywords in the corresponding ad group in Google Adwords - and add a label 
to them. (For instance, this will be to add exact negatives to an ad group 
containing only phrase or broad match modified keywords)
For queries that do meet a threshold- add them as positive exact match 
keywords to the corresponding ad group (the one containing only the exact 
match keywords - and add labels to them. Or if no such ad group exists for 
exact match keywords, then create it – add keywords, and label them.

If anyone is available to take on this project, then I'm looking for a 
quotation.

Thanks,

Jamie

-- 
-- 
=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~
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/d989a3a8-89ba-4b96-b49e-90b16ee70b4e%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: While create image ad , throws ImageError.UNEXPECTED_SIZE

['Yin Niu' via AdWords API Forum]

Hello, 

Please send the SOAP response as well. 

Thanks,
Yin, 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/9b0daf9b-4e87-46fc-adc4-04eea0375827%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Google Analytics data in Search Query Performance Report

[Jamie Turnbull]

Dear David,


Did you ever come up with a solution to this problem? Even an API solution.

Interested to hear.

Thanks,

Jamie

On Wednesday, April 15, 2015 at 2:50:00 PM UTC+1, David Midgley wrote:
>
> Hi all
>
> Can I assume as the GA columns are not available in the search query 
> report it's impossible to get bounce rate, etc for a search query?
>
> I can see there is conversion data, which is great but it would be even 
> better to get GA data.
>
> If you're looking for a use case, I have a couple:
>
> 1. Search query addition: If a search query has a lower bounce rate, more 
> time on site, etc then the query will be updated to an exact match keyword
> 2. Negative addition: If a search query has a high bounce rate. less time 
> on site, etc the keyword will be suggested as a negative
>
> The reason why conversion on its own may not be good enough is if the site 
> has a low conversion rate or conversion tracking is not implemented. Even 
> if conversion tracking was implemented, the GA data would help raise the 
> confidence level for the decision.
>
> If anyone has found a workaround, let me know! A potential solution could 
> be to use the GA API but I'm hoping to avoid that.
>
> Cheers
>
> David
>

-- 
-- 
=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~
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/7bb456cd-90b3-4ff9-b7e9-66ea4f9d27da%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: AdGroupAd status incorrect?

[James]

Hi Yin,

Thanks for your super fast response.

I know that i have called the variable $adgroup, but I think this is 
actually the AdGroupAd object. (each of the page -> entries) 

I'm currently selecting the entry's status: 

AdGroupAdPage Object
(
[entries] => Array
(
[0] => *AdGroupAd Object*
(
[adGroupId] => 25347X
[ad] => ProductAd Object
(
[promotionLine] => 
[id] => 81178XX
[url] => 
[displayUrl] => 
[finalUrls] => www.google.com
[finalMobileUrls] => 
[finalAppUrls] => 
[trackingUrlTemplate] => 
[urlCustomParameters] => 
[devicePreference] => 
[AdType] => ProductAd
[_parameterMap:Ad:private] => Array
(
[Ad.Type] => AdType
)

)

[experimentData] => 
*[status] => ENABLED*
[approvalStatus] => UNCHECKED
[trademarks] => 
[disapprovalReasons] => 
[trademarkDisapproved] => 
[labels] => 
[forwardCompatibilityMap] => 
)

)

[totalNumEntries] => 1
[PageType] => AdGroupAdPage
[_parameterMap:Page:private] => Array
(
[Page.Type] => PageType
)

)



>From the AdGroupAd selector guide it looks like adGroupAd.status is 
accessed at entries->status



I've added a new predicate (
$selector->predicates[] = new Predicate('Status', 'EQUALS', 'ENABLED');

but I still get a lot of results where the status is enabled even though 
the ad, or adgroup or campaign or account are paused / disabled.

Thanks again for your help!
James


On Thursday, February 18, 2016 at 5:54:09 PM UTC+1, Yin Niu wrote:
>
> Hi James, 
>
> You are checking on AdGroup status instead of AdGroupAd status in your 
> code. In your selector, you can add a predicate where AdGroupAd.status == 
> "ENABLED" so that you don't have to loop through all results. 
>
> Thanks,
> Yin, 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/762da078-cff9-4e71-b1b7-ee83d57c6830%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.