Google Ads API v2 deprecation

2020-03-11 Thread Michael Xue
Hi,

With the release of Google Ads API v3. I see that v2 is now deprecated. Is 
there a timeline for when we need to migrate to v3?

Thanks,
Michael Xue

-- 
-- 
=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~
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/f876842e-f343-43ba-b2c5-01e4d8bc84d6%40googlegroups.com.


Re: Unable to create and attach shared keywords in Google Ads API python client

2020-01-14 Thread Michael Xue


On Monday, January 13, 2020 at 4:08:16 PM UTC-5, Michael Xue wrote:
>
> When running the example create_and_attach_shared_keyword_set.py with the 
> latest Python client 4.1.1 release, I'm getting the following error. I've 
> also posted the issue in the Github python client issue section, but I'm 
> wondering if there are limitations on what types of campaigns I can apply 
> the shared keyword set to? In my case, I was trying to attach the shared 
> keywords to a video campaign. Is this also the case for shared negative 
> placements set? The strange thing is that it use to work but now is broken.
>
>
> Created shared criterion 
> "customers/{obfuscated}/sharedCriteria/{obfuscated}~{obfuscated}".
> Created shared criterion 
> "customers/{obfuscated}/sharedCriteria/{obfuscated}~{obfuscated}".
> Request made: ClientCustomerId: {obfuscated}, Host: 
> googleads.googleapis.com:443, Method: 
> /google.ads.googleads.v2.services.CampaignSharedSetService/MutateCampaignSharedSets,
>  RequestId: None, IsFault: True, FaultMessage: None
> Traceback (most recent call last):
>   File 
> "/Users/{obfuscated}/Projects/google-ads-python/examples/advanced_operations/create_and_attach_shared_keyword_set.py",
>  line 130, in 
> main(google_ads_client, args.customer_id, args.campaign_id)
>   File 
> "/Users/{obfuscated}/Projects/google-ads-python/examples/advanced_operations/create_and_attach_shared_keyword_set.py",
>  line 99, in main
> customer_id, [campaign_set_operation]).results[0].resource_name)
>   File 
> "/Users/{obfuscated}/.local/share/virtualenvs/google-ads-python-ObS9Yvf7/lib/python3.7/site-packages/google/ads/google_ads/v2/services/campaign_shared_set_service_client.py",
>  line 402, in mutate_campaign_shared_sets
> return self._inner_api_calls['mutate_campaign_shared_sets'](request, 
> retry=retry, timeout=timeout, metadata=metadata)
>   File 
> "/Users/{obfuscated}/.local/share/virtualenvs/google-ads-python-ObS9Yvf7/lib/python3.7/site-packages/google/api_core/gapic_v1/method.py",
>  line 143, in __call__
> return wrapped_func(*args, **kwargs)
>   File 
> "/Users/{obfuscated}/.local/share/virtualenvs/google-ads-python-ObS9Yvf7/lib/python3.7/site-packages/google/api_core/retry.py",
>  line 286, in retry_wrapped_func
> on_error=on_error,
>   File 
> "/Users/{obfuscated}/.local/share/virtualenvs/google-ads-python-ObS9Yvf7/lib/python3.7/site-packages/google/api_core/retry.py",
>  line 184, in retry_target
> return target()
>   File 
> "/Users/{obfuscated}/.local/share/virtualenvs/google-ads-python-ObS9Yvf7/lib/python3.7/site-packages/google/api_core/timeout.py",
>  line 214, in func_with_timeout
> return func(*args, **kwargs)
>   File 
> "/Users/{obfuscated}/.local/share/virtualenvs/google-ads-python-ObS9Yvf7/lib/python3.7/site-packages/google/api_core/grpc_helpers.py",
>  line 57, in error_remapped_callable
> return callable_(*args, **kwargs)
>   File 
> "/Users/{obfuscated}/.local/share/virtualenvs/google-ads-python-ObS9Yvf7/lib/python3.7/site-packages/grpc/_interceptor.py",
>  line 222, in __call__
> compression=compression)
>   File 
> "/Users/{obfuscated}/.local/share/virtualenvs/google-ads-python-ObS9Yvf7/lib/python3.7/site-packages/grpc/_interceptor.py",
>  line 257, in _with_call
> return call.result(), call
>   File 
> "/Users/{obfuscated}/.local/share/virtualenvs/google-ads-python-ObS9Yvf7/lib/python3.7/site-packages/grpc/_interceptor.py",
>  line 126, in result
> raise self._exception
>   File 
> "/Users/{obfuscated}/.local/share/virtualenvs/google-ads-python-ObS9Yvf7/lib/python3.7/site-packages/grpc/_interceptor.py",
>  line 248, in continuation
> compression=new_compression)
>   File 
> "/Users/{obfuscated}/.local/share/virtualenvs/google-ads-python-ObS9Yvf7/lib/python3.7/site-packages/grpc/_interceptor.py",
>  line 272, in with_call
> compression=compression)
>   File 
> "/Users/{obfuscated}/.local/share/virtualenvs/google-ads-python-ObS9Yvf7/lib/python3.7/site-packages/grpc/_interceptor.py",
>  line 257, in _with_call
> return call.result(), call
>   File 
> "/Users/{obfuscated}/.local/share/virtualenvs/google-ads-python-ObS9Yvf7/lib/python3.7/site-packages/grpc/_interceptor.py",
>  line 126, in result
> raise self._exception
>   File 
> "/Users/{obfuscated}/.local/share/virtualenvs/google-ads-python-ObS9Yvf7/lib/python3.7/site-packages/grpc/_interceptor.py",
>  line 248, in continuation
> compression=new_compression)
>   File 
> "/Users/{obfuscated}/.local/share/virtualenvs

