MutateSharedSets method returns ResourceCountLimitExceededError wrapped in InternalError

[Dorian Kind]

Hi there,

lately we've noticed that calling the SharedSetService's MutateSharedSets 
method with a MutateSharedSetsRequest that would exceed the limit of 20 
Shared Sets per account sometimes doesn't throw the documented 
ResourceCountLimitExceededError directly, but wrapped inside an 
InternalError.

As an example, the MutateSharedSets request with the ID 
oajUG4YRvmyGj8Q1X5Pz5g returned the 
expected ResourceCountLimitExceededError.RESOURCE_LIMIT, whereas the 
request with ID 6r7V8LbRssgLqy9Ti_kwqQ resulted in an 
InternalError.INTERNAL_ERROR.

In the later case, the actual error is still available inside the errors 
field of the containing InternalError, but it's a bit more complicated to 
handle error responses that way.

Is this expected behavior? We only started seeing these instances a couple 
of weeks ago.

Thanks for any feedback & best regards,
Dorian

-- 
-- 
=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~
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 
"Google Ads API and AdWords 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/001845d0-7aae-4072-a8d7-6f7daac1c462n%40googlegroups.com.

Re: GoogleAds Auction Insight Metrics exist in API v11 now, but developer access denied

[Dorian Kind]

Hi Aryeh,

this thread piqued my interest when you mentioned that there is a process 
to request access to Auction Insight Metrics. Can any organization apply? 
If so, how?

Thanks & best regards,
Dorian

On Monday, 22 August 2022 at 18:42:19 UTC+2 adsapi wrote:

> Hi there,
>
> Thank you for getting back to us with your use case. I raised with my team 
> your request for availability of Auction Insight Metrics. This request is 
> subject to review. You may monitor our blog 
>  for 
> an update.
>
>
> Regards,
>
> [image: Google Logo] 
> Aryeh 
> Google Ads API Team 
>   
>
> ref:_00D1U1174p._5004Q2dlHFs:ref
>

-- 
-- 
=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~
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 
"Google Ads API and AdWords 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/cd690fec-a3e1-4903-9f36-0db7d17332e6n%40googlegroups.com.

Re: Alignment between API version upgrades and client libraries

[Dorian Kind]

Hi Nirmita,

I think there's a bit of a disconnect between what I'm trying to convey and 
the impulse of API advisors on this board to fix every issue operationally.

Fundamentally, I'm wondering why client libraries are updated *after* a new 
version of the Ads API is released instead of *simultaneously or even* 
*before*. Understanding this might help in dealing with the issues that pop 
up during the in-between period or at the very least reduce the resulting 
frustration. I am well aware that I can open issues on the library's GH 
page or just wait for a new version to be published—but again, this doesn't 
address the question.

I do appreciate the efforts to help, but I don't really see any insight to 
be gained from this thread.

Thanks & best regards,
Dorian 
On Monday, 9 May 2022 at 16:54:13 UTC+2 adsapi wrote:

> Hi Dorin,
>
> Thank you for reaching out to the Google Ads API support team.
>
> With regards to your concern, you need to wait for new feature. If you 
> have any further question for client library, you should seek further 
> assistance with the Python client library owners 
> , as they will be 
> able to help your code specific inquiry.
>
> Thanks,
> [image: Google Logo] 
> Nirmita 
> Google Ads API Team 
>   
>
> ref:_00D1U1174p._5004Q2aOPQ7:ref
>

-- 
-- 
=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~
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 
"Google Ads API and AdWords 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/46caa35d-c742-478c-bf52-d55912deb30an%40googlegroups.com.

Re: Alignment between API version upgrades and client libraries

[Dorian Kind]

Hi Jinky,

sure thing! Here's my issue 
, which was 
specifically about the AdTypeEnums. There's others, too, such as this one 
 about the 
missing AdvertisingChannelTypeEnum.

Best,
Dorian

On Friday, 6 May 2022 at 10:17:12 UTC+2 adsapi wrote:

> Hi Dorian,
>
> Thank you for the reply. I'm also a member of the Google Ads API team and 
> allow me to assist you here. Could you please provide the link of the 
> github ticket number that you raised so that we can discuss this to the 
> rest of my team?
>
> Best regards,
> [image: Google Logo] 
> Jinky 
> Google Ads API Team 
>   
>
> ref:_00D1U1174p._5004Q2aOPQ7:ref
>

-- 
-- 
=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~
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 
"Google Ads API and AdWords 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/59f1b840-2a49-44a9-878c-059699bea8f0n%40googlegroups.com.

Re: Alignment between API version upgrades and client libraries

[Dorian Kind]

Hi Ernie,

Thanks for your continued support. I do agree that further discussion will 
most likely not be fruitful.

> With this, I would suggest raising your concern and suggestion to this Github 
tracker  to know if 
there is a workaround with your current client library version or if there 
are any updates about the client library version that is compatible with 
the newest API version.

I did that, believe it or not. There was no workaround and the solution is 
to wait for a new version of the client library (which has been published 
since). 

Best,
Dorian

On Thursday, 5 May 2022 at 03:57:56 UTC+2 adsapi wrote:

> Hi Dorian,
>
> Thank you for providing more details to your concern.
>
> I understand that you are having an issue with your client library as the 
> new version seems not compatible with the new Google Ads API version. 
> However, this concern is client library related and our team would not be 
> able to provide further comments as it is outside of our scope already. 
> With this, I would suggest raising your concern and suggestion to this Github 
> tracker  to know if 
> there is a workaround with your current client library version or if there 
> are any updates about the client library version that is compatible with 
> the newest API version.
>
> Regards,
> [image: Google Logo] 
> Ernie John 
> Google Ads API Team 
>   
>
> ref:_00D1U1174p._5004Q2aOPQ7:ref
>

-- 
-- 
=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~
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 
"Google Ads API and AdWords 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/9d3dd382-a9b8-4802-b739-e182f6ebe9aen%40googlegroups.com.

Re: Alignment between API version upgrades and client libraries

[Dorian Kind]

Hi Jakeia,

I appreciate your continued support, but I don't really see how your answer 
relates to the issue I've described. I'm well aware that the client 
libraries will be updated at some point in order to ensure compatibility 
with the latest API version. What's less clear to me is what to do in the 
time period after the API upgrade but before the new libraries are 
released, where existing code—such as the example I've provided above—no 
longer works.

Naively I would assume that this situation could be avoided by *first* updating 
the client libraries and *afterwards *publishing a new version of the API. 
But of course I'm not privy to the inner workings of Google and there 
probably is a valid reason not to do so. It's just frustrating for us to 
experience broken builds without any recourse apart from waiting for a new 
client library version to be released...

Best,
Dorian

On Tuesday, 3 May 2022 at 22:52:59 UTC+2 adsapi wrote:

> Hello,
>
> Thanks for reaching out to the Google Ads API support. As said on this 
> blog  -”to use some of the v10.1 
> features, you will need to upgrade your client libraries 
>  and 
> client code. The updated client libraries and code examples will be 
> published next week” and as this blog published earlier on April 27, 2022.
>
> With this, it’s not one week yet. Please try again with v10.1 next week. 
> Hope it will be resolved. Let us know if you have any questions.
>
> Best regards,
> [image: Google Logo] 
> Jakeia Sabrina 
> Google Ads API Team  
>
> ref:_00D1U1174p._5004Q2aOPQ7:ref
>

-- 
-- 
=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~
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 
"Google Ads API and AdWords 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/d707f63f-db0f-4974-8ec7-2272ed5b550fn%40googlegroups.com.

Re: Alignment between API version upgrades and client libraries

[Dorian Kind]

Hi Yasar,

thanks for getting back. I'm not exactly sure how the depreciation date of 
v10 is relevant to this discussion. As for your request about examples for 
client library breakage, here's a simplified Python snippet that might be 
used for reporting:

client = google.ads.googleads.client.GoogleAdsClient(, 
, login_customer_id=)
service = client.get_service('GoogleAdsService')
response = service.search(customer_id=, query='SELECT 
ad_group_ad.ad.type FROM ad_group_ad')
for entry in response:
  print(client.enums.AdTypeEnum.AdType.Name(entry.ad_group_ad.ad.type_))

Using the latest version of the Python client library (15.1.1), *this code 
used to work fine with v10, but will break in v10.1* as the enum values of 
discovery ads are not known to the client library. I hope this illustrates 
the challenges we face with the new API version.

Best,
Dorian 
On Monday, 2 May 2022 at 10:33:52 UTC+2 adsapi wrote:

> Hi Dorian,
>
> Thanks for getting back to us.
>
> As per this *guide* 
> , 
> depreciation date is not provided in the v10 version yet and sunset date is 
> set for October/November 2022. We understand the client libraries take a 
> bit of time to get supported once a new API version is launched. Note that 
> the Google Ads API follows *semantic versioning*  
> where there is a major and a minor version. When a minor version is 
> released, the endpoint that is already in use will automatically be 
> updated. This will not cause your code to break. You can continue to use 
> your existing client libraries. However, could you confirm if your existing 
> client libraries for v10 version are broken and throwing any error? If so, 
> you may provide us with complete logs via reply to author privately, so 
> that I can raise it to my team.
>
> Regards,
> [image: Google Logo] 
> Yasar 
> Google Ads API Team 
>   
>
> ref:_00D1U1174p._5004Q2aOPQ7:ref
>

-- 
-- 
=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~
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 
"Google Ads API and AdWords 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/312b497c-4d34-40d2-9507-fac3d6c34201n%40googlegroups.com.

Re: AdTypeEnum Values Documented in Google Ads API Not Appearing

[Dorian Kind]

See https://github.com/googleads/google-ads-python/issues/626. These enums 
were introduced in v10.1 and the client libraries aren't yet updated.

On Friday, 29 April 2022 at 15:52:46 UTC+2 Elliot Partridge wrote:

> Hello there,
>
> I'm hoping that someone could shed light on the below; it seems that Enum 
> values (`DISCOVERY_MULTI_ASSET_AD = 35, DISCOVERY_CAROUSEL_AD = 36`) 
> documented 
> in the v10 API 
> 
>  
> are not appearing:
>
> ```
> ad_types = client.get_type('AdTypeEnum')
> values = set(ad_type.value for ad_type in ad_types.AdType) 
>
> print(values)
> >> {0, 1, 2, 3, 7, 8, 9, 10, 12, 13, 14, 15, 16, 17, 18, 19, 20, 21, 22, 
> 23, 24, 25, 26, 27, 29, 30, 31, 32, 33, 34}
> ```
>
> Thanks!
>

-- 
-- 
=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~
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 
"Google Ads API and AdWords 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/c950be9b-94d1-481a-b0ad-391fe3ecc132n%40googlegroups.com.

Re: Alignment between API version upgrades and client libraries

[Dorian Kind]

Hi Peter,

Thanks for your reply. I did reach out to the client library owners, and
they have also told me that it's standard practice for the libraries to
only include support for new API versions some time after those have been
deployed.

To be quite honest, I don't understand the approach–what's the upside of
publishing a new version of your API when consumers won't be able to use
it? Even more so when the upgrade has the potential to disrupt existing
workflows? And lastly, why not at least provide an option for API consumers
to stay on v10 instead of being auto-upgraded to v10.1 (which, again, is a
version they can't even make use of in the first place as the client
libraries have no support for it)?

Best,
Dorian

On Fri, 29 Apr 2022 at 09:27, Google Ads API Forum Advisor
 wrote:

> Hi Dorian,
>
> Thank you for your feedback on the enums being unavailable in the client
> libraries.
>
> However, while the blog
> <https://ads-developers.googleblog.com/2022/04/announcing-v101-of-google-ads-api.html>
> states that "*The updated client libraries and code examples will be
> published next week.*", I would also recommend reaching out to the client
> library owners of the ones you are using, for further insight or
> information on when specifically these would be available in their packages.
>
> Should you then continue to encounter issues with the new version even
> after the new client libraries are officially released, you may reach back
> to us privately with the logs so I can raise the issue to the rest of our
> support team.
>
> Best regards,
>
> [image: Google Logo]
> Peter Laurence
> Google Ads API Team
>
>
> ref:_00D1U1174p._5004Q2aOPQ7:ref
>


-- 
Dorian Kind
Director Data & Technologies

Webrepublic AG
Phone: +41 44 542 90 64 <+41-44-542-90-64> | Mobile: +41 78 611 91 95
<+41-78-611-91-95>

dorian.k...@webrepublic.com

https://webrepublic.com/

Google has announced that Universal Analytics will be replaced with Google
Analytics 4 next year. Learn about
<https://webrepublic.com/en/news/blog/posts/update-ga4?utm_source=email_medium=organic_campaign=blog_content=google-analytics-4>
the important take-aways and recommendations for action.

-- 
-- 
=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~
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 
"Google Ads API and AdWords 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/CAHHj1zBnuaFGEjqw7JcEwTAud7v5Zr-jNZZdn5NG6jx8bJxwJA%40mail.gmail.com.

Alignment between API version upgrades and client libraries

[Dorian Kind]

Hi,

yesterday, version 10.1 of the Ads API was released 
,
 
adding support for discovery campaigns. While this feature is very helpful, 
to me it appears that the coordination with the client library owners 
wasn't ideal in this case because the new enum values (e.g. 
for AdvertisingChannelTypeEnum) are not yet included in the protobuf files. 
See this issue  in 
the PHP client library or this one 
 in the Python 
client library.
You could argue that introducing new enum values in API responses isn't a 
breaking change in a strict sense, but our jobs are now failing 
nevertheless.

The migration from the Adwords API to the Ads API is already putting quite 
a burden on developer teams—it'd be much appreciated if new features were 
introduced with a new major version.

Thanks and best regards,
Dorian

-- 
-- 
=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~
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 
"Google Ads API and AdWords 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/83e7dc96-03ae-4bed-889d-2ab7c9e230e3n%40googlegroups.com.

Re: `customer_label` returning labels that don't exist in `label`

[Dorian Kind]

Hi Peter,

thanks for reaching out. I've worded this issue terribly, apologies. Let me 
try and rephrase: There are label IDs which are being reported as applied 
to a specific client by querying the `*customer_client*` resource, let's 
take for example customer 929-857-9278.

SELECT
  customer_client.applied_labels, customer_client.id
FROM customer_client
WHERE customer_client.id = 9298579278

This query returns five labels:

customer_client {
  resource_name: "customers/5811963229/customerClients/9298579278"
  id: 9298579278
  applied_labels: "customers/5811963229/labels/2504066243"
  applied_labels: "customers/5811963229/labels/2504104868"
  applied_labels: "customers/5811963229/labels/2504105044"
  applied_labels: "customers/5811963229/labels/2504105333"
  applied_labels: "customers/5811963229/labels/21583384862"
}

However, some of these labels don't seem to exist in the `*customer_label*` 
resource when querying:

SELECT customer.id, customer_label.label
FROM customer_label
WHERE
  customer_label.label IN (
'customers/5811963229/labels/2504105044',
'customers/5811963229/labels/2504066243',
'customers/5811963229/labels/2504104868',
'customers/5811963229/labels/2504105333',
'customers/5811963229/labels/21583384862'
  )
  AND customer.id = 9298579278

This request only returns two labels:

customer {
  resource_name: "customers/9298579278"
  id: 9298579278
}
customer_label {
  resource_name: "customers/9298579278/customerLabels/2504066243"
  label: "customers/5811963229/labels/2504066243"
}

customer {
  resource_name: "customers/9298579278"
  id: 9298579278
}
customer_label {
  resource_name: "customers/9298579278/customerLabels/21583384862"
  label: "customers/5811963229/labels/21583384862"
}

Same behavior when using the *`label`* resource:

SELECT label.id, label.status FROM label
WHERE
label.id IN (
  2504105044,
  2504066243,
  2504104868,
  2504105333,
  21583384862
)

Only two labels returned, too:

label {
  resource_name: "customers/5811963229/labels/2504066243"
  status: ENABLED
  id: 2504066243
}

label {
  resource_name: "customers/5811963229/labels/21583384862"
  status: ENABLED
  id: 21583384862
}


I hope this makes the issue more understandable. I will be sending over 
request and response logs shortly.


Thanks again & best,
Dorian
On Thursday, 21 April 2022 at 10:44:02 UTC+2 adsapi wrote:

> Hi Dorian,
>
> Thank you for reaching out.
>
> Regarding your follow up post, could you confirm whether what you meant is 
> :
>
> *"As an addendum, I've checked a sample of accounts using 
> `customer_client`, and the additional labels also don't show up in that 
> resource. It seems to really only be `customer_label` that returns those 
> label IDs."*
>
> If yes, then as per the documentation of the customer_label 
> 
>  
> resource, it states that "*Represents a relationship between a customer 
> and a label. This customer may not have access to all the labels attached 
> to it. Additional CustomerLabels may be returned by increasing permissions 
> with login-customer-id.*".
>
> The label 
>  
> resource, on the other hand, should only return labels associated or 
> created within the account or customer_id specified in the request. The 
> customer_client 
> 
>  
> should then return "*the resource names of the labels owned by the 
> requesting customer that are applied to the client customer.*".
>
> That said, so that our team can help identify as to where the additional 
> labels (those from customer_label) are coming from, could you share the 
> complete request 
> 
>  
> and response 
> 
>  
> logs of your customer_label resource request, and specify a sample of these 
> labels that are not found anywhere else?
>
> You may then send the requested information via the *Reply privately to 
> author* option. If this option is not available, you may send the details 
> directly to our googleadsa...@google.com alias instead.
>
> Best regards,
>
> [image: Google Logo] 
> Peter Laurence 
> Google Ads API Team 
>   
>
> ref:_00D1U1174p._5004Q2a4sbV:ref
>

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

Re: `customer_label` returning labels that don't exist in `label`

[Dorian Kind]

The first sentence should of course be "...using the *`customer_client`* 
resource...". Apologies for the confusion.

On Tuesday, 19 April 2022 at 22:46:38 UTC+2 Dorian Kind wrote:

> Hi,
>
> when downloading all applied account labels within a manager account using 
> the `customer_label` resource and then comparing the returned IDs with the 
> labels listed by the `label` resource, a small number of labels only exist 
> in the former. Both requests use the same login-customer-id.
> Checking the web UI, these additional labels also don't seem to show up in 
> the interface.
>
> For a specific example, running the query
>
> SELECT customer_client.applied_labels, customer_client.id FROM 
> customer_client WHERE customer_client.applied_labels CONTAINS ALL 
> ('customers/5811963229/labels/2504104868 <(250)%20410-4868>')
>
> lists around 165 accounts in our manager account which have label ID 
> 2504104868 <(250)%20410-4868> applied, but running the corresponding query
>
> SELECT label.id, label.name, label.status FROM label
> WHERE label.id = 2504104868 <(250)%20410-4868>
>
> using the same login customer ID 5811963229 returns no results. Is there 
> anything I'm missing?
>
> Thanks & regards,
> Dorian
>

-- 
-- 
=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~
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 
"Google Ads API and AdWords 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/b6f6ea96-9fd1-4ad0-b56e-753017dcac29n%40googlegroups.com.

Re: `customer_label` returning labels that don't exist in `label`

[Dorian Kind]

As an addendum, I've checked a sample of accounts using `customer_label`, 
and the additional labels also don't show up in that resource. It seems to 
really only be `customer_client` that returns those label IDs.

On Tuesday, 19 April 2022 at 22:46:38 UTC+2 Dorian Kind wrote:

> Hi,
>
> when downloading all applied account labels within a manager account using 
> the `customer_label` resource and then comparing the returned IDs with the 
> labels listed by the `label` resource, a small number of labels only exist 
> in the former. Both requests use the same login-customer-id.
> Checking the web UI, these additional labels also don't seem to show up in 
> the interface.
>
> For a specific example, running the query
>
> SELECT customer_client.applied_labels, customer_client.id FROM 
> customer_client WHERE customer_client.applied_labels CONTAINS ALL 
> ('customers/5811963229/labels/2504104868 <(250)%20410-4868>')
>
> lists around 165 accounts in our manager account which have label ID 
> 2504104868 <(250)%20410-4868> applied, but running the corresponding query
>
> SELECT label.id, label.name, label.status FROM label
> WHERE label.id = 2504104868 <(250)%20410-4868>
>
> using the same login customer ID 5811963229 returns no results. Is there 
> anything I'm missing?
>
> Thanks & regards,
> Dorian
>

-- 
-- 
=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~
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 
"Google Ads API and AdWords 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/39238060-713f-4f83-8912-5fb84379cf4dn%40googlegroups.com.

`customer_label` returning labels that don't exist in `label`

[Dorian Kind]

Hi,

when downloading all applied account labels within a manager account using 
the `customer_label` resource and then comparing the returned IDs with the 
labels listed by the `label` resource, a small number of labels only exist 
in the former. Both requests use the same login-customer-id.
Checking the web UI, these additional labels also don't seem to show up in 
the interface.

For a specific example, running the query

SELECT customer_client.applied_labels, customer_client.id FROM 
customer_client WHERE customer_client.applied_labels CONTAINS ALL 
('customers/5811963229/labels/2504104868')

lists around 165 accounts in our manager account which have label ID 
2504104868 applied, but running the corresponding query

SELECT label.id, label.name, label.status FROM label
WHERE label.id = 2504104868

using the same login customer ID 5811963229 returns no results. Is there 
anything I'm missing?

Thanks & regards,
Dorian

-- 
-- 
=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~
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 
"Google Ads API and AdWords 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/d9bbbf30-ea07-43d1-b928-d1a4f00f5eb9n%40googlegroups.com.

Re: Regarding Client Hierarchy in the Ads API

[Dorian Kind]

Hi again,

to follow up on that, one additional advantage of having a tree as opposed 
to a list is in a situation where an account manager wants to select *all* 
accounts 
under a given manager account *except *for a small number of them. In a 
selectable tree that's easy: select the manager account—causing all 
accounts under it to be selected—and then unselect the ones that aren't 
required. In a list, this task is obviously much more difficult.

Thanks & best regards,
Dorian

On Tuesday, 12 April 2022 at 17:05:50 UTC+2 Dorian Kind wrote:

> Hi Peter,
>
> thanks for your continued support. Happy to share our main use case, which 
> is account selection in internal web tools—we are a mid-sized agency and 
> currently manage about 800 Google Ads accounts distributed over around 100 
> manager accounts in a hierarchy around 3 to 4 levels deep on average.
> In order to select the proper Ads account on which to run a specific job 
> in such a tool (they're mostly of the housekeeping and quality assurance 
> type), we've experienced that it's easier for account managers to be able 
> to follow the hierarchy of manager accounts in a tree-like view down to the 
> desired account instead of selecting it from a rather large list directly.
> In the Adwords API, implementing such a tree view is simple as it can be 
> done with a single call in the app's backend. While migrating one of our 
> tools to the Ads API, we discovered that we'd now have to do around a 
> hundred calls to get to the same result—which slows down the loading of the 
> tree view significantly, frustrating our users.
>
> I hope this gives some context for a feature request. Feel free to reach 
> out if you need more details.
>
> Best,
> Dorian
>
> On Thursday, 31 March 2022 at 08:49:00 UTC+2 adsapi wrote:
>
>> Hi Dorian,
>>
>> Thank you for your reply.
>>
>> I understand the concern on the new implementation of the get account 
>> hierarchy feature. We also are currently not aware of any plans or 
>> direction that this current implementation would be undergoing changes.
>>
>> However, our team could create a feature request, subject for review, 
>> regarding your suggestion in making the implementation less complex. For 
>> our team to do so, could you share your complete use case as well as 
>> relevant details on why the change would be more suitable?
>>
>> Best regards,
>>
>> [image: Google Logo] 
>> Peter Laurence 
>> Google Ads API Team 
>>   
>>
>> ref:_00D1U1174p._5004Q2Ys3MH:ref
>>
>

-- 
-- 
=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~
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 
"Google Ads API and AdWords 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/d553b9c5-9dcc-4120-94a8-25db012c1b31n%40googlegroups.com.

Re: Regarding Client Hierarchy in the Ads API

[Dorian Kind]

Hi Peter,

thanks for your continued support. Happy to share our main use case, which 
is account selection in internal web tools—we are a mid-sized agency and 
currently manage about 800 Google Ads accounts distributed over around 100 
manager accounts in a hierarchy around 3 to 4 levels deep on average.
In order to select the proper Ads account on which to run a specific job in 
such a tool (they're mostly of the housekeeping and quality assurance 
type), we've experienced that it's easier for account managers to be able 
to follow the hierarchy of manager accounts in a tree-like view down to the 
desired account instead of selecting it from a rather large list directly.
In the Adwords API, implementing such a tree view is simple as it can be 
done with a single call in the app's backend. While migrating one of our 
tools to the Ads API, we discovered that we'd now have to do around a 
hundred calls to get to the same result—which slows down the loading of the 
tree view significantly, frustrating our users.

I hope this gives some context for a feature request. Feel free to reach 
out if you need more details.

Best,
Dorian

On Thursday, 31 March 2022 at 08:49:00 UTC+2 adsapi wrote:

> Hi Dorian,
>
> Thank you for your reply.
>
> I understand the concern on the new implementation of the get account 
> hierarchy feature. We also are currently not aware of any plans or 
> direction that this current implementation would be undergoing changes.
>
> However, our team could create a feature request, subject for review, 
> regarding your suggestion in making the implementation less complex. For 
> our team to do so, could you share your complete use case as well as 
> relevant details on why the change would be more suitable?
>
> Best regards,
>
> [image: Google Logo] 
> Peter Laurence 
> Google Ads API Team 
>   
>
> ref:_00D1U1174p._5004Q2Ys3MH:ref
>

-- 
-- 
=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~
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 
"Google Ads API and AdWords 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/4c77064f-3afb-411d-8bb5-9109391ea287n%40googlegroups.com.

Re: Regarding Client Hierarchy in the Ads API

[Dorian Kind]

Hi Yasar,

I am aware of the fact that the Adwords API services don't always have a 
direct counterpart in the Ads API. My point is really just that a 
fundamental use case (at least for agencies that work with Google Ads) for 
the API is to build a hierarchy of all accessible Ads accounts for a given 
authenticated user, and this use case is* considerably* *more complex to 
implement* in the Ads API compared to the Adwords API. If I understand 
Ernie's and your reply correctly, there's also no plans to change that 
situation.

Best,
Dorian

On Wednesday, 30 March 2022 at 08:57:57 UTC+2 adsapi wrote:

> Hi Dorian,
>
> Thanks for getting back to us.
>
> Kindly note that AdWords API services have greatly changed or been 
> entirely replaced. CustomerService and ManagedCustomerService are 
> significantly different. However, you may check if it suits you to use the 
> *customer_client* 
>  
> report resource to get customer clients using ​​GoogleAdsService.search or 
> GoogleAdsService.searchStream methods.
>
> Regards,
> [image: Google Logo] 
> Yasar 
> Google Ads API Team 
>   
>
> ref:_00D1U1174p._5004Q2Ys3MH:ref
>

-- 
-- 
=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~
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 
"Google Ads API and AdWords 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/f87d5782-772a-4968-b1aa-a59d03899cfen%40googlegroups.com.

Re: Regarding Client Hierarchy in the Ads API

[Dorian Kind]

Hi Ernie,

Thanks for your response. I have seen the example code that you linked to 
and it still doesn't seem very efficient. It will perform 1+N calls to the 
Ads API, where N is the number of accessible manager accounts for the 
authenticated user. In larger account hierarchies—which are not uncommon 
for an agency—this can mean one has to do a couple hundred calls just to 
get the account structure. In my eyes this is a step back compared to the 
Adwords API, where the same information could be gathered with a single 
call (or a small number of calls, if paging is required) to 
the ManagedCustomerService.

Best,
Dorian

On Tuesday, 29 March 2022 at 05:28:59 UTC+2 adsapi wrote:

> Hi Dorian,
>
> I am also a member of the Google Ads API team and let me provide support 
> to your concern.
>
> It seems that you want to get the account hierarchy of your MCC account. 
> With this, try using this implementation 
> 
>  
> on retrieving account hierarchy.
>
> Let me know if this is what you are looking for. Let me know also if you 
> have further concerns.
>
> Regards,
> [image: Google Logo] 
> Ernie John 
> Google Ads API Team 
>   
>
> ref:_00D1U1174p._5004Q2Ys3MH:ref
>

-- 
-- 
=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~
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 
"Google Ads API and AdWords 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/e9ffa492-620c-4dff-9cc0-ae817b88a14bn%40googlegroups.com.

Re: Regarding Client Hierarchy in the Ads API

[Dorian Kind]

Hi Sai Teja,

it's been three years without an update. I still believe there's worth in 
having a more efficient way of downloading the whole account hierarchy 
without having to send (number of accessible manager accounts) +1 requests. 
Are you planning on adding some features towards that end?

Best,
Dorian

On Thursday, 2 May 2019 at 20:59:05 UTC+2 googleadsapi...@google.com wrote:

> Hello Dorian,
>
> In Google Ads API we don't have a way to get the account hierarchy with 
> the account details and link details in a single call. You have to follow 
> the process you mentioned to build that hierarchy. Adding to the 
> customer_client_link, when you use this resource you would be getting all 
> the links of the manager account (even of the canceled account's). Even 
> with the customer_client resource you will get canceled accounts and it is 
> not possible to filter them out. Out team is aware of the hierarchy(time 
> consuming, more requests) and the account status issues and will update you 
> once I have more information.
>
> Regards,
> Sai Teja, Google Ads API Team
>
>
> =~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~
> Also find us on our blog and discussion group:
> https://ads-developers.googleblog.com/search/label/google_ads_api
> https://developers.google.com/adwords/api/community/
> =~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~
>
> Was your question answered? Please rate your experience with us by taking 
> a short survey.
> If not -- reply to this email and tell us what else we can do to help.
>
> Take Survey 
> 
>
> Also find us on our blog and discussion group:
> http://googleadsdeveloper.blogspot.com/search/label/adwords_api
> https://developers.google.com/adwords/api/community/
> On 05/02/19 04:59:32 dor...@webrepublic.ch wrote:
>
> Hi,
>
> a common use case we have is to create an tree-like hierarchy of all Ads 
> accounts that are accessible from a given Ads OAuth2 credential. In the 
> Adwords API, it took a single call to the ManagedCustomerService to 
> receive all the information required to build such a data structure.
>
> As far as I can tell so far, in the Ads API the number of calls to build 
> an equivalent hierarchy grows linearly with the number of accounts that are 
> accessible. It seems that we'll have to
>
> 1) Use the customer_client resource to list all reachable accounts
> 2) For each gathered account, set the account's ID as login-customer-id 
> and use the customer resource to obtain account name and type 
> (sub-manager or actual account)
> 3) For each manager account identified in 2), set the account's ID as 
> login-customer-id and use the customer_client_link resource to gather 
> that manager's sub-accounts
>
> I hope I'm misunderstanding something because it looks like the process 
> above could take a while for large accounts structures (we sometimes 
> encounter MCCs with over 1'000 sub-managers and accounts).
>
> Is there a quicker way to get a list of all accessible accounts, including 
> the links between managers and accounts?
>
> Thanks for any feedback and best regards,
> Dorian
>
> -- 
> -- 
> =~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~
> 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 adwor...@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.
> 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/64bca39f-bc86-4e89-a4bb-9a0b4168e3ff%40googlegroups.com
>  
> 
> .
> For more options, visit https://groups.google.com/d/optout.
>
>

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

Re: Error details missing from ListBatchJobResultsResponse

[Dorian Kind]

Hi there,

are there any updates on this topic? Not being able to create exemption 
requests when using BatchJobService is somewhat of a show-stopper for 
migrating completely to the Ads API. Using a batch job and then reverting 
to sending mutate operations directly to the various entities' services in 
case of policy violations seems rather awkward.

Best,
Dorian

On Friday, 24 December 2021 at 09:44:17 UTC+1 ci...@channable.com wrote:

> Sharing Google's reply publicly for others who might be running into the 
> same problem:
>
> It appears that the policy details are indeed not being returned in the 
> batch job's response. That being said, allow me to create a feature request 
> for its support, subject for review. For now, you may keep an eye on our 
> blog  
> for updates or announcements.
>
> As a temporary workaround, you may collect the ads that were returned in 
> the listed results 
> 
>  
> and then replicate the error by performing the mutate using the 
> AdGroupAdService instead. Once the policy details are returned, you may 
> then perform the exemption request 
> 
> .
>
> On Monday, December 20, 2021 at 4:48:47 AM UTC+1 adsapi wrote:
>
>> Hi Ciel,
>>
>> Thank you for reaching out.
>>
>> I had to remove your initial post as it contained your logs. I also took 
>> note of your raw results when uploading the mutate operation via 
>> `AdGroupAdService`. However, would you also be able to provide the complete 
>> request 
>> 
>>  
>> and response 
>> 
>>  
>> logs from your batch job request, and also the batch job IDs generated?
>>
>> For reference, I have posted your initial concern here, minus the logs :
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>> *Hi Google Ads API team, We noticed for i.e. PolicyFinding errors on 
>> `AdGroupAd` create operations that the mutate response contains a lot of 
>> detailed information on the violation under `policy_finding_details`, which 
>> is very nice to have. However, when I send the same `AdGroupAd` create 
>> operation in a batch job, and then check the results, this bit of 
>> information is missing from the details. We use 
>> `BatchJobServiceClient.list_batch_job_results` from the python library, v9. 
>> The response content type on the `ListBatchJobResultsRequest` is set to 
>> `MUTABLE_RESOURCE`. I also tried `RESOURCE_NAME_ONLY` but same thing 
>> happens. Am I missing some parameter which ensures we receive all error 
>> details in the batch job results? Or are these details simply unavailable 
>> in the batch job result? Use case: We would like to show these policy 
>> violation details to our users so they can easily solve the problem, while 
>> using batch jobs to ensure we can efficiently send many operations to the 
>> Google Ads API. We send multiple millions of operations per day, so sending 
>> duplicate singular operations just to get this error information is not so 
>> feasible. Hope you can help, thanks in advance. Best, Ciel*
>>
>> You may then provide the additional details I requested via the *Reply 
>> privately to author* option, so that I may be able to raise this to the 
>> rest of our team to clarify the details that should be available when 
>> performing ad operations via th BatchJobService.
>>
>> If the above private option is not available, you may send the details 
>> directly to our googleadsa...@google.com alias instead.
>>
>> Best regards,
>>
>> [image: Google Logo] 
>> Peter Laurence Napa Oliquino 
>> Google Ads API Team 
>>   
>>
>> ref:_00D1U1174p._5004Q2TN6DT:ref
>>
>

-- 
-- 
=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~
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 
"Google Ads API and AdWords 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/9ccfc991-8e2c-4af5-88f1-020f58daa0ecn%40googlegroups.com.

Mutate HTML5_UPLOAD_AD ads

[Dorian Kind]

Hi,

according to the documentation 
, ads of 
type DisplayUploadAd are mutable. This should include the specific 
subtype HTML5_UPLOAD_AD 

.
However, when trying to set the "url_custom_parameters" field of 
an HTML5_UPLOAD_AD ad, the API responds with "field_error: IMMUTABLE_FIELD".
Is there only a subset of fields that are actually mutable for this type of 
ad? If so, is this documented somewhere?

Thanks & best regards,
Dorian

-- 
-- 
=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~
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 
"Google Ads API and AdWords 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/fc6cdaa7-cbac-417d-bbb1-0ccaf977cbffn%40googlegroups.com.

Re: How to Remove Custom Parameters in the Ads API

[Dorian Kind]

Thanks for the confirmation, Matt.

On Tuesday, 1 March 2022 at 17:22:14 UTC+1 adsapi wrote:

> Hi Dorian,
>
> Thanks for reaching out. As you pointed out, there isn't a field to set 
> the status of an existing custom parameter. To remove a single parameter 
> from the list, you will have to make an update request that only includes 
> the custom parameters that you wish to be included.
>
> Regards,
> Matt
> Google Ads API Team
>
> [image: Google Logo] 
> Matt 
> Google Ads API Team 
>   
>
> ref:_00D1U1174p._5004Q2Wz985:ref
>

-- 
-- 
=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~
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 
"Google Ads API and AdWords 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/4bd902f8-844a-486c-93d7-2b93d2668c16n%40googlegroups.com.

Re: How to Remove Custom Parameters in the Ads API

[Dorian Kind]

To bump this thread, note that it's of course possible to just send the 
full set of custom parameters excluding the unwanted one in an update 
operation, which will essentially remove the omitted parameter. Still 
wondering whether there is more elegant way of doing this.

On Friday, 25 February 2022 at 16:56:21 UTC+1 Dorian Kind wrote:

> Hello,
>
> in the Adwords API, Custom Parameters can be removed by sending an update 
> operation with the "isRemove" flag 
> <https://developers.google.com/adwords/api/docs/reference/v201809/CampaignService.CustomParameter>
>  
> set.
>
> In the Ads API, this flag doesn't exist 
> <https://developers.google.com/google-ads/api/reference/rpc/v10/CustomParameter>.
>  
> Setting the Custom Parameter's "value" field to the empty string will not 
> remove it and just omitting it (only sending the "key"  attribute) causes 
> an "INVALID_ARGUMENT" error with the explanation "Custom parameter value 
> cannot be null".
>
> How do I go about removing existing Custom Parameters from a campaign (or 
> ad group, ad, keyword etc.)?
>
> Thanks & best regards
> Dorian
>

-- 
-- 
=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~
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 
"Google Ads API and AdWords 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/675d204e-c50d-4528-9efa-e38f14eb7bb7n%40googlegroups.com.

How to Remove Custom Parameters in the Ads API

[Dorian Kind]

Hello,

in the Adwords API, Custom Parameters can be removed by sending an update 
operation with the "isRemove" flag 

 
set.

In the Ads API, this flag doesn't exist 
.
 
Setting the Custom Parameter's "value" field to the empty string will not 
remove it and just omitting it (only sending the "key"  attribute) causes 
an "INVALID_ARGUMENT" error with the explanation "Custom parameter value 
cannot be null".

How do I go about removing existing Custom Parameters from a campaign (or 
ad group, ad, keyword etc.)?

Thanks & best regards
Dorian

-- 
-- 
=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~
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 
"Google Ads API and AdWords 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/f6384c20-a51e-4712-a4b1-1a7142054380n%40googlegroups.com.

Re: UNEXPECTED_INTERNAL_API_ERROR When Removing And Adding Deleted Youtube Channel Criterion

[Dorian Kind]

Hi Ben,

thanks for the update. We have not yet tackled the migration of that 
specific code as we're focussing on moving the reporting use cases to the 
new API in order to first gain some experience. I will let you know what we 
find once we start working on migrating the batch modification code.

Best regards,
Dorian

On Wednesday, 15 December 2021 at 20:43:03 UTC+1 adsapi wrote:

> Hi Dorian,
>
> Unfortunately not yet. I'm following up with the batch jobs team to see if 
> they can increase the priority of the investigation.
>
> In the meantime, have you considered migrating your application to the new 
> Google Ads API? I'd be curious to know if you have the same issues there.
>
> Best,
>
> Ben, Google Ads API Team
>
> ref:_00D1U1174p._5004Q2Mhwnf:ref
>

-- 
-- 
=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~
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/85d75a24-a1d0-417d-a9fb-36bf845a1424n%40googlegroups.com.

Re: UNEXPECTED_INTERNAL_API_ERROR When Removing And Adding Deleted Youtube Channel Criterion

[Dorian Kind]

Hi Ben,

seeing as it's been a while, are there any updates on this issue?

Thanks & best regards,
Dorian

On Thursday, 23 September 2021 at 19:34:43 UTC+2 adsapi wrote:

> Hi Dorian,
>
> I'm a Developer Relations Engineer jumping in to help with this issue. 
> I've routed this through to the team that works on Batch Jobs, but they're 
> still in the process of investigating the root cause. I'll follow up here 
> as soon as I have more information. 
>
> Thanks,
> Ben, Google Ads API Team
>
> ref:_00D1U1174p._5004Q2Mhwnf:ref
>

-- 
-- 
=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~
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/7dc23e5e-753e-461b-aa90-ef592513b6d1n%40googlegroups.com.

Re: UNEXPECTED_INTERNAL_API_ERROR When Removing And Adding Deleted Youtube Channel Criterion

[Dorian Kind]

Hi Aryeh,

it's been a couple weeks, and this issue is still hitting us every now and 
then. Do you already have any feedback which you would be able to share?

Thanks,
Dorian
On Wednesday, 1 September 2021 at 21:21:56 UTC+2 adsapi wrote:

> Hi Dorian,
>
> I brought your internal error with your comments up with my team. We will 
> get back to you as soon as possible.
>
> Regards,
>
> [image: Google Logo] 
> Aryeh Baker 
> Google Ads API Team 
>   
>
> ref:_00D1U1174p._5004Q2Mhwnf:ref
>

-- 
-- 
=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~
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/66df97e2-0def-457e-8a53-cf3595521b20n%40googlegroups.com.

Re: UNEXPECTED_INTERNAL_API_ERROR When Removing And Adding Deleted Youtube Channel Criterion

[Dorian Kind]

Hi Yasar,

I *think* I have answered privately, but as there doesn't seem to a way to 
copy oneself when replying in the new Google Groups interface, I'm not 
completely sure. Could you confirm that you have received the SOAP logs? 
Thank you very much!

Best,
Dorian

On Wednesday, 25 August 2021 at 04:47:03 UTC+2 adsapi wrote:

> Hi Dorian,
>
> Thanks for reaching out to us.
>
> For us to provide the specific recommendations on the 
> InternalApiError.UNEXPECTED_INTERNAL_API_ERROR 
> ,
>  
> could you please provide with us the complete SOAP request 
> 
>  and response 
> 
>  logs, 
> along with its requestId 
> ,
>  
> generated when the error occurred? Also, could you send us the batch job 
> IDs that failed, so that our team can further check better? You may check 
> this guide 
> 
>  on 
> how to check batch job results.
>
> You may then send the requested information via the *Reply privately to 
> author* option. If this option is not available, you may send the details 
> directly to our googleadsa...@google.com alias instead.
>
> Regards, 
> [image: Google Logo] 
> Yasar 
> Google Ads API Team 
>   
>
> ref:_00D1U1174p._5004Q2Mhwnf:ref
>

-- 
-- 
=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~
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/e238d918-71cd-4232-ba68-b6267403325fn%40googlegroups.com.

UNEXPECTED_INTERNAL_API_ERROR When Removing And Adding Deleted Youtube Channel Criterion

[Dorian Kind]

Hi,

we've encountered a peculiar case where removing and adding the same 
criterion in a batch job reproducibly causes 
an UNEXPECTED_INTERNAL_API_ERROR to occur.

For some background, we have a housekeeping script in use that reads a 
rather large list of Youtube Channels from a spreadsheet and configures 
these channels as account level negatives in all of our Ads accounts. This 
is using the Adwords API.

When one of these channels get removed from Youtube, the following happens:

   - Our syncing logic checks the account's existing YT Channel exclusion 
   criteria
   - The removed channel is still existing, but has its channel ID and 
   channel name set to null
   - As we know that this criterion refers to a removed YT channel, we mark 
   it for removal
   - But at the same time, the YT Channel is still present in the source 
   spreadsheet, so we mark the channel as needing to be added to the account
   - Both entries actually refer to the same YT channel, but we cannot 
   check for that because the channel ID has been removed from the existing 
   criterion
   - We set up a batch job that contains two operations, one to remove the 
   existing criterion and one to create a new one
   - That batch job fails with an UNEXPECTED_INTERNAL_API_ERROR


I'm wondering how we can better handle this. The crux really lies in the 
fact that once a YT channel is deleted, the corresponding criterion on the 
Ads side no longer is identifiable because its channelId and channelName 
fields are both null. Any thoughts?

-- 
-- 
=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~
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/5382b875-b5c8-4e6f-bb21-7f57e88d1c7bn%40googlegroups.com.

Re: Unkown Feed Placeholder Type

[Dorian Kind]

For the benefit of future visitors to this thread—Anthony was able to help 
me. The following feed item types seem to be undocumented at this point in 
time:

*42*: Dymamic image extensions 

*48*: Image extensions 



On Tuesday, 19 January 2021 at 21:04:10 UTC+1 adsapiforumadvisor wrote:

> Hi Dorian,
>
> Can you please send the API request and response you used to get this 
> placeholder type? Please do so using *reply privately*.
>
> Regards,
> Anthony
>
> [image: Google Logo] 
> Anthony 
> Google Ads API Team 
>   
>
> ref:_00D1U1174p._5004Q2B1Sp7:ref
>

-- 
-- 
=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~
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/7b11cc52-255f-469c-9b74-9e876a55fda0n%40googlegroups.com.

Unkown Feed Placeholder Type

[Dorian Kind]

Hi,
we recently came across a single FeedItem in one of our accounts with 
placeholder type *48*. This type ID doesn't show up in the reference data 
 and 
it's the first time we encounter that specific type.
What kind of feed item are we looking at here?
Thanks for your feedback & best regards,
Dorian

-- 
-- 
=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~
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/c2b4a929-6429-4af5-b79f-057ea2f721dbn%40googlegroups.com.

Re: Test Accounts Cancelled

[Dorian Kind]

Hi Xiaoming,

I think we're having somewhat of a misunderstanding here. When we try to 
access these accounts over the API, we get a 
AuthorizationError.CUSTOMER_NOT_ACTIVE error. I assumed that this happens 
because the accounts are closed, but if I get you right then that's not the 
actual cause as all test accounts are closed in the first place(?).
So let me rephrase my question, how can we avoid the 
AuthorizationError.CUSTOMER_NOT_ACTIVE error when accessing our test 
accounts?

Best,
Dorian

On Wednesday, 2 December 2020 at 21:49:40 UTC+1 adsapiforumadvisor wrote:

> Hi Dorian,
>
> Thank you for reaching out. As I said earlier the accounts created under 
> the test manager account are test accounts by default and they have the 
> “Closed” status in the first place. These accounts are not suddenly closed. 
> To view them, you would need to click on the down arrow next to the test 
> account number and then click the three vertical dots followed by ticking 
> the cancelled accounts option.
>
>
>
> Thanks and regards,
> Xiaoming, Google Ads API Team
>
> [image: Google Logo] 
> Xiaoming 
> Google Ads API Team 
>   
>
> ref:_00D1U1174p._5004Q28lLgW:ref
>

-- 
-- 
=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~
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/6a92b037-de2e-4e7c-9f3c-70020e05f439n%40googlegroups.com.

Re: Test Accounts Cancelled

[Dorian Kind]

Hi Xiaoming,

thank you for your message. I'm still wondering why all of those accounts 
were suddenly closed and if there's any way to reactivate them so we don't 
have to set them all up again.

Best,
Dorian

On Monday, 30 November 2020 at 21:52:33 UTC+1 adsapiforumadvisor wrote:

> Hi Dorian,
>
> Thank you for reaching out. The test account is with “closed” status and 
> all the test client accounts are invisible by default. To be able to see 
> the test client accounts under the test manager account, you would need to 
> click on the down arrow next to the test manager account number and then on 
> the drop-down list click on the three vertical dots icon and select 
> cancelled accounts.
>
> Thanks and regards,
> Xiaoming, Google Ads API Team
> [image: Google Logo] 
> Xiaoming 
> Google Ads API Team 
>   
>
> ref:_00D1U1174p._5004Q28lLgW:ref
>

-- 
-- 
=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~
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/6eb2bdbd-675d-4b74-af2c-e935e24b1273n%40googlegroups.com.

Test Accounts Cancelled

[Dorian Kind]

Hi,

we have a Google Ads test manager acccount containing a couple of test 
accounts that we use for integration testing. Around two weeks ago, all of 
those accounts were cancelled, seemingly without any notice being sent to 
the account admin.
What's more, in contrast to regular Ads accounts that can be reactivated if 
they are cancelled for lack of spend, this doesn't appear to be an option 
in this case.
Is there anything we can do to un-suspend these accounts? Or at least 
understand why they were cancelled in the first place?

Thanks & Cheers

-- 
-- 
=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~
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/9fd0acb6-1abb-49af-9fa7-f0cd3d8b6ad8n%40googlegroups.com.

Re: Emtpy channelId and channelName in YouTubeChannel criterion

[Dorian Kind]

In case anyone stubles across this thread, the described behavior is 
expected and caused by a change in Youtube data retention policy: 
https://ads-developers.googleblog.com/2019/10/video-and-channel-ids-change-in-adwords.html

On Friday, 31 July 2020 at 10:02:01 UTC+2 Dorian Kind wrote:

> Hi Mitchell,
>
> I have sent you the logs privately. Many thanks for taking a look at this.
>
> Best,
> Dorian
>
>
> On Thursday, 30 July 2020 20:01:00 UTC+2, adsapiforumadvisor wrote:
>>
>> Hi Dorian,
>>
>> Thank you for reaching out. Can you please share your complete detailed 
>> request and response logs *via Reply privately to author *so I can 
>> further investigate the issue? You can find information on enabling logging 
>> in the ReadMe of your client library 
>> <https://developers.google.com/adwords/api/docs/clientlibraries>.
>>
>> Regards,
>> Mitchell
>> Google Ads API Team
>>
>> ref:_00D1U1174p._5004Q22aH4z:ref
>>
>

-- 
-- 
=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~
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/0a357ac0-ba2d-4e62-a79e-50736ba8c907n%40googlegroups.com.

Re: Emtpy channelId and channelName in YouTubeChannel criterion

[Dorian Kind]

Hi Mitchell,

I have sent you the logs privately. Many thanks for taking a look at this.

Best,
Dorian

On Thursday, 30 July 2020 20:01:00 UTC+2, adsapiforumadvisor wrote:
>
> Hi Dorian,
>
> Thank you for reaching out. Can you please share your complete detailed 
> request and response logs *via Reply privately to author *so I can 
> further investigate the issue? You can find information on enabling logging 
> in the ReadMe of your client library 
> .
>
> Regards,
> Mitchell
> Google Ads API Team
>
> ref:_00D1U1174p._5004Q22aH4z:ref
>

-- 
-- 
=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~
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/3de827b4-a1cb-4116-a6a0-a88d850123bco%40googlegroups.com.

Emtpy channelId and channelName in YouTubeChannel criterion

[Dorian Kind]

Hi,

I've stumbled upon a case where a specific Youtube exclusion (a Criterion 
object of type "YOUTUBE_CHANNEL" as returned by 
the CustomerNegativeCriterionService) did not have its channelId nor its 
channelName field set.
If it helps, the ID of that specific criterion is 295325090879.

I was wondering if this is expected behavior, or if something is off with 
that exclusion / YT channel?

Thanks for any feedback & best regards,
Dorian

-- 
-- 
=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~
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/c202a2e2-e8e5-48fe-982d-0190f5cdca03n%40googlegroups.com.

Re: Getting report totals in new Google Ads API

[Dorian Kind]

Hi there,

sorry to ressurect such an old thread, but I just wanted to inquire whether 
this feature has been added or is being considered for addition to the 
Google Ads API in the meanwhile.

Thanks & best regards,
Dorian

On Friday, 24 May 2019 22:54:12 UTC+2, adsapiforumadvisor wrote:
>
> Hello Dorian,
>
> I understand your concern. I will let my team know and update you when I 
> have more information.
>
> Regards,
> Sai Teja, Google Ads API Team
>
> ref:_00D1U1174p._5001UAqWq9:ref

-- 
-- 
=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~
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/60d08c4f-aa41-45d3-9a59-c33873812f27%40googlegroups.com.

Re: Getting report totals in new Google Ads API

[Dorian Kind]

Hi,

just wanted to follow up on this.

A reporting use case that we encounter quite frequently is to aggregate 
metrics for a specific set of campaigns of an account (e.g. "How are all my 
campaigns for product X doing?"). With the Adwords API, we can use the 
campaign report, set up appropriate filters and use the summary row of the 
report directly.

As Francis mentions, the complexity and feasibility of calculating 
totals on our end depends a lot on the chosen metrics. While it's simple to 
aggregate clicks, I wouldn't know how to calculate the total "Search lost 
absolute top impression share" for a subset of campaigns of an account—I'd 
assume it's weighted by impressions, but I don't think this is documented 
anywhere.

Thus, having a summary row available in the response of the 
GoogleAdsService.Search endpoint is essential for us.

Thanks and best regards,
Dorian

On Thursday, 13 December 2018 03:36:06 UTC+1, Luis Xander Talag (AdWords 
API Team) wrote:
>
> Hi Francis,
>
> I'm afraid the totals for metric values in reports in Google Ads API Beta 
> is not yet supported and is currently available only in AdWords API using 
> the skipReportSummary HTTP request 
> 
>  value. 
> I could not comment on if and when this feature will be supported in Google 
> Ads API Beta. However, you may follow our blog 
>  for any 
> updates on this.
>
> Thanks and regards,
> Luis
> AdWords API Team
>
> On Thursday, December 13, 2018 at 4:21:54 AM UTC+8, Francis Moore wrote:
>>
>> Hi all,
>>
>> I'm looking for a way to get the totals for the metrics of a report in 
>> the Google Ads Beta API. It is available in the current AdWords API with 
>> the CSV format, but not with the XML format.
>>
>> In the Google Ads API, it does not look to be available in the response, 
>> since all we get is an array of GoogleAdsRow
>>
>> https://developers.google.com/google-ads/api/reference/rpc/google.ads.googleads.v0.services#google.ads.googleads.v0.services.SearchGoogleAdsResponse
>>
>> I could of course just sum up the values, but many metrics just can't 
>> summed up like that, for example Search Impression Share. 
>>
>> Any idea? Thanks!
>>
>

-- 
-- 
=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~
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.
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/c06e4815-82eb-4178-a451-d591ed8a3b6b%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [GOOGLE ADS ERROR] - How to Fetch the Error Name and Discrepancy between Index and Number in Protobuf

[Dorian Kind]

Hi Marco,

about the first part of your question, there's an open issue on the client 
library's tracker covering exactly your scenario: 
https://github.com/googleads/google-ads-python/issues/110
As a workaround, you might be able to use 
`google.protobuf.json_format.MessageToDict` to get the enum name.

HTH, best regards,
Dorian

On Wednesday, 22 May 2019 16:30:51 UTC+2, Marco Frighetto wrote:
>
> Hi there,
> how can i take in python the error name from the enumerate in protobuf 
> response?
>
> Furthermore, i see a discrepancy between the index and number in protobuf. 
> Is this intended to be so? See the screenshot attached (for reference 
> 
> ). 
>
> Thank for you help.
> Marco
>

-- 
-- 
=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~
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.
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/a5c76e93-c9e8-4cf2-8cd1-2af9a01979aa%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

GAQL Queries with Time Ranges Before Unix Epoch Cause "Internal error encountered."

[Dorian Kind]

Hi,

I've been playing around with the GoogleAdsService a bit, and noticed that 
sending a query for dates before 1970-01-01 will reliably cause a 
StatusCode.INTERNAL 
/ Internal error encountered error.

Not that this matters for any real purposes, but maybe the error message 
could be more specific.

Regards,
Dorian

-- 
-- 
=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~
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.
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/d1987945-3e94-42be-886f-08e040c114a2%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Using LIMIT without ORDER BY in a query for customer_client results in server error

[Dorian Kind]

Hi there,

just an observation I made, if you send a query like the following to the 
GoogleAdsService, the result is reproducibly "Internal error encountered.":

SELECT
  customer_client.client_customer
FROM customer_client
LIMIT 1000

The actual limit value doesn't matter, only either adding an ORDER BY or 
removing the LIMIT clause makes the error go away. Other resources don't 
seem to be affected by this and as far as I understand the Google Ads Query 
Language grammar it should be a valid query.

-- 
-- 
=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~
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.
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/4b46b61a-3218-40d6-9aee-c8452f4efb11%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Outstream video ads don't seem to have an AdType in the AdWords API

[Dorian Kind]

Hi Sai Teja,

thanks for confirming. Can we rely on the behavior that these ads have no 
AdType going forward?

Best,
Dorian

On Tuesday, 7 May 2019 20:50:27 UTC+2, googleadsapi-forumadvisor wrote:
>
> Hello Dorian,
>
> I took a look at the API report for that outstream Ad and got no value for 
> the AdType field. It seems like for the Outstream Ads AdType is empty.  
>
> Regards,
> Sai Teja, Google Ads API Team
>
> =~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~
> Also find us on our blog and discussion group:
> https://ads-developers.googleblog.com/search/label/google_ads_api
> https://developers.google.com/adwords/api/community/
> =~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~
>
> Was your question answered? Please rate your experience with us by taking 
> a short survey.
> If not -- reply to this email and tell us what else we can do to help.
>
> Take Survey 
> 
>
> Also find us on our blog and discussion group:
> http://googleadsdeveloper.blogspot.com/search/label/adwords_api
> https://developers.google.com/adwords/api/community/
>

-- 
-- 
=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~
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.
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/b125ac6b-b61a-4bb4-b86a-81a16380d256%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Outstream video ads don't seem to have an AdType in the AdWords API

[Dorian Kind]

Hello Sai Teja,

here's the report definition:


https://adwords.google.com/api/adwords/cm/v201809;>
  
Id
AdType

  CampaignStatus
  IN
  ENABLED
  PAUSED


  AdGroupStatus
  IN
  ENABLED
  PAUSED


  Status
  IN
  ENABLED
  PAUSED

  
  Test Report
  AD_PERFORMANCE_REPORT
  TODAY
  CSV


For the customer with client ID *974-761-3036, *you'll see that ad 
ID 319718311814, which is an outstream video ad, does not have an AdType 
set, whereas ad ID 151640670846 (an instream ad) uses "Display Ad".

Let me know if additional information is required.

Thanks & cheers,
Dorian

On Monday, 6 May 2019 20:44:59 UTC+2, googleadsapi-forumadvisor wrote:
>
> Hello Dorian,
>
> Could you please share the report definition, the Client customer Id and 
> the Ad_Id for which you are seeing this discrepancy to help further?
>
> Regards,
> Sai Teja, Google Ads API Team
>
>
> =~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~
> Also find us on our blog and discussion group:
> https://ads-developers.googleblog.com/search/label/google_ads_api
> https://developers.google.com/adwords/api/community/
> =~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~
>
> Was your question answered? Please rate your experience with us by taking 
> a short survey.
> If not -- reply to this email and tell us what else we can do to help.
>
> Take Survey 
> 
>
> Also find us on our blog and discussion group:
> http://googleadsdeveloper.blogspot.com/search/label/adwords_api
> https://developers.google.com/adwords/api/community/
>

-- 
-- 
=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~
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.
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/97befeca-73bf-4d15-893a-5784b2ef2df8%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Outstream video ads don't seem to have an AdType in the AdWords API

[Dorian Kind]

Hi,

I just noticed that in the AD_PERFORMANCE_REPORT, outstream video ads have 
their AdType field set to the empty string, whereas other types of video 
ads use the value "Display ad", as far as I can tell,
Is this by design? If so, can we safely assume that an empty AdType field 
always indicates an outstream video ad?

Thanks and best regards,
Dorian

-- 
-- 
=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~
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.
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/1579c398-2b01-4482-b4d8-0f791ed58342%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Regarding Client Hierarchy in the Ads API

[Dorian Kind]

Hi,

a common use case we have is to create an tree-like hierarchy of all Ads 
accounts that are accessible from a given Ads OAuth2 credential. In the 
Adwords API, it took a single call to the ManagedCustomerService to receive 
all the information required to build such a data structure.

As far as I can tell so far, in the Ads API the number of calls to build an 
equivalent hierarchy grows linearly with the number of accounts that are 
accessible. It seems that we'll have to

1) Use the customer_client resource to list all reachable accounts
2) For each gathered account, set the account's ID as login-customer-id and 
use the customer resource to obtain account name and type (sub-manager or 
actual account)
3) For each manager account identified in 2), set the account's ID as 
login-customer-id and use the customer_client_link resource to gather that 
manager's sub-accounts