Re: Unable to create and attach shared keywords in Google Ads API python client

2020-01-13 Thread Michael Xue
Just an update, I tried the API call 
https://googleads.googleapis.com/v2/customers/{obfuscated}/campaignSharedSets:mutate
 with 
a *Display* campaign this time and it worked. But I was able to apply a 
shared keyword set/shared negative placement set to a *video *campaigns 
before. Is this a bug or you guys no longer support shared sets for video 
campaigns?

On Monday, January 13, 2020 at 5:23:21 PM UTC-5, Michael Xue wrote:
>
> Hi Bryan,
>
> Thanks for getting back to me. I tried running the same file but with an 
> older version (4.0.0) of the client and got this exception:
>
> Request with ID "zHpKD9RV14iyrt3TsCd2Hg" failed with status 
> "INVALID_ARGUMENT" and includes the following errors:
> Request made: ClientCustomerId: 7887825568, Host: 
> googleads.googleapis.com:443, Method: 
> /google.ads.googleads.v2.services.CampaignSharedSetService/MutateCampaignSharedSets,
>  
> RequestId: zHpKD9RV14iyrt3TsCd2Hg, IsFault: True, FaultMessage: The error 
> code is not in this version.
> Error with message "The error code is not in this version.".
> On field: operations
>
>
> I can confirm the same error when I make an API call using curl with 
> https://googleads.googleapis.com/v2/customers/{obfuscated}/campaignSharedSets:mutate
> .
> Here's the JSON body:
> {
> "operations": [
> {
> "create": {
> "campaign": {
> "value": 
> "customers/{obfuscated}/campaigns/{obfuscated}"
> },
> "shared_set": {
> "value": 
> "customers/{obfuscated}/sharedSets/{obfuscated}"
> }
> }
> }
> ]
> }
>
> I get the following response 
>
> {
>   "error": {
> "code": 400,
> "message": "Request contains an invalid argument.",
> "status": "INVALID_ARGUMENT",
> "details": [
>   {
> "@type": "
> type.googleapis.com/google.ads.googleads.v2.errors.GoogleAdsFailure",
> "errors": [
>   {
> "errorCode": {
>   "requestError": "UNKNOWN"
> },
> "message": "The error code is not in this version.",
> "trigger": {
>   "int64Value": "4"
> },
> "location": {
>   "fieldPathElements": [
> {
>   "fieldName": "operations",
>   "index": "0"
> }
>   ]
> }
>   }
> ]
>   }
> ]
>   }
> }
>
> Any ideas on why this is happening?
>
> On Monday, January 13, 2020 at 4:45:07 PM UTC-5, adsapiforumadvisor wrote:
>>
>> Hi Michael,
>>
>> Thank you for reaching out. It looks like it’s a setup issue in which 
>> there could have been a problem with the way the client library was 
>> installed, in which it is not reading the attribute file ‘errors_pb2’ while 
>> the the attribute is being used in the script. In this case I would 
>> recommend you to re-download and install the latest version of our client 
>> library to remedy setup issues. For Google Ads Python, you can find the 
>> latest version here 
>> <https://github.com/googleads/google-ads-python/releases>. Could you 
>> give that a try and let me know if you still run into issues with attaching 
>> the shared keyword set to your video campaign, as they should be able to 
>> have shared sets?
>>
>> Thank you,
>> Bryan, Google Ads API Team
>>
>>
>> ref:_00D1U1174p._5001USwM6Y: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/9ab32c50-aee6-4e5e-a434-1f0324f369af%40googlegroups.com.


Re: Unable to create and attach shared keywords in Google Ads API python client

2020-01-13 Thread Michael Xue
Hi Bryan,

Thanks for getting back to me. I tried running the same file but with an 
older version (4.0.0) of the client and got this exception:

Request with ID "zHpKD9RV14iyrt3TsCd2Hg" failed with status 
"INVALID_ARGUMENT" and includes the following errors:
Request made: ClientCustomerId: 7887825568, Host: 
googleads.googleapis.com:443, Method: 
/google.ads.googleads.v2.services.CampaignSharedSetService/MutateCampaignSharedSets,
 
RequestId: zHpKD9RV14iyrt3TsCd2Hg, IsFault: True, FaultMessage: The error 
code is not in this version.
Error with message "The error code is not in this version.".
On field: operations


I can confirm the same error when I make an API call using curl with 
https://googleads.googleapis.com/v2/customers/{obfuscated}/campaignSharedSets:mutate.
Here's the JSON body:
{
"operations": [
{
"create": {
"campaign": {
"value": "customers/{obfuscated}/campaigns/{obfuscated}"
},
"shared_set": {
"value": 
"customers/{obfuscated}/sharedSets/{obfuscated}"
}
}
}
]
}

I get the following response 

{
  "error": {
"code": 400,
"message": "Request contains an invalid argument.",
"status": "INVALID_ARGUMENT",
"details": [
  {
"@type": 
"type.googleapis.com/google.ads.googleads.v2.errors.GoogleAdsFailure",
"errors": [
  {
"errorCode": {
  "requestError": "UNKNOWN"
},
"message": "The error code is not in this version.",
"trigger": {
  "int64Value": "4"
},
"location": {
  "fieldPathElements": [
{
  "fieldName": "operations",
  "index": "0"
}
  ]
}
  }
]
  }
]
  }
}

Any ideas on why this is happening?

On Monday, January 13, 2020 at 4:45:07 PM UTC-5, adsapiforumadvisor wrote:
>
> Hi Michael,
>
> Thank you for reaching out. It looks like it’s a setup issue in which 
> there could have been a problem with the way the client library was 
> installed, in which it is not reading the attribute file ‘errors_pb2’ while 
> the the attribute is being used in the script. In this case I would 
> recommend you to re-download and install the latest version of our client 
> library to remedy setup issues. For Google Ads Python, you can find the 
> latest version here 
> . Could you give 
> that a try and let me know if you still run into issues with attaching the 
> shared keyword set to your video campaign, as they should be able to have 
> shared sets?
>
> Thank you,
> Bryan, Google Ads API Team
>
>
> ref:_00D1U1174p._5001USwM6Y: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/3e8674af-4bcc-45bd-b181-4d90753afda2%40googlegroups.com.


Unable to create and attach shared keywords in Google Ads API python client

2020-01-13 Thread Michael Xue


When running the example create_and_attach_shared_keyword_set.py with the 
latest Python client 4.1.1 release, I'm getting the following error. I've 
also posted the issue in the Github python client issue section, but I'm 
wondering if there are limitations on what types of campaigns I can apply 
the shared keyword set to? In my case, I was trying to attach the shared 
keywords to a video campaign. Is this also the case for shared negative 
placements set? The strange thing is that it use to work but now is broken.


Created shared criterion 
"customers/{obfuscated}/sharedCriteria/{obfuscated}~{obfuscated}".
Created shared criterion 
"customers/{obfuscated}/sharedCriteria/{obfuscated}~{obfuscated}".
Request made: ClientCustomerId: {obfuscated}, Host: 
googleads.googleapis.com:443, Method: 
/google.ads.googleads.v2.services.CampaignSharedSetService/MutateCampaignSharedSets,
 RequestId: None, IsFault: True, FaultMessage: None