I hope I'm misunderstanding something because it looks like the process 
above could take a while for large accounts structures (we sometimes 
encounter MCCs with over 1'000 sub-managers and accounts).

Is there a quicker way to get a list of all accessible accounts, including 
the links between managers and accounts?

Thanks for any feedback and best regards,
Dorian

-- 
-- 
=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~
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.
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/64bca39f-bc86-4e89-a4bb-9a0b4168e3ff%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Get permissions of login behind OAuth access token

[Dorian Kind]

To at least check whether there's only read-only access to a given account 
you could try send a simple operation (e.g. creating a new campaign) with 
the validateOnly header as suggested in this thread. 


On Tuesday, 2 April 2019 10:23:48 UTC+2, al...@trueclicks.com wrote:
>
> I have a quick question that I did not find answer to in this forum yet.
>
> Google Ads login can have one of 5 different permission levels, starting 
> from lowest Email-only all the way up to Administrative access. The OAuth 
> token inherits the same permissions of a login it was authenticated with.
>
> *Question:* Is it possible to retrieve through an Google Ads/AdWords API 
> call what permissions Email/../Administrative we have with the given OAuth 
> token?
>
>
> Best,
>  Ales
>

-- 
-- 
=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~
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.
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/89087cf2-3a93-48a8-be80-763d9ac75bf3%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Plausibility of automated monthly account backups through API?

[Dorian Kind]

Hi David,

we were facing the same challenge. As backing up accounts over the API 
doesn't seem feasible, we currently use a dedicated host which runs an 
AutoHotkey script every day to download and export a couple hundred 
accounts in the Adwords Editor. The script then uploads the .aea files to a 
cloud storage provider. While this solution isn't completely satisfactory, 
it generally runs reliably and only requires manual intervention if there's 
an update to the Adwords Editor.

Best regards,
Dorian

On Monday, 18 March 2019 20:46:06 UTC+1, david@mvfglobal.com wrote:
>
> Hi,
>
>
> I'm looking to find a way to automatically backup our adwords accounts 
> (200+) on a monthly basis.
>
> The main reason is as insurance, so that we can roll-back to a successful 
> state if a junior tanks performance (quickly or slowly).
>
>
> Currently, I back up high-risk accounts using adwords editor and save as 
> .aea & .zip (for images) on my computer.
>
>
> Does anyone know of a solution for doing this via API?
>
> My dream would be monthly account backups dropped into Google Drive or 
> Amazon S3 for all of the hundreds of accounts.
>
>
> Thanks in advance for any thoughts, suggestions or resources to help me on 
> my mission.
>

-- 
-- 
=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~
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.
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/d36b8470-e030-46ff-bfa3-cc8fd020e1f7%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Frequent time outs while accessing Adwords APIs

[Dorian Kind]

Hi,

FWIW, we're seeing the same issue with other Google APIs (such as Sheets), 
also only in the AWS Ireland (eu-west-1) region. The root cause seems to be 
closely related—we noticed that *.googleapis.com would only resolve to a 
single IP address (always 74.125.193.95) from these hosts, whereas normally 
and in all other AWS regions we tested, these queries resolve to multiple 
addresses.

AWS support in our case pointed out the DNS discrepancy as most likely 
reason for the timeouts and reset connections—they didn't find anything on 
their end that might be the cause.

I've created an issue about this 
 on Google's issue 
tracker, but haven't heard back so far. 

Regards,
Dorian

On Wednesday, 13 March 2019 21:59:27 UTC+1, googleadsapi-forumadvisor wrote:
>
> Hi Igor,
>
> So far our investigation has not identified a cause for these issues on 
> our side. Did you get a chance to check with AWS support to see if there 
> were any problems on their end?
>
> Thanks,
> Josh, AdWords API Team
>
> =~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~
> Also find us on our blog and discussion group:
> http://googleadsdeveloper.blogspot.com/search/label/adwords_api
> https://developers.google.com/adwords/api/community/
> =~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~
>
> On 03/13/19 15:03:45 sc...@bgenius.com  wrote:
>
> Hi,
>
> We did see a small window where this issue again arise but pretty quickly 
> resolved itself again. We eventually did not move our software, but earlier 
> tests did show us that moving from Ireland to Frankfurt would help.
>
> For me this is a red flag: issue was visible for both Carmine and us 
> whereas we both used AWS in Ireland.
>
> Hope you still find the issue to resolve it.
>
> Best,
>
> On Wednesday, 13 March 2019 18:49:27 UTC+1, googleadsapi-forumadvisor 
> wrote:
>
> Hi,
>
> Thanks for the update. We've heard from other users that this has subsided 
> as well.
>
> Cheers,
> Josh, AdWords API Team
>
> =~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~
> Also find us on our blog and discussion group:
> http://googleadsdeveloper.blogspot.com/search/label/adwords_api
> https://developers.google.com/adwords/api/community/
> =~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~
>
> On 03/13/19 06:23:57 carmine...@gmail.com wrote:
>
> Hi All,
> I solved moving to another AWS Region, from Ireland to Virginia.
>
> Thank you
>
> On Tuesday, March 12, 2019 at 8:52:19 AM UTC+1, Igor Schut wrote:
>
> Hi Josh,
>
> We see that yesterday ~ 17:00 CET all the timeouts resolved and the system 
> is now working as usual. Did you figure out what caused this temporary 
> blockage? What has changed?
>
> Minor side note: the issue started at Wednesday ~ 17:00 CET.
>
> Best,
> Igor
>
> On Monday, 11 March 2019 22:07:04 UTC+1, googleadsapi-forumadvisor wrote:
>
> Hi Igor, Carmine,
>
> I've asked the engineering team to look into this. In the meantime, since 
> you both seem to be having trouble with AWS, have you reached out to their 
> support team to see if there are any known issues on their side?
>
> Thanks,
> Josh, AdWords API Team
>
> =~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~
> Also find us on our blog and discussion group:
> http://googleadsdeveloper.blogspot.com/search/label/adwords_api
> https://developers.google.com/adwords/api/community/
> =~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~
>
> On 03/09/19 09:13:32 sc...@bgenius.com wrote:
>
> We have another system running elsewhere which does not have these issues. 
>
> The ipaddress of adwords.google.com is 74.125.193.100. 
>
> Best, 
> Igor 
>
> -- 
> -- 
> =~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~ 
> 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. 
> Visit this group at https://groups.google.com/group/adwords-api. 
> To view this discussion on the web visit https://groups.google.com/d/ms
> gid/adwords-api/42cbffa7-0423-4bb2-8346-62f0d8634f27%40googlegroups.com. 
> For more options, visit https://groups.google.com/d/optout. 
>
> -- 
> -- 
> =~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~
> Also find us on our blog:
> https://googleadsdeveloper.blogspot.com/
> =~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~
>  
> You received this message because you 

Re: Get Keyword Idea API

[Dorian Kind]

That should be the case, yes.

On Friday, 1 March 2019 11:30:31 UTC+1, Zied Chaari wrote:
>
> Thanks Dorian,
>
> So if i try to call this API with a production account and a verified 
> access token, I will get real results?
>
> Cheers,
> Zied
>
> On Friday, March 1, 2019 at 9:34:55 AM UTC+1, Dorian Kind wrote:
>>
>> Hi Zied,
>>
>> these keyword idea results are indicative of a *test account*. You'll 
>> only get real results from the TargetingIdeaService of *production* 
>> accounts.
>>
>> Cheers,
>> Dorian
>>
>> On Thursday, 28 February 2019 18:11:36 UTC+1, Zied Chaari wrote:
>>>
>>> Hi,
>>>
>>> When I'm trying to reproduce this 
>>> <https://developers.google.com/adwords/api/docs/samples/csharp/optimization#get-keywords-related-to-a-seed-keyword>
>>>  
>>> example 
>>> <https://developers.google.com/adwords/api/docs/samples/csharp/optimization#get-keywords-related-to-a-seed-keyword>:
>>>  
>>> EXAMPLE 
>>> <https://developers.google.com/adwords/api/docs/samples/csharp/optimization#get-keywords-related-to-a-seed-keyword>
>>>  to 
>>> retrieve keywords, 
>>> i'm getting results like this: bakery 50bca43, bakery 46a29ba6, ...
>>>
>>> what is 50bca43 and 46a29ba6? and why i'm not not getting a full words 
>>> like the screen bellow
>>>
>>>
>>> [image: Capture.PNG]
>>> Thanks
>>>
>>

-- 
-- 
=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~
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.
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/f0e042a5-df58-4ee0-904c-01901b1cb01a%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Get Keyword Idea API

[Dorian Kind]

Hi Zied,

these keyword idea results are indicative of a *test account*. You'll only 
get real results from the TargetingIdeaService of *production* accounts.

Cheers,
Dorian

On Thursday, 28 February 2019 18:11:36 UTC+1, Zied Chaari wrote:
>
> Hi,
>
> When I'm trying to reproduce this 
> 
>  
> example 
> :
>  
> EXAMPLE 
> 
>  to 
> retrieve keywords, 
> i'm getting results like this: bakery 50bca43, bakery 46a29ba6, ...
>
> what is 50bca43 and 46a29ba6? and why i'm not not getting a full words 
> like the screen bellow
>
>
> [image: Capture.PNG]
> Thanks
>

-- 
-- 
=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~
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.
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/6e702e87-f840-46f0-bbcf-e4833ab847ee%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: API Test account - how sandboxed and what data is available?

[Dorian Kind]

Yes, that is correct. You could say that there's three "levels" of 
credentials:

   - Developer token: Identifies a given Adwords API developer, used for 
   RMF enforcement, rate limiting and the like.
   - OAuth2 client: Used to identify a given application towards a user and 
   creating access tokens that can be used to access the API on the user's 
   behalf. Multiple OAuth2 clients/applications can use the same developer 
   token, and I assume the same OAuth2 client can be used with different 
   developer tokens (haven't tested the second case, though).
   - The actual Adwords user making the API call, identified via the OAuth2 
   access token. The effective Adwords permissions of that Adwords user 
   determine what operations can be performed, both in the Web UI and via the 
   Adwords API

I hope that clears up things somewhat.

Cheers,
Dorian

On Thursday, 21 February 2019 17:22:42 UTC+1, Si J wrote:
>
> Great thanks Dorian.
>
> To double check - the permissions set in the GUI persist to api access, 
> because access still requires an individual client id/secret?
>
> Cheers,
> Si.
>
> On Monday, 18 February 2019 09:56:58 UTC, Dorian Kind wrote:
>>
>> Hi Si,
>>
>> you might be able to handle the scenario by using a production developer 
>> token, but giving your developer read-only access to the Google Ads account 
>> in question. That way, he'll be able to access all account data without 
>> risking any unwanted modifications to the setup.
>>
>> Cheers,
>> Dorian
>>
>> On Friday, 15 February 2019 10:32:39 UTC+1, Si J wrote:
>>>
>>> Hi Peter 
>>>
>>> Thanks for the reply. I've had a look at the docs, that's helpful thank 
>>> you. 
>>>
>>> If someone was using a test account can they still access the 
>>> optimization service, in particular historical search volumes per keyword 
>>> using seed or upload test data?
>>>
>>> Thanks,
>>>
>>> Si.
>>>
>>

-- 
-- 
=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~
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.
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/814a7e6f-18cd-4b04-8c16-e1f4ec3afb56%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: API Test account - how sandboxed and what data is available?

[Dorian Kind]

Hi Si,

you might be able to handle the scenario by using a production developer 
token, but giving your developer read-only access to the Google Ads account 
in question. That way, he'll be able to access all account data without 
risking any unwanted modifications to the setup.

Cheers,
Dorian

On Friday, 15 February 2019 10:32:39 UTC+1, Si J wrote:
>
> Hi Peter 
>
> Thanks for the reply. I've had a look at the docs, that's helpful thank 
> you. 
>
> If someone was using a test account can they still access the optimization 
> service, in particular historical search volumes per keyword using seed or 
> upload test data?
>
> Thanks,
>
> Si.
>

-- 
-- 
=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~
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.
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/907225f5-832e-4dd7-ae00-67b1a7fbf1e3%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Invalid Mobile App Id - INVALID_MOBILE_APP

[Dorian Kind]

FWIW, I also reached out to the group back in 2017 about this sort of 
placements, and was told that

"[...] these IDs may continue to appear in placement reports for a time 
> while we continue to work on cleaning up the old data. However, the invalid 
> IDs do not actually affect your targeting, and they should always come back 
> with no stats because of this."


If I understand OP correctly, not only do they still appear in the 
placement reports, they also accumulate stats now. I'd also like to 
understand how we can exclude these (AdMob?) placements.

Best,
Dorian


On Friday, 18 January 2019 16:02:00 UTC+1, PPC Developer wrote:
>
> Hi Luis,
>
> I'm well aware of the format for both iOS and Android. However, these 
> mobile application IDs are returned by AdWords via a call to get Automatic 
> Placement Performance report.. So basically, adwords is telling me that 
> these are the mobile apps that are giving us a lot of clicks. It's not me 
> trying to construct my own app ID. These are coming back from the API call 
> to adwords. And when I try to add these to exclusion lists via 
> NegativeCampaignCriteria, the API returns an error complaining about the 
> app ID format. So, it's basically AdWords returning these. 
>
> I saw another post related to this, 
> https://groups.google.com/forum/#!searchin/adwords-api/INVALID_MOBILE_APP%7Csort:date/adwords-api/WUvX2wjhz6U/Xn_x7wdMBgAJ
>
> But, what's the solution?
>
> On Friday, January 18, 2019 at 8:22:08 AM UTC, googleadsapi-forumadvisor 
> wrote:
>>
>> Hi,
>>
>> The format of the app ID that you used was invalid which triggers 
>> the CriterionError.INVALID_MOBILE_APP error. A well formed app ID for 
>> AdWords API would be "1-476943146" for iOS and "2-com.labpixies.colordrips" 
>> for Android. You may check this guide 
>> 
>>  for 
>> details. I would suggest to correct those app ID then retry your request 
>> again.
>>
>> Let me know if you still encounter any error after doing my suggestion.
>>
>> Thanks and regards,
>> Luis
>> AdWords API Team
>>
>>
>> =~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~
>> Also find us on our blog and discussion group:
>> http://googleadsdeveloper.blogspot.com/search/label/adwords_api
>> https://developers.google.com/adwords/api/community/
>> =~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~
>>
>> Was your question answered? Please rate your experience with us by taking 
>> a short survey.
>> If not -- reply to this email and tell us what else we can do to help.
>>
>> Take Survey 
>> 
>>
>> Also find us on our blog and discussion group:
>> http://googleadsdeveloper.blogspot.com/search/label/adwords_api
>> https://developers.google.com/adwords/api/community/
>> On 01/18/19 12:06:25 ppcdev...@mineeds.com wrote:
>>
>> I'm getting mobile application ID(s) via the API, and trying to add as 
>> negative or biddable criterion to another ad group. In doing so, I get 
>> exceptions:
>>
>> [CriterionError.INVALID_MOBILE_APP @ 
>> operations[103].operand.criterion.appId; 
>> trigger:'10002-CA-APP-PUB-8367418828198308', 
>> CriterionError.INVALID_MOBILE_APP @ 
>> operations[309].operand.criterion.appId; 
>> trigger:'10002-CA-APP-PUB-8392731756470098']
>>
>> And I have a lot of these, where I cannot neither add or delete them:
>> mobileapp::10002-ca-app-pub-8367418828198308
>> mobileapp::10002-ca-app-pub-8392731756470098
>> mobileapp::10002-ca-app-pub-4028238683451937
>> mobileapp::10002-ca-app-pub-8162149483502798
>> mobileapp::10002-ca-app-pub-5694554969453415
>> mobileapp::10002-ca-app-pub-1413939963884036
>> mobileapp::10002-ca-app-pub-5075118958809920
>> mobileapp::10002-ca-app-pub-2397825577270378
>> mobileapp::10002-ca-app-pub-4640908852121081
>> mobileapp::10002-ca-app-pub-3169207933671961
>> mobileapp::10002-ca-app-pub-4547683005564946
>> mobileapp::10002-ca-app-pub-9549248647599949
>> mobileapp::10002-ca-app-pub-3605354403339561
>>
>>
>> How do I add or delete these mobile apps as adgroupscriterion?
>>
>> -- 
>> -- 
>> =~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~
>> 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 

Re: Does AdService support partial failure?

[Dorian Kind]

Hi Dhanya,

thanks for your response. I take it then that the partialFailureErrors field
 of AdReturnValue does not exist, contrary to the documentation.

Best,
Dorian

On Thursday, 17 January 2019 21:53:47 UTC+1, googleadsapi-forumadvisor 
wrote:
>
> Hi Dorian,
>
> AdService does not support partialfailure. Only the services stated under 
> Partial Failure documentation in your linked doc supports partial failure.
>
> Regards,
> Dhanya, AdWords API Team
> =~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~
> Also find us on our blog and discussion group:
> http://googleadsdeveloper.blogspot.com/search/label/adwords_api
> https://developers.google.com/adwords/api/community/
> =~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~
>
> Was your question answered? Please rate your experience with us by taking 
> a short survey.
> If not -- reply to this email and tell us what else we can do to help.
>
> Take Survey 
> 
>
> Also find us on our blog and discussion group:
> http://googleadsdeveloper.blogspot.com/search/label/adwords_api
> https://developers.google.com/adwords/api/community/
>

-- 
-- 
=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~
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.
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/b7b0d326-1020-4633-ab20-3f61f1cc9ef3%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Does AdService support partial failure?

[Dorian Kind]

Hi,

according to the Partial Failure documentation 
, 
AdService is not one of the services that supports this concept. However, 
while looking at AdService's documentation 
,
 
the returned SOAP object returned does have the partialFailureErrors field, 
which seems to indicate that partial failure is indeed supported. Which one 
is correct?

Thanks for your feedback and best regards,
Dorian

-- 
-- 
=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~
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.
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/0470d206-f33d-4534-854b-e5630aa85a05%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Custom Parameters on LocationExtensions

[Dorian Kind]

Hi,

according to the documentation, all FeedItem 

 
objects have a urlCustomParameters field.
However, when trying to set a custom parameter on a feed item that has been 
mapped to a Location Extension (placeholder type 7), we get an 
OperationAccessDenied.ACTION_NOT_PERMITTED error. Is this expected 
behavior? If so, could the documentation be adapted accordingly?

Thanks and best,
Dorian

-- 
-- 
=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~
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.
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/cae03522-71d3-4c93-a59f-3c1d72020ca6%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Estimated time of arrival for Benchmark Price metrics via API?

[Dorian Kind]

Hi,

Just a thought as these types of posts pop up somewhat frequently and never 
seem to warrant a response beyond telling the OP to check the blog for 
updates: how about adding a sticky post which explains that this forum is 
not the right place to post questions about adding features or about 
timelines to availability of such features?
I'm thinking about threads such as this one 

 that's 
been going on for the better part of three years or the perennial "When are 
Video Campaigns going to be supported" posts :)

Cheers,
Dorian


On Wednesday, 5 December 2018 07:10:53 UTC+1, Dannison Yao (AdWords API 
Team) wrote:
>
> Hi Chris,
>
> Unfortunately we do not have any news yet on if and when the new price 
> benchmarks metric fields will be supported in the API. You can follow our 
> blog  to 
> be updated on new features and updates.
>
> Regards,
> Dannison
> AdWords API Team
>
> On Wednesday, December 5, 2018 at 7:10:55 AM UTC+8, norisk GmbH wrote:
>>
>> Dear Ads API Team, 
>>
>> the new price metrics are now available in the UI. Any Estimated time of 
>> arrival for the metric availability via the API? 
>> I presume this will be the SHOPPING PERFORMANCE REPORT.
>>
>> Thanks for feedback,
>> Chris
>>
>

-- 
-- 
=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~
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.
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/f177b9cd-a10a-457e-9dd5-307793b72a0d%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: AdService throws UNEXPECTED_INTERNAL_API_ERROR when filtering by AdType

[Dorian Kind]

Hi Josh,

works great now! Thanks for the quick fix.

Best regards,
Dorian

On Wednesday, 7 November 2018 15:56:03 UTC+1, Josh Radcliff (AdWords API 
Team) wrote:
>
> Hi Dorian,
>
> Thanks again for raising this issue. The fix for this is live, so you can 
> now filter by *AdType* in your *AdService* get requests. Please give it 
> another try and post back here if you encounter any issues.
>
> Cheers,
> Josh, AdWords API Team
>
> On Monday, October 22, 2018 at 12:20:26 PM UTC-4, Josh Radcliff (AdWords 
> API Team) wrote:
>>
>> Hi Dorian,
>>
>> Thanks for sending over the logs. I'm following up on the internal error 
>> and will provide an update as soon as I hear back.
>>
>> Cheers,
>> Josh, AdWords API Team
>>
>> On Monday, October 22, 2018 at 7:19:30 AM UTC-4, Dorian Kind wrote:
>>>
>>> Hi Peter,
>>>
>>> thanks for your response. I've sent the SOAP logs in a private message.
>>>
>>> Best regards,
>>> Dorian
>>>
>>> On Monday, 22 October 2018 12:42:48 UTC+2, Peter Oliquino (AdWords API 
>>> Team) wrote:
>>>>
>>>> Hi Dorian,
>>>>
>>>> Could you send your SOAP logs as well? Our team will investigate this 
>>>> and will get back to you as soon as we identify the root cause. You may 
>>>> send them privately using the *reply privately to author* option.
>>>>
>>>> Thanks and regards,
>>>> Peter
>>>> AdWords API Team
>>>>
>>>> On Monday, October 22, 2018 at 5:54:39 PM UTC+8, Dorian Kind wrote:
>>>>>
>>>>> Hi,
>>>>>
>>>>> As the title says, AdService reproducibly errors out 
>>>>> with InternalApiError.UNEXPECTED_INTERNAL_API_ERROR when using a selector 
>>>>> with a predicate that filters by AdType. For example, use the following 
>>>>> AdService selector:
>>>>>
>>>>> {
>>>>> 'predicates': [{
>>>>> 'field': 'AdType',
>>>>> 'operator': 'NOT_EQUALS',
>>>>> 'values': ['IMAGE_AD']
>>>>> }],
>>>>> 'fields': [
>>>>> 'Id'
>>>>> ],
>>>>> 'paging': {
>>>>> 'numberResults': 10
>>>>> }
>>>>> }
>>>>>
>>>>> The result has been always UNEXPECTED_INTERNAL_API_ERROR for the ~10 
>>>>> accounts that I tested. The operator in the predicate does not seem to 
>>>>> matter, as soon as you filter on AdType, the error occurs. Happy to 
>>>>> provide 
>>>>> SOAP conversations.
>>>>>
>>>>> Best regards,
>>>>> Dorian
>>>>>
>>>>>
>>>>>

-- 
-- 
=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~
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.
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/faa2170c-d051-4327-b794-bb3e172940da%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Triggering UNEXPECTED_INTERNAL_API_ERROR all day today

[Dorian Kind]

Hi Luis,

I'd love to do that, but we don't have SOAP logging turned on by default in 
production as it is incredibly verbose. If you want just any example of an 
operation that results in an UNEXPECTED_INTERNAL_API_ERROR, please see my 
other thread 
<https://groups.google.com/d/msg/adwords-api/GmWeH9AIzZE/Jw5GTFfuCAAJ>.

Best,
Dorian

On Thursday, 25 October 2018 19:25:10 UTC+2, Luis Xander Talag (AdWords API 
Team) wrote:
>
> Hello Dorian,
>
> Please provide your clientCustomerId, and complete SOAP request and 
> response logs so I can further investigate the issue. You can send it to me 
> via *Reply privately to author*.
>
> Thanks,
> Luis
> AdWords API Team
>
> On Thursday, October 25, 2018 at 8:08:56 PM UTC+8, Dorian Kind wrote:
>>
>> Hi,
>>
>> we also see an increased frequency of those today. From our experience, 
>> just retrying the request after a short waiting period almost always fixes 
>> the issue.
>>
>> Cheers,
>> Dorian
>>
>> On Thursday, 25 October 2018 00:26:05 UTC+2, lix...@2ndaddress.com wrote:
>>>
>>>
>>> Does anyone know what is going on?
>>>
>>

-- 
-- 
=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~
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.
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/0fe30c48-9c24-4f92-a9cf-1e50fff86c1a%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Update the status of a CrmBasedUserList from Closed to Open

[Dorian Kind]

We've also seen a similar thing happen (audience lists being closed for no 
apparent reason) during the last month or so, but in production accounts in 
our case. I think our business side have escalated this with a Google Ads 
account manager, but I'm not sure if there's been any sort of conclusion 
yet.

Best regards,
Dorian

On Tuesday, 23 October 2018 17:04:37 UTC+2, GregT wrote:
>
> Just wanted to chime in that this kind of thing is affecting us in our 
> test account as well. We've had audiences that we manually created years 
> ago that have remained open all this time. In our automated tests, we 
> download all audiences, expect to find some, and then use them to create ad 
> group and campaign bid modifiers (our system doesn't create/modify 
> audiences, just audience bid modifiers, so that's what we test). These 
> kinds of tests have all run without issues for years, but have started 
> failing within the last couple weeks because the audiences we download from 
> our test account have been closed. When we've gone into the Google Ads UI 
> and re-marked them as Open, they only stay that way for a few minutes to an 
> hour, which often doesn't give time for our entire test suite to run (it 
> does a lot of things, not all of which involve hitting the AdWords API).
>
> So it seems like sometime in the last couple weeks, something has changed 
> on Google's end, where audiences in test accounts used to be ignored and 
> not automatically closed, but no longer are. Could you guys please look 
> into this, and change it back to where audiences in test accounts are not 
> automatically closed?
>
> Thanks,
> Greg
>
> On Tuesday, October 23, 2018 at 6:44:49 AM UTC-5, Joana Esteves wrote:
>>
>> Hi Dannison,
>>
>> Thanks for coming back to me.
>>
>> I tried the code again, also in another audience that created after, and 
>> it didn't work for any case.
>> As we are using testing data, the audience size is < 100. Could be it a 
>> reason why the audience sets to close, and also the lifespanmember value 
>> drops from 180 to 1?
>>
>> I appreciate that an OPEN status means that the list is still populating 
>> members and can still be targeted, and if CLOSED, then the list is not 
>> being populated already and cannot be used for targeting anymore.
>> So, I have a question: Why do lists automatically *Close*, without our 
>> intervention, a little while after they are created? (Could it be due to 
>> low volumes?)
>>
>> To clarify what we're trying to achieve, we need audiences to stay *Open*, 
>> so we can keep adding recipients to them on a daily basis. How can I grant 
>> that?
>>
>> Any help with this, greatly appreciated
>>
>> Thanks,
>> Joana
>>
>> segunda-feira, 22 de Outubro de 2018 às 05:12:11 UTC+1, Dannison Yao 
>> (AdWords API Team) escreveu:
>>>
>>> Hi Joana,
>>>
>>> Your code appears to be logically correct. If recent changes have been 
>>> applied to your user list, it usually takes a while before it is reflected. 
>>> Could you try running your code again and see if the changes have been 
>>> reflected? If not, could you provide the complete SOAP request and response 
>>> logs that were generated after setting the status to *OPEN* so I could 
>>> investigate this further? You may send the requested information using the 
>>> *Reply 
>>> privately to author* option. If you have not enabled logging yet, you 
>>> may follow this guide 
>>> 
>>>  on 
>>> how to do so.
>>>
>>> According to this guide about the CrmBasedUserLIst.status 
>>> ,
>>>  
>>> if the status is *OPEN*, the list is still populating members and can 
>>> still be targeted. If it is set to *CLOSED*, then the list is not being 
>>> populated already and cannot be used for targeting anymore. From your 
>>> understanding, *client 1 *and *client 2* should be in the list, while 
>>> *client 
>>> 3* should not be in the list because it was targeted after the list was 
>>> CLOSED.
>>>
>>> Regards,
>>> Dannison
>>> AdWords API Team
>>>
>>> On Saturday, October 20, 2018 at 7:17:53 AM UTC+8, Joana Esteves wrote:

 Hi Google team,

 I'm using your API, using PHP client library, to update Customer Lists 
 daily.

 We noticed that some of the lists are closed status, checked by 
 select/query the list for it status:
 $selector->setFields(['Id', 'Name', 'Status']); 
  (...)

 var_dump($user_list->getStatus()); // CLOSED

 it returns: closed, the same status I can see on the UI.

 Then I use the code to set the OPEN status:
 if ($user_list->getStatus() === UserListMembershipStatus::CLOSED) {
   var_dump($user_list->setStatus(UserListMembershipStatus::OPEN));
   var_dump($user_list->getStatus());
 }

 immediately after set the status using this code, the 

Re: Triggering UNEXPECTED_INTERNAL_API_ERROR all day today

[Dorian Kind]

Hi,

we also see an increased frequency of those today. From our experience, 
just retrying the request after a short waiting period almost always fixes 
the issue.

Cheers,
Dorian

On Thursday, 25 October 2018 00:26:05 UTC+2, lix...@2ndaddress.com wrote:
>
>
> Does anyone know what is going on?
>

-- 
-- 
=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~
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.
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/c6fefaa5-53be-482d-b0e7-897fe9d8ac49%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: From service to JSON

[Dorian Kind]

Hi Osso,

you can use the `zeep.helpers.serialize_object` helper to convert a SOAP 
object as returned by zeep into a native dict and then turn that into JSON 
via `json.dumps`.

Cheers,
Dorian

On Thursday, 25 October 2018 09:49:33 UTC+2, Osso romain wrote:
>
> Hi 
>
> When i'm getting the datas from a service :
>
> datas = adwords_client.GetService('AdGroupAdService', 'v201809').get(
> selector)
> datas = datas['entries']
>
> print(str(datas))
>
> it will pint something like this :
>
> [{
> 'id': 1xx,
> 'campaignGroupId': None,
> 'name': '1xe',
> 'status': 'PAUSED',
> 'servingStatus': 'SERVING',
> 'startDate': 'xx',
> 'endDate': 'x0',
> 'budget': {
> 'budgetId': xx,
> 'name': 'Budget Marque',
> 'amount': {
> 'ComparableValue.Type': 'Money',
> 'microAmount': 8000
> },
> 'deliveryMethod': 'STANDARD',
> 'referenceCount': 17,
> 'isExplicitlyShared': True,
> 'status': 'ENABLED'
> },
>
> Which is not json formator xml format.
>
> So let's print the type of "datas". 
> It is a list of "zeep.objects.Campaign". I think it's a class of 
> campaigns. But how do i do to get it in XML or either json ? 
>
> There are no informations about that on the sdk .
>
> Service used : 
> https://developers.google.com/adwords/api/docs/reference/v201809/CampaignService
> Sdk : 
> https://developers.google.com/adwords/api/docs/samples/python/campaign-management
>  
>
> Thanks for your help,
>
> Regards 
> Le mercredi 24 octobre 2018 19:54:36 UTC+2, Milind Sankeshware (AdWords 
> API Team) a écrit :
>>
>> Hi Osso,
>>
>> I am afraid that you will get the data in XML format only. However, you 
>> could convert the response in XML to JSON at your end. Please find the 
>> sample 
>> examples 
>> 
>>  from 
>> the stack overflow, which might be helpful for you. Let me know if you have 
>> any further questions. 
>>
>> Thanks,
>> Milind, AdWords API Team
>>
>

-- 
-- 
=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~
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.
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/7df02a81-36bb-4e3c-95f8-d7566dadd4dd%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Change of Error Types When Attaching Bidding Strategies

[Dorian Kind]

Hi Thanet,

thanks for the update. It'd be great if the documentation 
<https://developers.google.com/adwords/api/docs/reference/v201809/AdGroupCriterionService#errors>
 
could be updated accordingly.

Best regards,
Dorian

On Wednesday, 24 October 2018 14:04:23 UTC+2, Thanet Knack Praneenararat 
(AdWords API Team) wrote:
>
> Hello Dorian,
>
> I've got confirmation that, going forward, the error message for such a 
> scenario is now *OPERATION_NOT_PERMITTED_FOR_CAMPAIGN_TYPE* instead.
>
> Best,
> Thanet, AdWords API Team
>
> On Monday, July 30, 2018 at 5:48:00 PM UTC+9, Dorian Kind wrote:
>>
>> Hi,
>>
>> we run daily integration test for our Adwords API framework. Since July 
>> 25, a couple of these tests fail because of what appears to be a change in 
>> returned error codes.
>>
>> Specifically, we try to attach a bidding strategy to an adgroup (which 
>> was possible up to v201705, but disallowed from then on), and check whether 
>> the returned error is *CANNOT_ATTACH_BIDDING_STRATEGY_TO_ADGROUP* (link 
>> to reference 
>> <https://developers.google.com/adwords/api/docs/reference/v201806/AdGroupService.BiddingErrors.Reason#CANNOT_ATTACH_BIDDING_STRATEGY_TO_ADGROUP>).
>>  
>> A second test attaches a bidding strategy to an AdGroupCriterion, which we 
>> expect to similarly fail with an 
>> *CANNOT_ATTACH_BIDDING_STRATEGY_TO_ADGROUP_CRITERIA* (link 
>> <https://developers.google.com/adwords/api/docs/reference/v201806/AdGroupService.BiddingErrors.Reason#CANNOT_ATTACH_BIDDING_STRATEGY_TO_ADGROUP_CRITERIA>
>> ).
>>
>> Both of these operations now return an 
>> *OPERATION_NOT_PERMITTED_FOR_CAMPAIGN_TYPE *error, which seems a bit 
>> confusing as the campaign in question is a regular search campaign.
>>
>> Can we expect this new error type to stay going forward, or is it an 
>> oversight that will be rolled back?
>>
>> Thanks for any feedback and best regards,
>> Dorian
>>
>

-- 
-- 
=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~
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.
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/11b81d1d-29fb-4b27-8d5a-8137cae94cfc%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Can we use AdService to update only specific parts of an ETA?

[Dorian Kind]

Hi Teja,

thanks for your response and following up with your team.

There's an interesting thing I just realized when playing around with the 
AdService. No matter which fields you actually specify in the selector, the 
service will always return a minimum set of fields. To illustrate, if you 
just list "Id" in your selector, you'll get back the following fields for 
all Ad objects:

id
url
displayUrl
finalUrls
finalMobileUrls
finalAppUrls
trackingUrlTemplate
finalUrlSuffix
urlCustomParameters
urlData
automated
type
devicePreference
systemManagedEntitySource
Ad.Type
headlinePart1
headlinePart2
headlinePart3
description
description2
path1
path2

Interestingly, up until Ad.Type, these are just the attributes of the base
 Ad type. But the following ones seem to just apply for ExpandedTextAd.
It gets stranger still, however: If you actually request an ad object of 
type ExpandedTextAd, then these extra fields are *not populated *if your 
selector just lists "Id". You'll need to explicitely include headlinePart1 
in the selector to get an actual value for that attribute, even though it's 
always included in the response. Same goes for headlinePart2 etc. I find 
this a bit confusing.

Obviously, the service would ideally always return the required/relevant 
set of attributes for the given ad type of the returned object.

Best regards,
Dorian


On Monday, 22 October 2018 18:16:34 UTC+2, Teja Makani wrote:
>
> Hello Dorlan,
>
> I am Bharani's colleague, responding on this thread as she is not 
> available. It seems like there is no workaround, you have to pass all the 
> required fields to the AdService. However, I understand your concern and 
> shared it with our team to see whether there is any simplified process. I 
> will get back to you once i get more information on this concern. 
>
> Regards,
> Sai Teja, AdWords API Team.
>
> On Wednesday, July 11, 2018 at 8:00:49 AM UTC-4, Yang Gao wrote:
>>
>> Hi, I'm trying to use AdService to update only the final url of some 
>> existing ads but I'm getting errors saying that headline and description 
>> etc are required. Is there on way to update just specific components of the 
>> ad rather than all parts of it? If so, what's the benefit of editing vs 
>> just creating an entirely new ad?
>>
>> Thanks,
>> Yang
>>
>

-- 
-- 
=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~
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.
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/2a7d54ff-0291-4b4d-b4f8-6afab61afb0e%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: AdService throws UNEXPECTED_INTERNAL_API_ERROR when filtering by AdType

[Dorian Kind]

Hi Peter,

thanks for your response. I've sent the SOAP logs in a private message.

Best regards,
Dorian

On Monday, 22 October 2018 12:42:48 UTC+2, Peter Oliquino (AdWords API 
Team) wrote:
>
> Hi Dorian,
>
> Could you send your SOAP logs as well? Our team will investigate this and 
> will get back to you as soon as we identify the root cause. You may send 
> them privately using the *reply privately to author* option.
>
> Thanks and regards,
> Peter
> AdWords API Team
>
> On Monday, October 22, 2018 at 5:54:39 PM UTC+8, Dorian Kind wrote:
>>
>> Hi,
>>
>> As the title says, AdService reproducibly errors out 
>> with InternalApiError.UNEXPECTED_INTERNAL_API_ERROR when using a selector 
>> with a predicate that filters by AdType. For example, use the following 
>> AdService selector:
>>
>> {
>> 'predicates': [{
>> 'field': 'AdType',
>> 'operator': 'NOT_EQUALS',
>> 'values': ['IMAGE_AD']
>> }],
>> 'fields': [
>> 'Id'
>> ],
>> 'paging': {
>> 'numberResults': 10
>> }
>> }
>>
>> The result has been always UNEXPECTED_INTERNAL_API_ERROR for the ~10 
>> accounts that I tested. The operator in the predicate does not seem to 
>> matter, as soon as you filter on AdType, the error occurs. Happy to provide 
>> SOAP conversations.
>>
>> Best regards,
>> Dorian
>>
>>
>>

-- 
-- 
=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~
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.
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/1a6cb3bb-b68c-41f3-8ad2-46f8d95ef44c%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

AdService throws UNEXPECTED_INTERNAL_API_ERROR when filtering by AdType

[Dorian Kind]

Hi,

As the title says, AdService reproducibly errors out 
with InternalApiError.UNEXPECTED_INTERNAL_API_ERROR when using a selector 
with a predicate that filters by AdType. For example, use the following 
AdService selector:

{
'predicates': [{
'field': 'AdType',
'operator': 'NOT_EQUALS',
'values': ['IMAGE_AD']
}],
'fields': [
'Id'
],
'paging': {
'numberResults': 10
}
}

The result has been always UNEXPECTED_INTERNAL_API_ERROR for the ~10 
accounts that I tested. The operator in the predicate does not seem to 
matter, as soon as you filter on AdType, the error occurs. Happy to provide 
SOAP conversations.

Best regards,
Dorian


-- 
-- 
=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~
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.
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/6f0032b0-5c01-4f8c-a979-f7f36bb4c185%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Can we use AdService to update only specific parts of an ETA?

[Dorian Kind]

Hi,

let me just stress how important this feature ist. We have a use case where 
we need to change the URL suffices of all ads in an account. Ideally, we'd 
download an AD_PERFORMANCE_REPORT to get all ads IDs regardless of type, 
and then just send SET operations for those IDs with the correct 
finalUrlSuffix field.
As that's not possible though, we'll need to either keep a mapping of all 
report fields to all existing fields for all ad types, or use the AdService 
to first download all ad objects with all fields, modify the finalUrlSuffix 
field and send a mutate request again. Both of these options seem not very 
efficient.

Best regards,
Dorian

On Wednesday, 11 July 2018 16:48:04 UTC+2, Bharani Cherukuri (AdWords API 
Team) wrote:
>
> Hello Yang, 
>
> With the previous versions of the API, v201802 and earlier, the Ads were 
> immutable. Using v201806, you will be able to mutate your ads without 
> losing their performance data using AdService 
> . 
> For this, you will have to add all the required fields listed here 
> .
>  
> Currently, it is not possible to update only specific elements without the 
> required fields. However, I have shared your concern with the team. Please 
> keep an eye on our blog 
>  for any 
> updates or announcements related to this feature. 
>
> Thanks,
> Bharani, AdWords API Team
>

-- 
-- 
=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~
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.
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/7ec2d575-53c1-4f45-affa-2488c6e17050%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: AdOperations and BatchJobService

[Dorian Kind]

As a follow-up, from the documentation it appears that, in contrast to 
AdGroupAdService, the AdService does not support GoalOptimizedShoppingAd.
My question would be the same, is this something that will come later?

On Monday, 22 October 2018 09:38:21 UTC+2, Dorian Kind wrote:
>
> Hi,
>
> I just noticed that AdService's AdOperations are not in the list of supported 
> operations 
> <https://developers.google.com/adwords/api/docs/guides/batch-jobs#supported_operations>
>  
> for the BatchJobService. Is this by design or something that might be 
> planned for one of the next API revisions?
>
> Thanks and best regards,
> Dorian
>

-- 
-- 
=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~
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.
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/f32d75d7-8233-48d7-b0f0-c12556ddec43%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

AdOperations and BatchJobService

[Dorian Kind]

Hi,

I just noticed that AdService's AdOperations are not in the list of supported 
operations 

 
for the BatchJobService. Is this by design or something that might be 
planned for one of the next API revisions?

Thanks and best regards,
Dorian

-- 
-- 
=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~
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.
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/05af54b5-02e7-4e3d-9aef-82f50ba39944%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Policy Checks in v201809

[Dorian Kind]

Hi Luis,

thanks for your response. I'll see if the product experts have some advice 
here.
Regarding the second part of my post, can you suggest any practices to test 
error handling? I seem to remember that a long time ago, when there was the 
Adwords API sandbox environment instead of test accounts, there used to be 
a mechanism to cause arbitrary API calls to return errors (by including 
some specific HTTP header), but I might be mistaken.

Best regards,
Dorian

On Friday, 19 October 2018 22:33:47 UTC+2, Luis Xander Talag (AdWords API 
Team) wrote:
>
> Hi Dorian,
>
> Thanks for bringing this to our attention. In the AdWords API perspective, 
> we're unsure if there were changes in the backend validation for both API 
> (from old version to latest version) and UI (from old UI to new UI) with 
> regards to handling of policy violations. I suggest to reach out to the 
> product experts via the Google Ads Community forum 
> <https://www.en.advertisercommunity.com/t5/Google-Ads/ct-p/google-ads> about 
> this as they are better equipped to provide you the right information you 
> need. 
>
> Thanks,
> Luis
> AdWords API Team
>
> On Friday, October 19, 2018 at 11:17:05 PM UTC+8, Dorian Kind wrote:
>>
>> Hi,
>>
>> we're currently updating our frameworks from v201802 to v201809 and 
>> noticed something peculiar about the new version, namely that it allows us 
>> to upload ads containing policy violations where we were denied previously. 
>> We check the correct handling of certain policy violations in our test 
>> suite, and were surprised to see these tests fail because no policy 
>> violation error was returned.
>>
>> As an example, any ads containing the word "cigar" in the ad copy caused 
>> a *AdPolicyError.POLICY_ERROR* to be returned in v201802, whereas in 
>> v201809 that same ad can be created just fine. I suppose it would later 
>> still be disapproved after review, but this is still a quite significant 
>> change in how policy violations are handled.
>>
>> Interestingly enough, in the old Google Ads web interface it's also *not* 
>> *possible* to save an ad containing the word "cigar", while in the new 
>> interface no error is thrown and the text ad is created.
>>
>> Is this expected behavior? If so, are there any recommendations how to 
>> test the correct handling of policy violations going forward?
>>
>> Thanks and best regards,
>> Dorian
>>
>

-- 
-- 
=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~
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.
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/4bf251ba-f347-4cc1-aa00-15d6fef8d748%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Policy Checks in v201809

[Dorian Kind]

Hi,

we're currently updating our frameworks from v201802 to v201809 and noticed 
something peculiar about the new version, namely that it allows us to 
upload ads containing policy violations where we were denied previously. We 
check the correct handling of certain policy violations in our test suite, 
and were surprised to see these tests fail because no policy violation 
error was returned.

As an example, any ads containing the word "cigar" in the ad copy caused a 
*AdPolicyError.POLICY_ERROR* to be returned in v201802, whereas in v201809 
that same ad can be created just fine. I suppose it would later still be 
disapproved after review, but this is still a quite significant change in 
how policy violations are handled.

Interestingly enough, in the old Google Ads web interface it's also *not* 
*possible* to save an ad containing the word "cigar", while in the new 
interface no error is thrown and the text ad is created.

Is this expected behavior? If so, are there any recommendations how to test 
the correct handling of policy violations going forward?

Thanks and best regards,
Dorian

-- 
-- 
=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~
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.
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/21406186-2aa8-4651-80e3-97b48de35100%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: AppId with strange platform code?

[Dorian Kind]

Hi Nadine,

thanks a lot for your quick reply! I noticed that it's not yet possible to 
use this format over the API—I got a CriterionError.INVALID_MOBILE_APP 
error. Can we expect Windows Store apps to be supported it one of the 
upcoming API revisions?

Cheers,
Dorian

On Friday, 31 August 2018 16:28:31 UTC+2, Nadine Sundquist (AdWords API 
Team) wrote:
>
> Hello Dorian,
>
> The 3 after mobileapp indicates that it's from the Windows store. I don't 
> see it that often myself, but I think it's cool that your business is 
> growing enough to start picking up even more platforms. Congrats!
>
> Cheers,
> Nadine, AdWords API Team
>
> On Friday, August 31, 2018 at 8:57:21 AM UTC-4, Dorian Kind wrote:
>>
>> Hi,
>>
>> sorry for bringing this old thread back to life, but I just stumbled over 
>> mobile apps whose platform code is none of the above, but *3*. As an 
>> example:
>>
>> *mobileapp::3-6a12c4cf-5681-4db2-a433-7aaa063aab35*
>>
>> Is there any information about what this platform code corresponds to?
>>
>> Thanks and best regards,
>> Dorian
>>
>>
>> On Monday, 11 January 2016 21:25:30 UTC+1, Nadine Sundquist (AdWords API 
>> Team) wrote:
>>>
>>> Hi Berry,
>>>
>>> Thanks for sending over the additional information. I'm posting the 
>>> answer publicly rather than directly to you to help other people who may 
>>> see this. Here's the mapping.
>>>
>>>- *mobileapp::10001- *iOS apps with either very long or 
>>>empty app IDs
>>>- *mobileapp::10002- *Google Play apps with either very 
>>>long or empty app IDs
>>>
>>> As far as I can tell, this case doesn't happen very often.
>>>
>>> Cheers,
>>> Nadine, AdWords API Team
>>>
>>> On Thursday, January 7, 2016 at 8:06:38 AM UTC-5, Berry wrote:
>>>>
>>>> Hi,
>>>>
>>>> In the URL performance report i'm getting some entries with field 'URL' 
>>>> that start with "mobileapp::10001-...".
>>>> From the documentation, the platform codes should be either 1 (iOS) or 
>>>> 2 (Android).Which platform do these apps belong to?
>>>> These entries are not present in the UI.
>>>>
>>>> Thanks
>>>>
>>>>

-- 
-- 
=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~
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.
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/f72aee10-9f16-4ac2-a04b-da9675533ab1%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: AppId with strange platform code?

[Dorian Kind]

Hi,

sorry for bringing this old thread back to life, but I just stumbled over 
mobile apps whose platform code is none of the above, but *3*. As an 
example:

*mobileapp::3-6a12c4cf-5681-4db2-a433-7aaa063aab35*

Is there any information about what this platform code corresponds to?

Thanks and best regards,
Dorian


On Monday, 11 January 2016 21:25:30 UTC+1, Nadine Sundquist (AdWords API 
Team) wrote:
>
> Hi Berry,
>
> Thanks for sending over the additional information. I'm posting the answer 
> publicly rather than directly to you to help other people who may see this. 
> Here's the mapping.
>
>- *mobileapp::10001- *iOS apps with either very long or empty 
>app IDs
>- *mobileapp::10002- *Google Play apps with either very long 
>or empty app IDs
>
> As far as I can tell, this case doesn't happen very often.
>
> Cheers,
> Nadine, AdWords API Team
>
> On Thursday, January 7, 2016 at 8:06:38 AM UTC-5, Berry wrote:
>>
>> Hi,
>>
>> In the URL performance report i'm getting some entries with field 'URL' 
>> that start with "mobileapp::10001-...".
>> From the documentation, the platform codes should be either 1 (iOS) or 2 
>> (Android).Which platform do these apps belong to?
>> These entries are not present in the UI.
>>
>> Thanks
>>
>>

-- 
-- 
=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~
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.
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/b1214d60-3795-4935-a9a2-7d1438d69e0f%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Account labels in API are not correct

[Dorian Kind]

Hi,

something to be aware of is that account labels are associated with a 
specific client manager account. The same account will appear to have 
different labels depending on which MCC account ID you provide for the call 
to the ManagedCustomerService.
Just in case that might be the cause of the observed behavior.

Cheers,
Dorian

On Tuesday, 28 August 2018 09:25:35 UTC+2, Oliver wrote:
>
> We use *ManagedCustomer.accountLabels* to retireve the account lables for 
> all accounts in a hierarchy of an MCC together with all its sub MCCs.
>
> The account labels returned for the sub MCCs do not match the labels those 
> accounts actually have.  This issue seems to happen only for the sub MCCs.
>
> Any ideas what the reason could be?
>
> Oliver
>

-- 
-- 
=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~
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.
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/13e763c6-c66a-4188-a1ee-d0ae62c93c42%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Change of Error Types When Attaching Bidding Strategies

[Dorian Kind]

Hi Peter,

thanks for your response and please excuse the rather unfortunate way my 
messages were structured. You understand correctly that the described 
behavior is existing in v201802 for us. I will send you a SOAP conversation 
in a private reply.

Best,
Dorian

On Monday, 30 July 2018 12:39:36 UTC+2, Peter Oliquino (AdWords API Team) 
wrote:
>
> Hi Dorian,
>
> Could you confirm if you still require assistance? It may be worth noting 
> that in the release notes of v201806 
> <https://developers.google.com/adwords/api/docs/reference/release-notes/v201806#bidding>,
>  
> MANUAL_CPM is no longer allowed to be applied to search campaigns and a 
> specific error message has been defined if this was being applied directly 
> to the said campaign.
>
> However, since you are using the v201802 
> <https://developers.google.com/adwords/api/docs/reference/release-notes/v201802#bidding>,
>  
> the above mentioned changes in bidding should not yet be applicable. If 
> anything is still unclear, you may send to me the complete SOAP request and 
> response should you need that we look into this further and you may reply 
> using the *Reply privately to author* option.
>
> Thanks and regards,
> Peter
> AdWords API Team
>
> On Monday, July 30, 2018 at 5:22:10 PM UTC+8, Dorian Kind wrote:
>>
>> Just to clarify, the change in error codes was with v201802 both before 
>> and after. Sorry for the ambiguity below.
>>
>> On Monday, 30 July 2018 11:19:41 UTC+2, Dorian Kind wrote:
>>>
>>> FWIW, I just noticed that the described change in error codes coincided 
>>> exactly with the sunset date of API v201710. We currently use v201802.
>>>
>>> On Monday, 30 July 2018 10:48:00 UTC+2, Dorian Kind wrote:
>>>>
>>>> Hi,
>>>>
>>>> we run daily integration test for our Adwords API framework. Since July 
>>>> 25, a couple of these tests fail because of what appears to be a change in 
>>>> returned error codes.
>>>>
>>>> Specifically, we try to attach a bidding strategy to an adgroup (which 
>>>> was possible up to v201705, but disallowed from then on), and check 
>>>> whether 
>>>> the returned error is *CANNOT_ATTACH_BIDDING_STRATEGY_TO_ADGROUP* (link 
>>>> to reference 
>>>> <https://developers.google.com/adwords/api/docs/reference/v201806/AdGroupService.BiddingErrors.Reason#CANNOT_ATTACH_BIDDING_STRATEGY_TO_ADGROUP>).
>>>>  
>>>> A second test attaches a bidding strategy to an AdGroupCriterion, which we 
>>>> expect to similarly fail with an 
>>>> *CANNOT_ATTACH_BIDDING_STRATEGY_TO_ADGROUP_CRITERIA* (link 
>>>> <https://developers.google.com/adwords/api/docs/reference/v201806/AdGroupService.BiddingErrors.Reason#CANNOT_ATTACH_BIDDING_STRATEGY_TO_ADGROUP_CRITERIA>
>>>> ).
>>>>
>>>> Both of these operations now return an 
>>>> *OPERATION_NOT_PERMITTED_FOR_CAMPAIGN_TYPE *error, which seems a bit 
>>>> confusing as the campaign in question is a regular search campaign.
>>>>
>>>> Can we expect this new error type to stay going forward, or is it an 
>>>> oversight that will be rolled back?
>>>>
>>>> Thanks for any feedback and best regards,
>>>> Dorian
>>>>
>>>

-- 
-- 
=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~
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.
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/a789c078-b126-4c8c-aab0-a06d8b2bca11%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Change of Error Types When Attaching Bidding Strategies

[Dorian Kind]

Just to clarify, the change in error codes was with v201802 both before and 
after. Sorry for the ambiguity below.

On Monday, 30 July 2018 11:19:41 UTC+2, Dorian Kind wrote:
>
> FWIW, I just noticed that the described change in error codes coincided 
> exactly with the sunset date of API v201710. We currently use v201802.
>
> On Monday, 30 July 2018 10:48:00 UTC+2, Dorian Kind wrote:
>>
>> Hi,
>>
>> we run daily integration test for our Adwords API framework. Since July 
>> 25, a couple of these tests fail because of what appears to be a change in 
>> returned error codes.
>>
>> Specifically, we try to attach a bidding strategy to an adgroup (which 
>> was possible up to v201705, but disallowed from then on), and check whether 
>> the returned error is *CANNOT_ATTACH_BIDDING_STRATEGY_TO_ADGROUP* (link 
>> to reference 
>> <https://developers.google.com/adwords/api/docs/reference/v201806/AdGroupService.BiddingErrors.Reason#CANNOT_ATTACH_BIDDING_STRATEGY_TO_ADGROUP>).
>>  
>> A second test attaches a bidding strategy to an AdGroupCriterion, which we 
>> expect to similarly fail with an 
>> *CANNOT_ATTACH_BIDDING_STRATEGY_TO_ADGROUP_CRITERIA* (link 
>> <https://developers.google.com/adwords/api/docs/reference/v201806/AdGroupService.BiddingErrors.Reason#CANNOT_ATTACH_BIDDING_STRATEGY_TO_ADGROUP_CRITERIA>
>> ).
>>
>> Both of these operations now return an 
>> *OPERATION_NOT_PERMITTED_FOR_CAMPAIGN_TYPE *error, which seems a bit 
>> confusing as the campaign in question is a regular search campaign.
>>
>> Can we expect this new error type to stay going forward, or is it an 
>> oversight that will be rolled back?
>>
>> Thanks for any feedback and best regards,
>> Dorian
>>
>

-- 
-- 
=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~
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.
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/f63f254a-605d-49b9-8477-0c41ebbc7338%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Change of Error Types When Attaching Bidding Strategies

[Dorian Kind]

FWIW, I just noticed that the described change in error codes coincided 
exactly with the sunset date of API v201710. We currently use v201802.

On Monday, 30 July 2018 10:48:00 UTC+2, Dorian Kind wrote:
>
> Hi,
>
> we run daily integration test for our Adwords API framework. Since July 
> 25, a couple of these tests fail because of what appears to be a change in 
> returned error codes.
>
> Specifically, we try to attach a bidding strategy to an adgroup (which was 
> possible up to v201705, but disallowed from then on), and check whether the 
> returned error is *CANNOT_ATTACH_BIDDING_STRATEGY_TO_ADGROUP* (link to 
> reference 
> <https://developers.google.com/adwords/api/docs/reference/v201806/AdGroupService.BiddingErrors.Reason#CANNOT_ATTACH_BIDDING_STRATEGY_TO_ADGROUP>).
>  
> A second test attaches a bidding strategy to an AdGroupCriterion, which we 
> expect to similarly fail with an 
> *CANNOT_ATTACH_BIDDING_STRATEGY_TO_ADGROUP_CRITERIA* (link 
> <https://developers.google.com/adwords/api/docs/reference/v201806/AdGroupService.BiddingErrors.Reason#CANNOT_ATTACH_BIDDING_STRATEGY_TO_ADGROUP_CRITERIA>
> ).
>
> Both of these operations now return an 
> *OPERATION_NOT_PERMITTED_FOR_CAMPAIGN_TYPE *error, which seems a bit 
> confusing as the campaign in question is a regular search campaign.
>
> Can we expect this new error type to stay going forward, or is it an 
> oversight that will be rolled back?
>
> Thanks for any feedback and best regards,
> Dorian
>

-- 
-- 
=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~
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.
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/4e8f14a7-1493-49e3-aae5-df818fa84067%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Change of Error Types When Attaching Bidding Strategies

[Dorian Kind]

Hi,

we run daily integration test for our Adwords API framework. Since July 25, 
a couple of these tests fail because of what appears to be a change in 
returned error codes.

Specifically, we try to attach a bidding strategy to an adgroup (which was 
possible up to v201705, but disallowed from then on), and check whether the 
returned error is *CANNOT_ATTACH_BIDDING_STRATEGY_TO_ADGROUP* (link to 
reference 
).
 
A second test attaches a bidding strategy to an AdGroupCriterion, which we 
expect to similarly fail with an 
*CANNOT_ATTACH_BIDDING_STRATEGY_TO_ADGROUP_CRITERIA* (link 

).

Both of these operations now return an 
*OPERATION_NOT_PERMITTED_FOR_CAMPAIGN_TYPE *error, which seems a bit 
confusing as the campaign in question is a regular search campaign.

Can we expect this new error type to stay going forward, or is it an 
oversight that will be rolled back?

Thanks for any feedback and best regards,
Dorian

-- 
-- 
=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~
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.
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/550fdff5-d8b1-4d53-985b-bf64940c258c%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Open Weather API data in banner

[Dorian Kind]

AFAIK you can't load any external assets or code at all, apart from those 
explicitely specified 
here: https://support.google.com/adwords/answer/1722096 (section "All other 
HTML5 ads" -> "Upload requirements"). So I think what you are describing is 
not possible on the GDN.

On Tuesday, 15 May 2018 23:31:12 UTC+2, R wrote:
>
> Hi,
>
> We need to make a HTML display banner for the GDN network. And we would 
> like to make use of the data from the OpenWeater api: 
> https://openweathermap.org/api. We would like to display the current 
> temperature in our banner. Do you know if it's possible to make a call to 
> the api?
>

-- 
-- 
=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~
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.
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/6925541b-cbc1-4d8e-ad4d-aa3ca3eca24b%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: throwing DetailedReportDownloadResponseException with 400 Response code.

[Dorian Kind]

Hi Josh,

any updates on this topic? Can we just retry downloads that fail with this 
specific error condition (400 HTTP status code and no response content) for 
the time being?

Thanks for your feedback and best regards,
Dorian

On Monday, 23 April 2018 14:52:50 UTC+2, Josh Radcliff (AdWords API Team) 
wrote:
>
> Hi Ron,
>
> Thanks for getting back to me. I think we have enough examples now to 
> track this down. The eng team is making progress, but I don't have any 
> updates to report just yet. I'll reply back as soon as I have more info.
>
> Cheers,
> Josh, AdWords API Team
>
> On Monday, April 23, 2018 at 4:16:20 AM UTC-4, Ronald Findling wrote:
>>
>> Taking into account the daylight savings we currently have UTC+2.
>> Concerning the 502 unfortionately I don't have the logs at hand any more 
>> -- but what I remember was an 502 which resulted in a 400 in our usage of 
>> the library.
>>
>> Best Regards,
>> Ron
>>
>> Am Montag, 16. April 2018 23:01:11 UTC+2 schrieb Josh Radcliff (AdWords 
>> API Team):
>>>
>>> Also, I forgot to ask: is that timestamp in CST?
>>>
>>> Thanks,
>>> Josh, AdWords API Team
>>>
>>> On Monday, April 16, 2018 at 4:59:35 PM UTC-4, Josh Radcliff (AdWords 
>>> API Team) wrote:

 Hi Ron,

 I'm a little perplexed by the most recent example. I see it shows both:

 com.google.api.ads.adwords.lib.utils.ReportException: *502*: Bad 
 Gateway

 and:

 Caused by: HTTP Response Code: *400*

 Was that a bad copy/paste, or are you actually seeing both 502 and 400 
 mentioned within the same error?

 Thanks,
 Josh, AdWords API Team

 On Monday, April 16, 2018 at 11:27:53 AM UTC-4, Ronald Findling wrote:
>
> After adding some more logging, another example that results in a 400 
> on our side:
>
>
> 19:07:52 [WARN] c.g.a.a.a.lib.utils.report_download Request made: 
> Service: reportdownload Method: POST clientCustomerId: XXX URL: 
> https://adwords.google.com//api/adwords/reportdownload/v201710 Request 
> ID: null ResponseTime(ms): null OperationsCount: null IsFault: true 
> FaultMessage: com.google.api.ads.adwords.lib.utils.ReportException: 502: 
> Bad Gateway
> 2018-04-15 19:07:52 [INFO] c.g.a.a.a.lib.utils.report_download HTTP 
> request:
> accept-encoding: [gzip]
> authorization: REDACTED
> user-agent: [XXX (AwApi-Java, Common-Java/3.12.0, Java/1.8.0_121, 
> maven, ReportDownloader)]
> developertoken: REDACTED
> clientcustomerid: XXX
> includezeroimpressions: false
>
> Content:
> __rdquery: SELECT Conversions,ConversionValue FROM 
> SHOPPING_PERFORMANCE_REPORT WHERE CountryCriteriaId = 2250 DURING 
> 20180316,20180415
> __fmt: XML
>
> Caused by: HTTP Response Code: 400 at 
> com.google.api.ads.adwords.lib.utils.v201710.DetailedReportDownloadResponseException$Builder.build(DetailedReportDownloadResponseException.java:35)
>
> Am Freitag, 30. März 2018 15:15:38 UTC+2 schrieb Josh Radcliff 
> (AdWords API Team):
>>
>> Hi Ron,
>>
>> Sorry, I'm still having trouble locating those requests in our logs. 
>> Would you mind sending over the customer ID where your developer token 
>> is 
>> registered? You can send it only to me by clicking *Reply privately 
>> to author*.
>>
>> Regarding the timeout theory, the ReportDownloader won't 
>> automatically retry requests. However, if you think timeouts are the 
>> root 
>> cause here, you can adjust the timeout for report downloads 
>> programmatically or in your *ads.properties* file. Check out this 
>> section of the ads.properties file 
>> 
>>  for 
>> details.
>>
>> Thanks,
>> Josh, AdWords API Team
>>
>> On Wednesday, March 28, 2018 at 8:10:33 AM UTC-4, Ronald Findling 
>> wrote:
>>>
>>> Hi Josh,
>>>
>>> I checked the request data that I provided you and they are exactly 
>>> what I can see in my logs. Maybe I should mention that the provided 
>>> time is 
>>> the time at which the request failed not when it was sent to your 
>>> servers 
>>> (that time is ~30-40 seconds before).
>>>
>>> Concerning the thread-safety recommendations I'm sure that the 
>>> ReportDownloader and its Session are not used in multiple threads in 
>>> our 
>>> code.
>>>
>>> Further information: 
>>> Checking our errors I found an interesting pattern, failing requests 
>>> always take at least 30 seconds (usually 30-31) while successful ones 
>>> are 
>>> most likely to be around 1 second.
>>>
>>> Maybe a stupid thought but could it be a something like the 
>>> java-library timing out after 30 seconds and retrying using the 
>>> provided 
>>> 

Re: Reporting API gives more and more BadRequest (400) responses

[Dorian Kind]

See also this thread 
. We 
are hit by these errors at a rate of about one in every couple of thousand 
requests. As far as I can see, we first encountered this end of December 
2017. From our end, it doesn't seem that the frequency is increasing much, 
but of course the sample size isn't terribly large.

Cheers,
Dorian

On Wednesday, 11 April 2018 21:41:40 UTC+2, Sreelakshmi Sasidharan (AdWords 
API Team) wrote:
>
> Hi Zweitze, 
>
> I can confirm that the report definitions that you have shared is valid 
> and not expected to return the HTTP 400 error code. I will let the team 
> know about this and investigate it at our end. I will keep you posted on 
> the updates. 
>
> Thanks,
> Sreelakshmi, 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/8e3b3c79-2e80-4d2b-b438-25c845642868%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Unsupported Content Label Exclusions

[Dorian Kind]

Hi all,

currently there's a number of content label exclusions that can be set in 
the Web UI, but are returned with ContentLabelType "UNKNOWN" and thus 
cannot be added to a campaign or account using the API. As far as I can 
see, the following content labels are affected:

"Content suitable for families": Returned as a single criterion with 
"UNKOWN" type
"Sensitive social issues": Returned as two separate criteria, both with 
type "UNKNOWN"
"Tragedy and conflict": Returned as two separate criteria types, one being 
"TRAGEDY" and one "UNKNOWN"

What's interesting about the last case is that when you add the "TRAGEDY" 
criterion on the account level, the "Tragedy and conflict" checkbox in the 
web UI is checked, even without adding the second "UNKNOWN" criterion 
(which is of course impossible anyway).
Could it be that the second "UNKNOWN" criterion in that scenario refers to 
the no longer available "CONFLICT" content label?

As for the first two cases, when can we expect to be able to set these 
exclusions over the API? Or are these referring to obsolete content labels 
as well?

Thanks for your feedback and best regards,
Dorian

-- 
-- 
=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~
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/8fdac51b-99b9-4aa7-833f-570a29caa566%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: throwing DetailedReportDownloadResponseException with 400 Response code.

[Dorian Kind]

Hi all,

I thought I posted previously in this thread, but it looks like my message 
has been deleted. I just wanted to chime in that we've also been seeing 
these sporadic report failures that return a HTTP 400 status code and no 
reponse content. They don't seem to be reproducible, from what we can tell 
and are most likely not the result of an expired OAuth token or a malformed 
report definition as both of these cases give detailed error messages.
We don't feel comfortable automatically retrying report download requests 
for error codes below 500, so it'd be great if the Adwords team could shed 
some light on the issue.

Thanks and best regards,
Dorian

On Friday, 30 March 2018 15:15:38 UTC+2, Josh Radcliff (AdWords API Team) 
wrote:
>
> Hi Ron,
>
> Sorry, I'm still having trouble locating those requests in our logs. Would 
> you mind sending over the customer ID where your developer token is 
> registered? You can send it only to me by clicking *Reply privately to 
> author*.
>
> Regarding the timeout theory, the ReportDownloader won't automatically 
> retry requests. However, if you think timeouts are the root cause here, you 
> can adjust the timeout for report downloads programmatically or in your 
> *ads.properties* file. Check out this section of the ads.properties file 
> 
>  for 
> details.
>
> Thanks,
> Josh, AdWords API Team
>
> On Wednesday, March 28, 2018 at 8:10:33 AM UTC-4, Ronald Findling wrote:
>>
>> Hi Josh,
>>
>> I checked the request data that I provided you and they are exactly what 
>> I can see in my logs. Maybe I should mention that the provided time is the 
>> time at which the request failed not when it was sent to your servers (that 
>> time is ~30-40 seconds before).
>>
>> Concerning the thread-safety recommendations I'm sure that the 
>> ReportDownloader and its Session are not used in multiple threads in our 
>> code.
>>
>> Further information: 
>> Checking our errors I found an interesting pattern, failing requests 
>> always take at least 30 seconds (usually 30-31) while successful ones are 
>> most likely to be around 1 second.
>>
>> Maybe a stupid thought but could it be a something like the java-library 
>> timing out after 30 seconds and retrying using the provided 
>> session/ReportDownloader again which then violates the threadSafety and 
>> results in invalid requests?
>>
>> Best Regards,
>> Ron
>>
>>
>> Am Dienstag, 27. März 2018 23:05:31 UTC+2 schrieb Josh Radcliff (AdWords 
>> API Team):
>>>
>>> Hi Ronald,
>>>
>>> I searched the logs on our side and could not find either of those 
>>> requests. Are you sure that they were submitted for the account ID you 
>>> mentioned?
>>>
>>> By the way, did you check if you're adhering to the thread safety 
>>> guidelines I mentioned earlier? I just want to make sure we can rule that 
>>> out as a possible cause of the errors.
>>>
>>> Thanks,
>>> Josh, AdWords API Team
>>>
>>> On Tuesday, March 27, 2018 at 9:53:11 AM UTC-4, Ronald Findling wrote:

 Hi Josh,

 thx for the hints.
 Concerning the requested information I can give you 2 identical request 
 where one succeeded and the other one failed with a 400 as shown in my 
 last 
 message.

 failed:
 time: 27.03.18 01:06:08 CEST
 googleAdwordsAccountId: 685-366-2732
 SELECT Conversions,ConversionValue FROM SHOPPING_PERFORMANCE_REPORT 
 WHERE CountryCriteriaId = 2826 DURING 20180225,20180327;

 succeeded:
 time: 27.03.18 03:06:30 CEST
 googleAdwordsAccountId: 685-366-2732
 SELECT Conversions,ConversionValue FROM SHOPPING_PERFORMANCE_REPORT 
 WHERE CountryCriteriaId = 2826 DURING 20180225,20180327;

 Best Regards, Ron

 Am Dienstag, 20. März 2018 21:54:13 UTC+1 schrieb Josh Radcliff 
 (AdWords API Team):
>
> Hi Raneen,
>
> From our logs, it appears that your requests are most frequently 
> failing with the following errors:
>
>- ReportDefinitionError.CUSTOMER_SERVING_TYPE_REPORT_MISMATCH
>- AuthorizationError.USER_PERMISSION_DENIED
>- ReportDefinitionError.INVALID_FIELD_NAME_FOR_REPORT
>
> Could you share a report request that failed, with any sensitive 
> information removed (developer token, OAuth access token, etc.)?
>
> Also, I see that you are using the client library for Java. Are you 
> adhering to the thread-safety recommendations 
> ? 
> For example, you should not use a *ReportDownloader* instance within 
> multiple threads. Doing so will produce unpredictable behavior, such as 
> malformed requests or issues parsing responses.
>
> Thanks,
> Josh, AdWords API Team
>
> On Tuesday, March 20, 2018 at 3:06:14 PM UTC-4, Sreelakshmi Sasidharan 
> (AdWords API Team) wrote:

Re: throwing DetailedReportDownloadResponseException with 400 Response code.

[Dorian Kind]

Hi,

FWIW, we've also noticed these intermittent 400 Bad Request errors when 
downloading reports. We have not seen these specific failures before.
>From what I can tell in our case, they do not seem to be related to OAuth2 
access token issues as those fail with a message of 
"AuthenticationError.OAUTH_TOKEN_INVALID", while the observed errors do not 
seem to have a response body. I don't think that the report definition is 
faulty, either, as the requests are correctly processed when we retry them.

Best regards,
Dorian

On Tuesday, 20 March 2018 09:10:42 UTC+1, Ronald Findling wrote:
>
> Hi Raneen,
>
> we face a similar issue for some months now observing requests 
> sporadically failing with 400 Bad Request.
> Our versions:
> 201702 version of the AdWords API
> https://github.com/googleads/googleads-java-lib 3.12
>
> The related log part:
> 2018-03-19 01:21:15 [WARN] c.g.a.a.a.lib.utils.report_download Request 
> made: Service: reportdownload Method: POST clientCustomerId: 125-142-3890 
> URL: https://adwords.google.com//api/adwords/reportdownload/v201710 
> Request ID: null ResponseTime(ms): null OperationsCount: null IsFault: true 
> FaultMessage: com.google.api.ads.adwords.lib.utils.ReportException: 400: 
> Bad Request
> 2018-03-19 01:21:15 [ERROR] c.g.a.a.a.l.c.A.soapXmlLogger Couldn't 
> process XML into a Document
>
> Best Regards,
> Ron
>
> Am Mittwoch, 10. Januar 2018 11:25:23 UTC+1 schrieb raneenb...@gmail.com:
>>
>> Hi Anash,
>> the failure also happen with other reports.
>> we think that the problem happen because of that the 
>> AdWordsSession expired .
>>  we have checked in the documentation  which error returned if the 
>> AdWordsSession expired .
>> can you please confirm that we got 400 if the session expired .
>>
>> Thanks,
>> Raneen.
>>
>>
>> On Friday, January 5, 2018 at 4:28:11 PM UTC+2, Anash P. Oommen (AdWords 
>> API Team) wrote:
>>>
>>> Hi Raneen,
>>>
>>> This looks to me as a combination of two issues - a server issue that's 
>>> occasionally sending 400 responses, and the client library not being able 
>>> to handle it correctly.
>>>
>>> For the first part, could you turn on logging and capture a failing 
>>> request? The instructions are here: 
>>> https://github.com/googleads/googleads-java-lib/wiki/Logging. Once you 
>>> have the logs, share it with me using the "Reply privately to author" and 
>>> I'll ask the reporting team to respond.
>>>
>>> For the second part, file an issue with the Java client library here: 
>>> https://github.com/googleads/googleads-java-lib/issues. You'd want to 
>>> post a redacted version of the log you are sharing with me privately.
>>>
>>> Cheers
>>> Anash P. Oommen,
>>> AdWords API Team.
>>>
>>>
>>> On Thursday, January 4, 2018 at 6:37:05 AM UTC-5, Raneen Bsais wrote:

 Hi Peter,
 this error not always reprduce , we didn't catch this excption by 
 debugging , it happens sometiems for our clients ,
 and even after the client try again the issue desapper.
 the main problem that the issue happen and if try it not happen . 

 Regards,
 Raneen.


 On Thursday, January 4, 2018 at 7:56:51 AM UTC+2, Peter Oliquino wrote:
>
> Hi Raneen,
>
> Thank you for sending the requested information. Upon trying out your 
> report and by also using the 201702 version of the AdWords API, I was 
> able 
> to successfully generate it on my end and did not encounter the error 
> 400. 
> This being said, could you confirm if you are still encountering the 
> issue?
>
> Best regards,
> Peter
> AdWords API Team
>


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

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

Re: MUTATE_ACTION_NOT_PERMITTED_FOR_CLIENT given by CampaignSharedSetService for Video Campaign

[Dorian Kind]

Hi Sreelakshmi,

sorry to revive this old thread, but just as a heads-up: the documentation 
of the MUTATE_ACTION_NOT_PERMITTED_FOR_CLIENT error still does not seem to 
cover the case mentioned above (trying to attach a shared list to a video 
campaign).

Cheers,
Dorian

On Wednesday, 7 June 2017 17:45:11 UTC+2, Sreelakshmi Sasidharan (AdWords 
API Team) wrote:
>
> Hi Dorain, 
>
> I was able to reproduce the error specific to the 
> CampaignSharedSetService. It looks like the API documentation of this 
> 
>  error 
> needs update to address this specific case. I will pass on this information 
> to the team and request them to get the docs updated. 
>
> Regarding setting custom URL parameters in a Video Campaign, would you be 
> able to share the campaignId, AdGroupId and the AdId in which you were able 
> to set the custom URL parameter via the API? I tried this scenario on an 
> ExpandedTextAd and it failed with the error 
> 'OperationAccessDenied.OPERATION_NOT_PERMITTED_FOR_CAMPAIGN_TYPE' which is 
> the expected behavior.
>
> Thanks,
> Sreelakshmi, 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/bab41fc9-5754-439d-a4b4-d50433ebfb2d%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: How do I stop an API making automatic changes to my campaigns?

[Dorian Kind]

Just as a FYI, that account is associated with the DoubleClick suite. The 
mentioned Adwords account is most likely being managed in DoubleClick 
Search. It's hard to fathom why they wouldn't use a more telling email 
address, but there you go.

Best regards,
Dorian

On Tuesday, 6 March 2018 11:16:36 UTC+1, ashle...@gmail.com wrote:
>
> Hello, 
>
> I have noticed that within the change history of my clients campaign, 
> there are consistent CPC increases daily. The email address making these 
> changes is - ds3api...@gmail.com 
>
>
> After contacting AdWords support, because its an API issue, the guy on the 
> phone couldn't help me. However he did say that someone has previously 
> added code in order for these changes to occur. Whoever has added this has 
> since left so there is no way of finding out exactly how they were added. 
> Is there anyway of removing this? 
>
> Many thanks! 
>
> Ashley 
>

-- 
-- 
=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~
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/70fbe859-99aa-494d-98e3-94179501%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Structure Report for CustomerNegativeCriterion

[Dorian Kind]

Hi Bharani,

thanks for your response. I understand there's a number of reports for 
campaign level negative criteria, however I am interested in the 
account/customer level ones.
Also, I'm a bit surprised you mention Shared Sets, as from what I can tell 
they don't support CustomerNegativeCriterion. Can you clarify?

Best regards,
Dorian

On Monday, 26 February 2018 20:42:49 UTC+1, Bharani Cherukuri (AdWords API 
Team) wrote:
>
> Hi Dorian, 
>
> There are several report types that you could use to retrieve the campaign 
> level negative criteria. You may use Campaign Negative Placements 
> Performance Report 
> 
> , Campaign Negative Keywords Performance Report 
> 
>  and Campaign Negative Locations Report 
> 
>  to 
> retrieve the excluded placement, keywords and locations information. 
>
> To retrieve the account level negative criteria, it is currently not 
> possible using API reports. You will need to use the 
> CustomerNegativeCriterionService 
> 
>  or 
> use Shared sets 
> 
>  to 
> manage this criteria.
>
> Let me know if you have any other questions. 
>
> Regards,
> Bharani, 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/f12b8c34-f765-4b17-afe2-3a2b917dcda7%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Structure Report for CustomerNegativeCriterion

[Dorian Kind]

Hi,

since API version 201710 there is the possibility to add negative criteria 
on the account level via the CustomerNegativeCriterionService. As there can 
be up to 65,000 of these negative criteria, I was a bit surprised to find 
that apparently there is no structure report that can be used to determine 
which negative placements already are set on an account in order to not 
upload these again.

So it appears that we'll have to use the CustomerNegativeCriterionService 
in order to retrieve the list of existing CustomerNegativeCriterion 
instances, but this is not necessarily straightforward because of the page 
size limit of 10'000 entries and the fact that there is no obvious way of 
segmenting the result (you obviously cannot fetch them separately by 
campaign or ad group ID, for example). Taking that into account, I was 
wondering whether we should just upload our local list of negative criteria 
without first checking if there are any criteria already present. Or is 
there a better way of synchronizing account-level negative criteria?

Thanks for any feedback and best regards,
Dorian

-- 
-- 
=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~
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/4bcd2191-b99c-48e8-a610-1474af7942a0%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: AWQL Reporting slowdown?

[Dorian Kind]

Hi all,

I was just wondering whether the situation is still the same for you? On 
our end, the reporting slowdown first encountered in September seems to be 
permanent.

Thanks for your feedback and best regards,
Dorian

On Tuesday, 7 November 2017 11:50:10 UTC+1, Tomas R wrote:
>
> It's a bit like a closed loop:
> 1) Reporting API does not support sorters and paging, so you end up 
> getting data you don't really need which increases response time.
> 2) All the requests are super slow anyway, so you have to implement 
> caching with multi-threading. The slower it gets, the more threads you use. 
> Multiple companies hammering reporting API this way, obviously doesn't 
> improve API performance.
> 3) Finally from time-to-time the API stops responding in timely fashion at 
> all or starts throwing 500 errors (happens relatively often these days) and 
> *the 
> engineers* apply some temporary work-around which doesn't solve the real 
> issue and we are back at point 1.
>

-- 
-- 
=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~
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/01efaa45-86f9-4497-beda-23c2ea663f59%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Downloading > 100.000 adgroups

[Dorian Kind]

The maximum number of ad groups per campaign is 20'000 
(https://support.google.com/adwords/answer/6372658). So as long as you 
download them per campaign, you shouldn't have a problem with pagination.

Cheers,
Dorian

On Friday, 17 November 2017 03:40:03 UTC+1, David Antunes wrote:
>
> Hi,
>
> I have a client who, I believe, has more than 100.000 adgroups in a 
> campaign.
> How can I download them using the api? (there's a pagination limit of 
> 100.000, right?)
>
> Thanks!
> 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/0c4032a8-f749-4299-a8ee-415902d417fc%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Duplicate Labels

[Dorian Kind]

Hi there,

we've also been experiencing this issue lately, the first time on November 
7th. Interestingly it only affects certain label names. As an example for 
today, in one account we were able to create the label "M: 07.11.2017", but 
not "M: 06.11.2017". Both of these labels did never exist in the account 
before.

Best regards,
Dorian

On Monday, 13 November 2017 19:41:27 UTC+1, David Antunes wrote:
>
> Hi,
>
> Same issue here :)
>
> Kind regards,
> David
>
> On Friday, November 10, 2017 at 11:37:29 AM UTC, Ashish Pathak wrote:
>>
>> Hello,
>>
>> We are also facing the same issue when we try to create label from API it 
>> is throwing error LabelError.DUPLICATE_NAME  and we can not see the label 
>> with same name in  AdWords web interface,Adwords editor neither we can 
>> fetch label with that name from AdWords scripts I have come across this 
>> problem on 2 accounts so far, can you please look into it ASAP? 
>>
>> On Wednesday, November 8, 2017 at 11:34:29 AM UTC+5:30, Peter Oliquino 
>> wrote:
>>>
>>> Hi Jon,
>>>
>>> Please correct my understanding if it is wrong. Based on your statement, 
>>> "*I tried renaming the removed label through the API, which was 
>>> successful*", could you confirm if you were indeed able to rename a 
>>> REMOVED label via the AdWords API? This being said and in order to better 
>>> investigate the issue, could you provide the generated SOAP request and 
>>> response when you renamed the original label and the one generated when you 
>>> encountered the LabelError.DUPLICATE_NAME error? You may reply to me using 
>>> the *Reply privately to author* option.
>>>
>>> Thanks and regards,
>>> Peter
>>> AdWords API Team
>>>
>>

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

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

Re: What are requirements for poxy server to coop with Google AdWordsAPI library

[Dorian Kind]

I think you need to take a look at this issue with your administrator, as 
it's hard to say what's going on without knowing how your proxy setup looks 
like.

To the best of my knowledge, as far as the Adwords API client library is 
concerned, all you need is to be able to make HTTPS requests to the 
"adwords.google.com" host. Except probably for the BatchJobService, which 
AFAIK uses Google Cloud Storage to up/download large jobs.


On Friday, 20 October 2017 10:59:59 UTC+2, Sebastian Piskorski wrote:
>
> @Dorian Kind, Thank you for the reply.
>
> Your answer gives some light to my issue, but I don't quite understand 
> what " originates from a reverse lookup:" means. I have whitelisted "
> adwords.google.com" but an error is still the same. At least when I try 
> to run examples, provided by the lib.
>
> On Thursday, October 19, 2017 at 3:07:06 PM UTC+2, Dorian Kind wrote:
>>
>> If I may chime in, I'm pretty sure the googleads library only connects to 
>> "adwords.google.com". The "1e100.net" domain probably originates from a 
>> reverse lookup:
>>
>> $ host adwords.google.com 
>> adwords.google.com is an alias for adwords.l.google.com.
>> adwords.l.google.com has IPv6 address 2a00:1450:400c:c04::64
>>
>> $ host 2a00:1450:400c:c04::64 
>> 4.6.0.0.0.0.0.0.0.0.0.0.0.0.0.0.4.0.c.0.c.0.0.4.0.5.4.1.0.0.a.2.ip6.arpa 
>> domain 
>> name pointer wk-in-x64.1e100.net.
>>
>> So if we're talking about a web proxy, whitelisting the "
>> adwords.google.com" host should be fine. If you really need to whitelist 
>> on the network level, Google announces quite a number of IPv6 prefixes...
>>
>>
>> On Thursday, 19 October 2017 09:39:25 UTC+2, Sebastian Piskorski wrote:
>>>
>>> But requirements for proxy should be the same for all languages. All I 
>>> need is probably list of addresses that I have to whitelist in order to run 
>>> AdWords API requests through proxies using Google Library. Also, I think 
>>> you should know CURL and why lib tries to connect 
>>> "2a00:1450:4016:80c::200a:", and how to force it to use domain address 
>>> instead.
>>>
>>> On Wednesday, October 18, 2017 at 10:30:33 PM UTC+2, Jude Amagoh wrote:
>>>>
>>>> Hi,
>>>>
>>>> I'd be glad to assist you with your query but, unfortunately this 
>>>> question is out of my scope. I recommend you post your question on the php 
>>>> github <https://github.com/googleads/googleads-php-lib/issues> and they'll 
>>>> be better equipped to answer this question. 
>>>>
>>>> Best Regards,
>>>> Jude, 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/7f443ca6-a712-4667-a386-9cbd58fe3d01%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: What are requirements for poxy server to coop with Google AdWordsAPI library

[Dorian Kind]

If I may chime in, I'm pretty sure the googleads library only connects to 
"adwords.google.com". The "1e100.net" domain probably originates from a 
reverse lookup:

$ host adwords.google.com 
adwords.google.com is an alias for adwords.l.google.com.
adwords.l.google.com has IPv6 address 2a00:1450:400c:c04::64

$ host 2a00:1450:400c:c04::64 
4.6.0.0.0.0.0.0.0.0.0.0.0.0.0.0.4.0.c.0.c.0.0.4.0.5.4.1.0.0.a.2.ip6.arpa domain 
name pointer wk-in-x64.1e100.net.

So if we're talking about a web proxy, whitelisting the 
"adwords.google.com" host should be fine. If you really need to whitelist 
on the network level, Google announces quite a number of IPv6 prefixes...


On Thursday, 19 October 2017 09:39:25 UTC+2, Sebastian Piskorski wrote:
>
> But requirements for proxy should be the same for all languages. All I 
> need is probably list of addresses that I have to whitelist in order to run 
> AdWords API requests through proxies using Google Library. Also, I think 
> you should know CURL and why lib tries to connect 
> "2a00:1450:4016:80c::200a:", and how to force it to use domain address 
> instead.
>
> On Wednesday, October 18, 2017 at 10:30:33 PM UTC+2, Jude Amagoh wrote:
>>
>> Hi,
>>
>> I'd be glad to assist you with your query but, unfortunately this 
>> question is out of my scope. I recommend you post your question on the php 
>> github  and they'll 
>> be better equipped to answer this question. 
>>
>> Best Regards,
>> Jude, 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/3000d30f-d1c2-48ed-a390-0e04b75d9051%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: AWQL Reporting slowdown?

[Dorian Kind]

On Monday, 16 October 2017 20:28:44 UTC+2, AdWordsApiUser wrote:
>
>
> @Dorian, do you use TSV format by any chance? I keep suspecting that it is 
> something to do with TSV format reports, but I am not able to prove it in 
> experiments with a hundred or so reports. 
>

No, we use CSV reports exclusively.

-- 
-- 
=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~
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/ed644b40-c3bc-4fd2-a647-b60f9a1d0b1b%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Change account e-mail

[Dorian Kind]

Hi,

To me your issue is not exactly clear.

If you are talking about changing the email address of an existing Google 
accounts, as far as I know this is only possible if you are using G Suite. 
A G Suite domain administrator should be able to change the email address 
of the account.
However, if you would like to move existing OAuth credentials to a new 
user, I don't think there's any way to do that as the credentials 
are intrinsically linked to the user that granted them.

Hope this helps.

Best regards,
Dorian

On Thursday, 28 September 2017 16:32:25 UTC+2, Gabriel Moser wrote:
>
> Hi guys!
>
> We URGENTLY need to change the current MCC holder of API credentials to 
> another e-mail.
> We cannot keep changing accounts and leaving the current MCC account's 
> e-mail online because it is from an employee.
> We are a huge partner of Google in Brazil! Please, Help Us!
>
>
> Em terça-feira, 19 de setembro de 2017 21:25:09 UTC+2, Gabriel Moser 
> escreveu:
>>
>> Hi there ! We have an account already connected with the API, with 
>> hundreds off customer MCC's linked to it.
>> However, our first registered e-mail was badly chosen, and it contains 
>> one employee personal e-mail, so we must change it because it appears on 
>> every change that we perform on the accounts through automated processes.
>>
>> The issue is that we need to change without having to create another 
>> account and passing through all the homologation steps again to use the 
>> API. We have daily robots that use the API constantly working.
>>
>> Can you help us with that? Thank you folks !
>>
>

-- 
-- 
=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~
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/1fd1e66e-df28-45c3-8827-22681ca4e9a8%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: AWQL Reporting slowdown?

[Dorian Kind]

Hello,

FWIW, we also have experienced somewhat of a performance degradation in the 
reporting infrastructure.

We have one job in particular that collects a number of KPIs and structural 
data for a few hundred accounts using non-AWQL report definitions, and up 
until September 7th its run time was always in the order of ~200 minutes. 
Starting from September 8th however, this job now takes more than double 
that time, usually between 400 and 500 minutes for the same number of 
accounts. It's not a problem for us as the functionality is not 
time-critical, but it definitely became slower.

The timing suggests that it could be the same issue as described 
by AdWordsApiUser in the original post.

Best regards,
Dorian

On Wednesday, 27 September 2017 14:38:11 UTC+2, Michael Cloonan (AdWords 
API Team) wrote:
>
> Hello,
>
> No changes were made that should affect reporting speed, so I have some 
> followup questions to see if we can determine the root cause here.
>
> - Is this across all report types, or is there a specific report type 
> where you're seeing the slower behavior?
> - Do you see more rows get returned or anything else changed in the 
> content of the reports?
> - For a single report, how long did it take previously and how long does 
> it take now?
>
> Regards,
> Mike, AdWords API Team
>
> On Tuesday, September 26, 2017 at 8:02:13 AM UTC-4, Michael Cloonan 
> (AdWords API Team) wrote:
>>
>> Hello,
>>
>> No updates yet. I will follow up with the team to see what they've found 
>> so far. I will post here when I have any information to share.
>>
>> Regards,
>> Mike, AdWords API Team
>>
>> On Tuesday, September 26, 2017 at 5:00:47 AM UTC-4, AdWordsApiUser wrote:
>>>
>>> Any updates on this? Thanks!
>>>
>>> On Thursday, September 21, 2017 at 12:32:37 PM UTC+5:30, AdWordsApiUser 
>>> wrote:

 I saw this new thread mentioning the slowdown in TSV reports - we use 
 TSV reports exclusively - probably that is the issue - 
 https://groups.google.com/forum/?utm_medium=email_source=footer#!topic/adwords-api/lnuRYUwohNw

 A swift resolution will be appreciated :-)

 MG


 On Tuesday, September 19, 2017 at 8:04:09 PM UTC+8, Michael Cloonan 
 (AdWords API Team) wrote:
>
> Hello,
>
> No, that will not be necessary; you specifically specified AWQL so I 
> wanted to know if you had done any tests narrowing that down.
>
> When you say your "job", you mean that your job runs multiple reports 
> that, in aggregate, used to take 8 hours and now take 16, right? It's not 
> a 
> single report taking that long?
>
> I will pass along the details you sent privately to our engineering 
> team to investigate in the meanwhile.
>
> Regards,
> Mike, AdWords API Team
>
> On Monday, September 18, 2017 at 5:53:21 PM UTC-4, AdWordsApiUser 
> wrote:
>>
>> Hi Michael,
>>
>> Thanks for your reply. We only use AWQL styled queries, so I don't 
>> know right now if that could be the reason. Do you suggest that we try 
>> using the definition styled reports and compare performance?  As I 
>> mentioned earlier, my job that used to get over in 8 hours now takes 16.
>>
>> Cheers, 
>> MG
>>
>>

-- 
-- 
=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~
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/827031be-dce3-4ad3-8522-3fd60dc957de%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: FeedItemService clear a moneyWithCurrencyValue attribute

[Dorian Kind]

Hi Shwetha,

that works indeed! Thanks a lot for your support!

Best regards,
Dorian

On Wednesday, 27 September 2017 16:08:46 UTC+2, Shwetha Vastrad (AdWords 
API Team) wrote:
>
> Hi Dorian, 
>
> Thanks for pointing this out. I tried a couple of things and the following 
> operation successfully cleared the price:
>
> 
> SET
> 
> FeedId
> FeedItemId
> 
> 7
> 
> 
> 
>
> So, you should not send a null moneyWithCurrencyValue, rather not specify 
> the attribute value to clear it. I apologize for the confusion earlier. I 
> hope this clears things up. 
>
> 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/c3c7ba3f-a7fd-4e2d-9ffd-87951fe22cf6%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: FeedItemService clear a moneyWithCurrencyValue attribute

[Dorian Kind]

Hi Shwetha,

just to clarify: The documentation at 
https://developers.google.com/adwords/api/docs/reference/v201708/FeedItemService.FeedItemAttributeValue
 
clearly says

*"Leave empty to clear an existing PRICE attribute value."*

when talking about the "moneyWithCurrencyValue" field.

So is the UNEXPECTED_INTERNAL_API_ERROR a bug that is going to be fixed in 
a later version, or is the documentation wrong? Also note that creating a 
new FeedItem and deleting the old one would mean that its competitive 
metrics are lost, so we'd much prefer to edit the existing one.

Thanks and best regards,
Dorian

On Tuesday, 26 September 2017 20:01:08 UTC+2, Shwetha Vastrad (AdWords API 
Team) wrote:
>
> Hi, 
>
> I'm afraid its not possible to clear the price of an item in a row. I see 
> that if you clear the other attributes, but not the price, the FeedItem is 
> disapproved. If you want to clear the attribute values for a particular 
> item (say item 8) in a price extension, I would suggest that you create a 
> new FeedItem which doesn't contain these attributes.
>
> 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/1d1e0bf1-b64d-40d9-9ba9-2603ed2e976b%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: IPv6 Exclusion

[Dorian Kind]

An update to my original post: In the meantime the behavior changed; it's 
now possible to exclude arbitrarily large IPv6 subnets using the 
CampaignCriterionService, here's an example with a */4* prefix(!)

(CampaignCriterionPage){
   totalNumEntries = 1
   Page.Type = "CampaignCriterionPage"
   entries[] = 
  (NegativeCampaignCriterion){
 campaignId = 924438233
 isNegative = True
 criterion = 
(IpBlock){
   id = 362641166356
   type = "IP_BLOCK"
   Criterion.Type = "IpBlock"
   ipAddress = "2000:0:0:0:0:0:0:0/4"
}
 CampaignCriterion.Type = "NegativeCampaignCriterion"
  },
 }

Maybe this helps someone.

Cheers,
Dorian

On Tuesday, 12 May 2015 18:20:59 UTC+2, Dorian Kind wrote:
>
> Hi there,
>
> I've gathered some anecdotal evidence that the CampaignCriterionService 
> supports blocking whole IPv6 prefixes up to size */48*. Any prefixes 
> larger than that (i.e. with a smaller prefix length) will give 
> you CriterionError.INVALID_IP_FORMAT.
>
> By the way, if you're looking for the selector field to get the actual IP 
> address out of the criterion, it's *KeywordText*(!!!) Just in case anyone 
> is desperately looking for it.
>
> Cheers,
> Dorian
>
> On Thursday, May 7, 2015 at 4:53:39 PM UTC+2, Nadine Sundquist (AdWords 
> API Team) wrote:
>>
>> Hello Dorian,
>>
>> I'm looking into this and will get back to you. If you get a chance to 
>> test it before I have the answer for you, I would like to hear about the 
>> outcome.
>>
>> Best,
>> Nadine, AdWords API Team
>>
>> On Wednesday, May 6, 2015 at 11:40:28 AM UTC-4, Dorian Kind wrote:
>>>
>>> Hi there,
>>>
>>> Just out of curiosity, I've tried to set up some IP exclusion rules in a 
>>> test account. It appears that IPv6 addresses are supported in the 
>>> corresponding dialog, as I cannot save incomplete or invalid entries. 
>>> However, I have found no way to exclude whole prefixes. With IPv6 privacy 
>>> extensions now being supported by all popular operating systems, excluding 
>>> individual addresses is probably not really going to get you anywhere.
>>>
>>> I tried to enter an address with a prefix length, and something very 
>>> interesting happened: When I enter *2001:db8::/32 *as address and click 
>>> "Save", the address is changed to *2001:db8::/32/128 *and I get an 
>>> "Invalid address" error.
>>>
>>> Besides this amusing behavior, is there any way to exclude whole IPv6 
>>> prefixes as opposed to individual addresses in the web interface?
>>>
>>> As far as the API is concerned, it's stated that "*IPv4 and IPv6 
>>> addresses, individual addresses (192.168.0.1), masks for individual 
>>> addresses (192.168.0.1/32 <http://192.168.0.1/32>) [and] masks for Class C 
>>> networks (192.168.0.1/24 <http://192.168.0.1/24>)*" are supported as 
>>> *IpBlock* criteria, but I'm not sure if this also includes IPv6 
>>> prefixes. I intend on testing it, but if anyone already knows the answer, 
>>> I'd be glad to hear it.
>>>
>>> Thanks for any feedback and best regards,
>>> Dorian
>>>
>>>

-- 
-- 
=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~
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/7f693c95-7f70-4255-9f1a-c747372e09b7%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.