Traceback (most recent call last):
  File 
"/Users/{obfuscated}/Projects/google-ads-python/examples/advanced_operations/create_and_attach_shared_keyword_set.py",
 line 130, in 
main(google_ads_client, args.customer_id, args.campaign_id)
  File 
"/Users/{obfuscated}/Projects/google-ads-python/examples/advanced_operations/create_and_attach_shared_keyword_set.py",
 line 99, in main
customer_id, [campaign_set_operation]).results[0].resource_name)
  File 
"/Users/{obfuscated}/.local/share/virtualenvs/google-ads-python-ObS9Yvf7/lib/python3.7/site-packages/google/ads/google_ads/v2/services/campaign_shared_set_service_client.py",
 line 402, in mutate_campaign_shared_sets
return self._inner_api_calls['mutate_campaign_shared_sets'](request, 
retry=retry, timeout=timeout, metadata=metadata)
  File 
"/Users/{obfuscated}/.local/share/virtualenvs/google-ads-python-ObS9Yvf7/lib/python3.7/site-packages/google/api_core/gapic_v1/method.py",
 line 143, in __call__
return wrapped_func(*args, **kwargs)
  File 
"/Users/{obfuscated}/.local/share/virtualenvs/google-ads-python-ObS9Yvf7/lib/python3.7/site-packages/google/api_core/retry.py",
 line 286, in retry_wrapped_func
on_error=on_error,
  File 
"/Users/{obfuscated}/.local/share/virtualenvs/google-ads-python-ObS9Yvf7/lib/python3.7/site-packages/google/api_core/retry.py",
 line 184, in retry_target
return target()
  File 
"/Users/{obfuscated}/.local/share/virtualenvs/google-ads-python-ObS9Yvf7/lib/python3.7/site-packages/google/api_core/timeout.py",
 line 214, in func_with_timeout
return func(*args, **kwargs)
  File 
"/Users/{obfuscated}/.local/share/virtualenvs/google-ads-python-ObS9Yvf7/lib/python3.7/site-packages/google/api_core/grpc_helpers.py",
 line 57, in error_remapped_callable
return callable_(*args, **kwargs)
  File 
"/Users/{obfuscated}/.local/share/virtualenvs/google-ads-python-ObS9Yvf7/lib/python3.7/site-packages/grpc/_interceptor.py",
 line 222, in __call__
compression=compression)
  File 
"/Users/{obfuscated}/.local/share/virtualenvs/google-ads-python-ObS9Yvf7/lib/python3.7/site-packages/grpc/_interceptor.py",
 line 257, in _with_call
return call.result(), call
  File 
"/Users/{obfuscated}/.local/share/virtualenvs/google-ads-python-ObS9Yvf7/lib/python3.7/site-packages/grpc/_interceptor.py",
 line 126, in result
raise self._exception
  File 
"/Users/{obfuscated}/.local/share/virtualenvs/google-ads-python-ObS9Yvf7/lib/python3.7/site-packages/grpc/_interceptor.py",
 line 248, in continuation
compression=new_compression)
  File 
"/Users/{obfuscated}/.local/share/virtualenvs/google-ads-python-ObS9Yvf7/lib/python3.7/site-packages/grpc/_interceptor.py",
 line 272, in with_call
compression=compression)
  File 
"/Users/{obfuscated}/.local/share/virtualenvs/google-ads-python-ObS9Yvf7/lib/python3.7/site-packages/grpc/_interceptor.py",
 line 257, in _with_call
return call.result(), call
  File 
"/Users/{obfuscated}/.local/share/virtualenvs/google-ads-python-ObS9Yvf7/lib/python3.7/site-packages/grpc/_interceptor.py",
 line 126, in result
raise self._exception
  File 
"/Users/{obfuscated}/.local/share/virtualenvs/google-ads-python-ObS9Yvf7/lib/python3.7/site-packages/grpc/_interceptor.py",
 line 248, in continuation
compression=new_compression)
  File 
"/Users/{obfuscated}/.local/share/virtualenvs/google-ads-python-ObS9Yvf7/lib/python3.7/site-packages/grpc/_interceptor.py",
 line 272, in with_call
compression=compression)
  File 
"/Users/{obfuscated}/.local/share/virtualenvs/google-ads-python-ObS9Yvf7/lib/python3.7/site-packages/grpc/_interceptor.py",
 line 256, in _with_call
continuation, client_call_details, request)
  File 
"/Users/{obfuscated}/.local/share/virtualenvs/google-ads-python-ObS9Yvf7/lib/python3.7/site-packages/google/ads/google_ads/interceptors/exception_interceptor.py",
 line 139, in intercept_unary_unary
self._handle_grpc_failure(response)
  File 
"/Users/{obfuscated}/.local/share/virtualenvs/google-ads-python-ObS9Yvf7/lib/python3.7/site-packages/google/ads/googl

Ad Impression Beacon

2019-10-15 Thread Michael Xue
Hi,

Are impressions beacons on Ads accessible through Google Ads API? I took a 
look at the AdGroupAd service but didn't see it.

Thanks,
Michael Xue

-- 
-- 
=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~
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/c23d8321-c0d6-435f-b107-d495595be671%40googlegroups.com.


CIDR block for Google Ads Script

2019-08-16 Thread Michael Xue
Hi,

We have a Google Ads script that is trying to access one of our private 
HTTP server running in AWS. We set the security group for the EC2 instance 
that hosts the HTTP server to allow CIDR block 107.178.192.0/18 (which 
expands to 107.178.192.0 - 107.178.255.255). This seems to be the range of 
IPs that Google Ads script is calling from, based on inspecting the server 
request logs. We're using UrlFetchApp.fetch() to make the HTTP calls to the 
HTTP server. We notice that for Ads scripts calls from IP range 
*107.178.194-5.150-160*, the request would time out. Other Google IP ranges 
seem to work fine. Do you know why this might be happening? Also I noticed 
this IP range is not listed in any docs online.

Thanks,
Michael Xue

-- 
-- 
=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~
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/c0004a96-a7c1-47f0-9a76-1431dd7657fd%40googlegroups.com.


Re: Negative placement list at MCC/Managed Account Level

2019-07-04 Thread Michael Xue
Thank you Bharani.

On Wednesday, July 3, 2019 at 10:16:32 AM UTC-4, adsapiforumadvisor wrote:
>
> Hello Michael, 
>
> The Google Ads API will have the same feature parity as AdWords API. This 
> feature about sharing the MCC level negative criteria to all the 
> sub-accounts is not supported in AdWords API, and is not yet available in 
> Google Ads API too. Please keep an eye on our blog 
>  for 
> details on upcoming releases. 
>
> Thanks,
> Bharani, Google Ads API Team
>
> ref:_00D1U1174p._5001UCaWG5: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/24d1c3c7-3b54-41b3-948a-05b932d9c1ae%40googlegroups.com.


Applying placement exclusion lists to account/ad group programmatically

2019-07-01 Thread Michael Xue
Hi,

I'm wondering if the Google Ads API supports applying placement exclusion 
lists to an account or ad group programmatically? I see that this is 
possible in the Google Ads user interface: 
https://support.google.com/google-ads/answer/7331110.

I know that placement exclusion lists can be applied to campaigns using a 
combination of SharedSetService and CampaignSharedSetService API services. 
Is there something similar for account or ad group?

Thanks,
Michael Xue

-- 
-- 
=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~
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/3eaf43b2-6718-4bc5-a1a1-485dd798b86b%40googlegroups.com.


Re: Negative placement list at MCC/Managed Account Level

2019-07-01 Thread Michael Xue
Hi, I have a similar question, and am wondering if things have changed 
since the original post date. I would like to know if its possible to share 
MCC account level negative placements across sub-accounts with *Google Ads 
API*.

On Monday, March 27, 2017 at 11:57:05 AM UTC-4, Sreelakshmi Sasidharan 
(AdWords API Team) wrote:
>
> Hi, 
>
> By using Shared sets 
> ,
>  
> you will be able to manage your negative keywords and placement exclusions 
> across all campaigns in an account removing the need for duplication.
>
> Unfortunately, we do not have any service that can be used to apply the 
> keywords and placement exclusions across the accounts. If you haven't 
> already, please follow the Ads Developer blog 
>  for 
> updates and announcements. 
>
> Thanks,
> Sreelakshmi, 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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/adwords-api/f20fd7f2-3a00-4928-8fe2-e6cdc1fc2e2d%40googlegroups.com.


Re: Detail Placement report fields with value '--'

2019-07-01 Thread Michael Xue
Thank you Hiroyuki!

On Wednesday, June 5, 2019 at 11:57:39 PM UTC-4, adsapiforumadvisor wrote:
>
> Hi Michael,
>
> The value '--' in reports means null. However, your concern appears to be 
> more specific to the Google Ads UI and how values in reports are generated. 
> With this, I would suggest that you get in touch with the product experts 
> via the Google Ads Community Forum 
>  so 
> they can better assist you if you have further concerns.
>
> Regards,
> Hiroyuki
> Google Ads API Team
>
>
> ref:_00D1U1174p._5001UBlkB7: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/92107ca9-f3d4-4508-a9de-b6678c8020fb%40googlegroups.com.


Detail Placement report fields with value '--'

2019-06-05 Thread Michael Xue
Hi,

When pulling a detail placement from the Google Ads UI in the browser, 
we're noticing now that some fields have the value '--'. Is this suppose to 
mean that data for this field is not known? Here's a sample CSV:

Placement (group),Placement (group) url,Placement (detail),Placement 
(detail) url,Campaign,Ad group,Impr.,Currency code,Avg. 
cost,Cost,Conversions,Cost / conv.,Conv. rate,Avg. CPV,Views,View rate,Avg. 
CPM
redacted,redacted,redacted,redacted,redacted,redacted,1,GBP,0.03,0.03,0,0,0.00%,0.03,1,100.00%,25.6
redacted,redacted,redacted,redacted,redacted,redacted,1,GBP,0.01,0.01,0,0,0.00%,
 
--,0,0.00%,5.83
redacted,redacted,redacted,redacted,redacted,redacted,38,GBP,0.02,0.37,0,0,0.00%,
 
--,0,0.00%,9.68

Thanks,
Michael Xue

-- 
-- 
=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~
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/4c60c671-c92a-4ea8-a335-e2018406179f%40googlegroups.com.


Google Ads API: Migrating ManagedCustomerService to CustomerClientService

2019-04-09 Thread michael . xue
Hi,

I've followed the Google Ads API migration guide and we are in the process 
of migrating functionality related to *ManagedCustomerService* in AdWords 
to *CustomerClientService* in the new API. Our current use case is to use a 
manager account to fetch a list of client accounts. However I'm unsure as 
to how to fetch the metadata for the list of customers returned by 
CustomerClientService. In ManagedCustomerService 
<https://developers.google.com/adwords/api/docs/reference/v201809/ManagedCustomerService>,
 
I would get back a list of ManagedCustomer 
<https://developers.google.com/adwords/api/docs/reference/v201809/ManagedCustomerService.ManagedCustomer>
 
objects type. In the new API, the CustomerClientService does not seem to 
have all the fields. However I did notice that CustomerService 
<https://developers.google.com/google-ads/api/docs/fields/customer> in new 
API did have similar set of fields to ManagedCustomer. How can I get fields 
for client accounts in the new API? Thanks in advance.

Best,
Michael Xue

-- 
-- 
=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~
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/c0e86712-d62f-4ef9-ad37-29ee9bf7c09c%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


Re: [1-1567000026135] Adwords' CRITERIA_PERFORMANCE_REPORT mapping in Google Ads API

2019-04-09 Thread michael . xue
Hi Dave,

Anash was able to provide me with the following answer, and it works!

YOUTUBE_CHANNEL is a placement criterion, so managed_placement_view should 
give you the data you need. The following query should work.

SELECT metrics.active_view_viewability, metrics.average_cpm, " +
"metrics.average_cpv, metrics.cost_micros, 
metrics.impressions, " +
"metrics.video_quartile_25_rate, 
metrics.video_quartile_50_rate, " +
"metrics.video_quartile_75_rate, 
metrics.video_quartile_100_rate, " +
"metrics.video_view_rate, metrics.video_views FROM 
managed_placement_view " +
"WHERE ad_group_criterion.type = 'YOUTUBE_CHANNEL' and 
ad_group.id = 61856865793

Best,
Michael Xue

On Thursday, April 4, 2019 at 4:34:05 AM UTC-4, googleadsapi-forumadvisor 
wrote:
>
> Hi Michael,
>
> Thank you for reaching out. Unfortunately, The CRITERIA_PERFORMANCE_REPORT 
> from AdWords API has no exact equivalent in Google Ads API. For your 
> concern about the GAQL returning 0 rows as opposed to the AWQL returning 
> 3800 rows, I would need to check this with the team. I will get back to you 
> as soon as we gather all the information needed to help you with this 
> concern.
>
> Regards,
> Dave Paurillo
> 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 
> <https://support.google.com/google-ads/contact/survey_transactional?caseid=1-156726135&hl=en&ctx=1>
>
> 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 04/04/19 00:14:44 micha...@openslate.com  wrote:
>
> Hi,
>
> We're in the process of migrating from Adwords API to Google Ads API. One 
> issue we had was mapping the CRITERIA_PERFORMANCE_REPORT query to its 
> equivalent in Google Ads query. Here's a sample query we run in AWQL:
> SELECT ActiveViewViewability, AverageCpm, AverageCpv, Cost, Impressions, 
> VideoQuartile25Rate, VideoQuartile50Rate, VideoQuartile75Rate, 
> VideoQuartile100Rate, VideoViewRate, VideoViews 
> FROM CRITERIA_PERFORMANCE_REPORT
> WHERE CriteriaType='YOUTUBE_CHANNEL' AND AdGroupId=61856865793
>
> This is our best guess at the equivalent query in Google Ads:
> SELECT metrics.active_view_viewability, metrics.average_cpm, metrics.
> average_cpv, metrics.cost_micros, metrics.impressions, metrics.
> video_quartile_25_rate, metrics.video_quartile_50_rate, metrics.
> video_quartile_75_rate, metrics.video_quartile_100_rate, metrics.
> video_view_rate, metrics.video_views
> FROM ad_group_audience_view
> WHERE ad_group_criterion.type='YOUTUBE_CHANNEL' 
> AND ad_group.id=61856865793
>
> However, the original AWQL returns around 3800 rows, but the new GAQL 
> query returns 0 rows. Can you confirm that this is indeed the correct 
> mapping? Thanks in advance.
>
> Best,
> Michael Xue
>
> -- 
> -- 
> =~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~
> 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/4f256271-7025-472a-b924-3c1d007e8840%40googlegroups.com
>  
> <https://groups.google.com/d/msgid/adwords-api/4f256271-7025-472a-b924-3c1d007e8840%40googlegroups.com?utm_medium=email&utm_source=footer>
> .
> For more options, visit https://groups.google.com/d/optout.
>
>

-- 
-- 
=~=~

Adwords' CRITERIA_PERFORMANCE_REPORT mapping in Google Ads API

2019-04-03 Thread michael . xue
Hi,

We're in the process of migrating from Adwords API to Google Ads API. One 
issue we had was mapping the CRITERIA_PERFORMANCE_REPORT query to its 
equivalent in Google Ads query. Here's a sample query we run in AWQL:
SELECT ActiveViewViewability, AverageCpm, AverageCpv, Cost, Impressions, 
VideoQuartile25Rate, VideoQuartile50Rate, VideoQuartile75Rate, 
VideoQuartile100Rate, VideoViewRate, VideoViews 
FROM CRITERIA_PERFORMANCE_REPORT
WHERE CriteriaType='YOUTUBE_CHANNEL' AND AdGroupId=61856865793

This is our best guess at the equivalent query in Google Ads:
SELECT metrics.active_view_viewability, metrics.average_cpm, metrics.
average_cpv, metrics.cost_micros, metrics.impressions, metrics.
video_quartile_25_rate, metrics.video_quartile_50_rate, metrics.
video_quartile_75_rate, metrics.video_quartile_100_rate, metrics.
video_view_rate, metrics.video_views
FROM ad_group_audience_view
WHERE ad_group_criterion.type='YOUTUBE_CHANNEL' 
AND ad_group.id=61856865793

However, the original AWQL returns around 3800 rows, but the new GAQL query 
returns 0 rows. Can you confirm that this is indeed the correct mapping? 
Thanks in advance.

Best,
Michael Xue

-- 
-- 
=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~
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/4f256271-7025-472a-b924-3c1d007e8840%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.