Re: Google Ads APIv12 (java client) doesn't throw any errors anymore when modify a deleted AdsGroups

[Google Ads API and AdWords API Forum]

Re-posting the last inquiry 
 [https://groups.google.com/g/adwords-api/c/NRjQoeP1tfM] from the forum as 
it wasn't routed to our support queue.

Regards,
Carmela
Google Ads API Team

On Friday, November 18, 2022 at 1:44:47 AM UTC+8 Ronald Findling wrote:

> Dear GoogleAds Team, we're on the migration path from v10 to v12 with our 
> java client.
>
> and observe the following seemingly undocumented behaviour change:
>
> * In v10 when trying to modify a deleted adsGroup a 
> `OperationAccessDeniedErrorEnum.OperationAccessDeniedError` is thrown
> * In v12 when trying to modify a deleted adsGroup the modified adsGroup 
> gets returned (with status `Removed`)
>
> Is this intended behaviour or a bug?
>
> Best Regards
> Ron
>
> PS: Seems somehow similar to 
> https://groups.google.com/g/adwords-api/c/GSJmnw05iB4/m/7T9BHQmaAQAJ 
> (where also deleted AdGroups are observed)
>

-- 
-- 
=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~
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/5144b40c-91c7-4a56-aeaa-ed4236f55108n%40googlegroups.com.

Re: ResourceExhausted: 429 Resource has been exhausted (e.g. check quota)

[Google Ads API and AdWords API Forum]

Re-posting the last inquiry 
 [https://groups.google.com/g/adwords-api/c/HX6BOQd3yYs] from the forum as 
it wasn't routed to our support queue.

Regards,
Carmela
Google Ads API Team
On Thursday, November 17, 2022 at 10:35:58 PM UTC+8 data...@weekendesk.fr 
wrote:

> Hello,
>
> We've started to used the API not very long time ago, we had only tested 
> it on a test account so far, and we have basic access.
> Yesterday we started to launch our project in production, we had to change 
> the status of about 12k adgroups. After about 10k adgroups updated we got 
> the resource exhausted error, saying we had to try again in 17 hours. The 
> quota should be 15000 operations/day but I'm pretty sure we didn't reach it.
> Today I was able to update only 2 adgroups. Now I get the error again, 
> telling me to try again in 30s this time, but even a while later, I can't 
> update even a single adgroup. I really don't understand how this quota 
> works. Is it daily as in at some time of the day it will reset or it it 
> like 15000 operations over a rolling 24 hours period ?
> And again, I don't think we reached those 15k operations yesterday.
>
> Any help would be appreciated, 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/880a4ae7-fa8c-4772-acf3-b5fd057ebd3an%40googlegroups.com.

Re: INTERNAL ERROR occur get Metrics and Campaign Data using Google Ads API V10 version

[Google Ads API and AdWords API Forum]

Re-posting the last inquiry 
[https://groups.google.com/g/adwords-api/c/blDBedj6c4M] from the forum as 
it wasn't routed to our support queue.

Regards,
Carmela
Google Ads API Team
On Thursday, November 17, 2022 at 8:32:53 PM UTC+8 changh...@rakuten.com 
wrote:

> Hello sir
>
>we are trying to get Display Ads campaign and Metrics data using 
> Google Ads V10 API , but occasionally  it will give me INTERNAL ERROR , and 
> i can't find why this such type of error has been come
>
> com.google.ads.googleads.v10.errors.GoogleAdsException: errors {
>
>   error_code {
>
> internal_error: INTERNAL_ERROR
>
>   }
>
>   message: "An internal error has occurred."
>
> }
>
> request_id: "EDSPIdhbp3lSjX29k4INQg"
>
>
>at 
> com.google.ads.googleads.v10.errors.GoogleAdsException$Factory.createException(GoogleAdsException.java:42)
>
>at 
> com.google.ads.googleads.v10.errors.GoogleAdsException$Factory.createException(GoogleAdsException.java:34)
>
>at 
> com.google.ads.googleads.lib.stubs.exceptions.BaseGoogleAdsException$Factory.createGoogleAdsException(BaseGoogleAdsException.java:105)
>
>at 
> com.google.ads.googleads.lib.callables.GoogleAdsExceptionTransformation.transform(GoogleAdsExceptionTransformation.java:39)
>
>at 
> com.google.ads.googleads.lib.stubs.callables.ExceptionTransformingServerStreamingCallable$ExceptionTransformingStreamObserver.onError(ExceptionTransformingServerStreamingCallable.java:71)
>
>at 
> com.google.api.gax.tracing.TracedResponseObserver.onError(TracedResponseObserver.java:103)
>
>at 
> com.google.api.gax.rpc.RetryingServerStreamingCallable$1.onFailure(RetryingServerStreamingCallable.java:99)
>
>at com.google.api.core.ApiFutures$1.onFailure(ApiFutures.java:68)
>
>at 
> com.google.common.util.concurrent.Futures$CallbackListener.run(Futures.java:1041)
>
>at 
> com.google.common.util.concurrent.DirectExecutor.execute(DirectExecutor.java:30)
>
>at 
> com.google.common.util.concurrent.AbstractFuture.executeListener(AbstractFuture.java:1215)
>
>at 
> com.google.common.util.concurrent.AbstractFuture.complete(AbstractFuture.java:983)
>
>at 
> com.google.common.util.concurrent.AbstractFuture.setException(AbstractFuture.java:771)
>
>at 
> com.google.api.gax.retrying.BasicRetryingFuture.handleAttempt(BasicRetryingFuture.java:200)
>
>at 
> com.google.api.gax.retrying.CallbackChainRetryingFuture$AttemptCompletionListener.handle(CallbackChainRetryingFuture.java:135)
>
>at 
> com.google.api.gax.retrying.CallbackChainRetryingFuture$AttemptCompletionListener.run(CallbackChainRetryingFuture.java:117)
>
>at 
> com.google.common.util.concurrent.DirectExecutor.execute(DirectExecutor.java:30)
>
>at 
> com.google.common.util.concurrent.AbstractFuture.executeListener(AbstractFuture.java:1215)
>
>at 
> com.google.common.util.concurrent.AbstractFuture.complete(AbstractFuture.java:983)
>
>at 
> com.google.common.util.concurrent.AbstractFuture.setException(AbstractFuture.java:771)
>
>at 
> com.google.api.core.AbstractApiFuture$InternalSettableFuture.setException(AbstractApiFuture.java:95)
>
>at 
> com.google.api.core.AbstractApiFuture.setException(AbstractApiFuture.java:77)
>
>at 
> com.google.api.core.SettableApiFuture.setException(SettableApiFuture.java:52)
>
>at 
> com.google.api.gax.rpc.ServerStreamingAttemptCallable.onAttemptError(ServerStreamingAttemptCallable.java:378)
>
>at 
> com.google.api.gax.rpc.ServerStreamingAttemptCallable.access$600(ServerStreamingAttemptCallable.java:97)
>
>at 
> com.google.api.gax.rpc.ServerStreamingAttemptCallable$2.onErrorImpl(ServerStreamingAttemptCallable.java:249)
>
>at 
> com.google.api.gax.rpc.StateCheckingResponseObserver.onError(StateCheckingResponseObserver.java:86)
>
>at 
> com.google.api.gax.rpc.Watchdog$WatchdogStream.onErrorImpl(Watchdog.java:284)
>
>at 
> com.google.api.gax.rpc.StateCheckingResponseObserver.onError(StateCheckingResponseObserver.java:86)
>
>at 
> com.google.api.gax.grpc.ExceptionResponseObserver.onErrorImpl(ExceptionResponseObserver.java:84)
>
>at 
> com.google.api.gax.rpc.StateCheckingResponseObserver.onError(StateCheckingResponseObserver.java:86)
>
>at 
> com.google.api.gax.grpc.GrpcDirectStreamController$ResponseObserverAdapter.onClose(GrpcDirectStreamController.java:149)
>
>at 
> io.grpc.PartialForwardingClientCallListener.onClose(PartialForwardingClientCallListener.java:39)
>
>at 
> io.grpc.ForwardingClientCallListener.onClose(ForwardingClientCallListener.java:23)
>
>at 
> io.grpc.ForwardingClientCallListener$SimpleForwardingClientCallListener.onClose(ForwardingClientCallListener.java:40)
>
>at 
> com.google.ads.googleads.lib.logging.LoggingInterceptor$1$1.onClose(LoggingInterceptor.java:113)
>
>at 
> io.grpc.internal.DelayedClientCall$DelayedListener$3.run(DelayedClientCall.java:463)
>
>at 
> io.grpc.internal.DelayedClientCall$DelayedListener.delayOrExecute(DelayedClientCall.java:427)
>
>  

Re: ad_group_audience_view, ad_group_criterion.type = UNKNOWN

['Oksana Sulyma' via Google Ads API and AdWords API Forum]

Hello! Kindly reminder on my question sending privately.

On Thursday, November 17, 2022 at 11:01:31 AM UTC+2 Oksana Sulyma wrote:

> Thanks Yasar and team! I have a follow-up question which I've sent 
> privately together with account info. Thank you!
>
> On Monday, November 14, 2022 at 4:44:26 PM UTC+2 adsapi wrote:
>
>> Hi Oksana,
>>
>> Thanks for reaching out to the Google Ads API Forum
>>
>> Yes, you are correct to get "type":"USER_INTEREST" using user_interest 
>> report
>>  
>> to know affinity categories that are found here: 
>> https://developers.google.com/google-ads/api/reference/data/codes-formats#expandable-1
>>
>> Upon checking your screenshot, I can see that you are referring to a 
>> custom combination segment. If my understanding is correct, then you may 
>> need to use *user_list* 
>>  
>> report instead. However, can you clarify if what you meant here is that 
>> while pulling custom combination segments using ad_group_audience_view 
>> report you are getting UNKNOWN in Google Ads API?
>>
>> I asked this because I was able to pull the UI screen data using the 
>> below query for the *AdWords optimized list* customer combination 
>> segments. Here’s the below GAQL:
>>
>>  
>>
>> SELECT user_list.name,
>>
>>user_list.id
>>
>> FROM   user_list
>>
>> WHERE  user_list.name LIKE 'AdWords optimized list' 
>>
>>  
>>
>> Let us know if you are able to pull the said data using the above report 
>> on your end.
>>
>> Regards,
>> [image: Google Logo] 
>> Yasar 
>> Google Ads API Team 
>>   
>>
>> ref:_00D1U1174p._5004Q2g3RyN: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/a22cdd47-6ac7-4505-9468-1d5a0d3beb16n%40googlegroups.com.

Re: ad_group_audience_view, ad_group_criterion.type = UNKNOWN

['Oksana Sulyma' via Google Ads API and AdWords API Forum]

Hello! Kindly reminder on my question sent privately. 

On Thursday, November 17, 2022 at 11:01:31 AM UTC+2 Oksana Sulyma wrote:

> Thanks Yasar and team! I have a follow-up question which I've sent 
> privately together with account info. Thank you!
>
> On Monday, November 14, 2022 at 4:44:26 PM UTC+2 adsapi wrote:
>
>> Hi Oksana,
>>
>> Thanks for reaching out to the Google Ads API Forum
>>
>> Yes, you are correct to get "type":"USER_INTEREST" using user_interest 
>> report
>>  
>> to know affinity categories that are found here: 
>> https://developers.google.com/google-ads/api/reference/data/codes-formats#expandable-1
>>
>> Upon checking your screenshot, I can see that you are referring to a 
>> custom combination segment. If my understanding is correct, then you may 
>> need to use *user_list* 
>>  
>> report instead. However, can you clarify if what you meant here is that 
>> while pulling custom combination segments using ad_group_audience_view 
>> report you are getting UNKNOWN in Google Ads API?
>>
>> I asked this because I was able to pull the UI screen data using the 
>> below query for the *AdWords optimized list* customer combination 
>> segments. Here’s the below GAQL:
>>
>>  
>>
>> SELECT user_list.name,
>>
>>user_list.id
>>
>> FROM   user_list
>>
>> WHERE  user_list.name LIKE 'AdWords optimized list' 
>>
>>  
>>
>> Let us know if you are able to pull the said data using the above report 
>> on your end.
>>
>> Regards,
>> [image: Google Logo] 
>> Yasar 
>> Google Ads API Team 
>>   
>>
>> ref:_00D1U1174p._5004Q2g3RyN: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/2aa4ad7f-5b15-4588-a313-d10476dbf5bdn%40googlegroups.com.

Re: Getting future X points between two tRoas values for a bidding simulator

[Google Ads API and AdWords API Forum]

Re-posting the last inquiry 
 [https://groups.google.com/g/adwords-api/c/RLPDhGmoVNs] from the forum as 
it wasn't routed to our support queue.

Regards,
Carmela
Google Ads API Team
On Friday, November 18, 2022 at 1:58:31 AM UTC+8 EladB wrote:

> Hi
>
> As seen on the UI:
>
>
> https://screenshot.googleplex.com/4MpcsgGkkzUsC7V
>
> Will this GAQL bring the desired results?
>
>
> SELECT
>
> bidding_strategy_simulation.bidding_strategy_id,
>
> bidding_strategy_simulation.target_roas_point_list.points
>
> FROM bidding_strategy_simulation
>
> WHERE
>
> bidding_strategy_simulation.type = 'TARGET_ROAS'
>
> AND bidding_strategy_simulation.bidding_strategy_id = 1234
>
> AND bidding_strategy_simulation.start_date > '2022-11-17'
> AND bidding_strategy_simulation.start_date > '2022-11-27'
> AND bidding_strategy.target_roas.target_roas IN (400.0, 410.0)
>
>
>
>
>
> because some fields are output only, but I think we can filter by them:
>
> *bidding_strategy_simulation.end_date*
> Field description Output only. Last day on which the simulation is based, 
> in -MM-DD format
>
> --
>
> •  Elad Ben-David *(He / Him)*
>
> •  Customer Solutions Engineer
>
> •  el...@google.com
>
> •  Google EEM
>
> Available: Sun - Thu
>
>
>- New external solutions 
>
> 
>  
>we offer.
>- Always: go/nohi
>
>
>
>
>

-- 
-- 
=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~
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/2aa1099f-b6d1-42e2-a8a2-5d3b745e1235n%40googlegroups.com.

Problems with event API & marketing API

[keji dianfei]

Hi, I have two questions about the API.
The first one is about the event API, and I want to implement the data 
upload back by way of event API for my standalone site.
When testing, I found that no valid Gclid could not achieve the test. Is 
there any official test method I can use to test if the API is successful?
(I have read GA's documentation and didn't find a good way)
If not, I can only test the data by real ad placement.
Also, is there an official marketing API interface that can modify the 
account-level tracking template? If so, can you provide a link to the 
documentation? Thank you very much!

-- 
-- 
=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~
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/17ab8fb1-d359-4139-bc9e-97db194ddcc2n%40googlegroups.com.

Re: intermittent UNAUTHENTICATED errors: "The error code is not in this version"

[Anshu Tomar]

Hi,
Seems like the error is not coming anymore. We can close this thread. If it 
happens again, I will open up a new thread.
Thanks!

On Tuesday, November 15, 2022 at 9:59:33 PM UTC-5 adsapi wrote:

> Hi Anshu,
>
> Thank you for the reply.
>
> For our team to further check and validate the errors you are getting in 
> some runs, could you provide us with the updated complete API logs (
> request 
> 
>  and response 
> 
>  with request-id 
> )
>  
> generated on your end? Note that this can be requested or provided to the 
> developer handling the Google Ads API transactions when logging of the API 
> requests has been enabled. You may check here 
> 
>  
> and click your client library for the specific guideline to enable it.
>
> For REST interface requests, you can enable logging via the curl command 
> by using the -i flag. This will cause the tool to include the HTTP response 
> headers in the output.
>
> You may then send the requested information via the Reply privately to the 
> 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] 
> Heidi 
> Google Ads API Team 
>   ​​​
>
> ref:_00D1U1174p._5004Q2gOhVt: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/be65181e-2d65-4489-867e-452227c86c8bn%40googlegroups.com.

Re: Google Ads Test Account Does Not Function As Expected

['Google Ads API Forum Advisor' via Google Ads API and AdWords API Forum]

Hello,

Thank you for your detailed response. I'm sharing this information with our 
OAuth team and working with them to try to figure out the best steps to 
proceed. I will let you know when I have any new information to share, or if I 
need more information from you.

Regards,
Mike, Google Ads API Team
ref:_00D1U1174p._5004Q2ewsYl: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/x2Azk0RLJRCU00ruRMDWLsQoGGFM5JAt4ntw%40sfdc.net.

Google.ads.googleads.v10.services.GoogleAdsService.Search

[Eric Xu]

Today, our API call mostly mostly failed，response is like below：

Status: Status{code=RESOURCE_EXHAUSTED, description=Resource has been 
exhausted (e.g. check quota)., cause=null}.
com.google.ads.googleads.v10.errors.GoogleAdsException: errors {
error_code {
quota_error: RESOURCE_EXHAUSTED
}
message: "Too many requests. Retry in 786 seconds."
details {
quota_error_details {
rate_scope: DEVELOPER
rate_name: "Number of operations for basic access"
retry_delay {
seconds: 786
}
}
}
}
request_id: "QQqB23VyM4IvGL3gCIXhVw"


But the truth is that: we didn't make more api calls today,  from latest 
week‘s api call histories, our api call times not reached 15000 whole day. 
Anyone has meet the issues?
Pls give me some advice.

-- 
-- 
=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~
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/951d5c97-56e6-4451-8ea1-b2e2472ebc17n%40googlegroups.com.

Re: ad_group_audience_view, ad_group_criterion.type = UNKNOWN

['Google Ads API Forum Advisor' via Google Ads API and AdWords API Forum]

Hi,

Thank you for sending response privately. We will check and reply on their 
thread.

Thanks,

Nirmita
Google Ads API Team
ref:_00D1U1174p._5004Q2g3RyN: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/kgQ3Y0RLJU1L00VhYyJP7pRaajY5Zlr905Sw%40sfdc.net.

Re: Trying to Reproduce the Payload for Getting a Refresh Token

[Chad Wood]

By the way, I had submitted a pretty detailed and nicely formatted message 
of the process and my goal--hoping that it would make everything super 
clear for whoever is able to help me.
But, for some reason, at the time all my messages were automatically 
getting marked as "Message has been deleted".

I assume this was some kind of automatic block I must have triggered, and 
maybe a review lifted it? I don't know.
But, I am wondering if you guys can still see those messages. 

The one directly after my message stamped for Nov 17, 2022, 8:14:48 AM is 
the one that has really clear details on all of this.

On Thursday, November 17, 2022 at 2:46:06 PM UTC-8 Chad Wood wrote:

> Thanks. I'll keep an eye out until then.
>
> On Thursday, November 17, 2022 at 1:45:50 PM UTC-8 adsapi wrote:
>
>> Hi Chad,
>>
>> Thanks for your patience on this and for your detailed description. 
>> Please allow me to raise this question to our team. We will provide an 
>> update on this shortly.
>>
>> Thanks,
>>
>> [image: Google Logo] 
>> Matt 
>> Google Ads API Team 
>>   
>>
>> ref:_00D1U1174p._5004Q2gPExm: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/b157ffda-8566-44ab-9d1d-b5dce5d04d46n%40googlegroups.com.

Re: Google Ads Test Account Does Not Function As Expected

[Chad Wood]

Thanks, I will keep a watch out until then!

On Friday, November 18, 2022 at 6:10:26 AM UTC-8 adsapi wrote:

> Hello,
>
> Thank you for your detailed response. I'm sharing this information with 
> our OAuth team and working with them to try to figure out the best steps to 
> proceed. I will let you know when I have any new information to share, or 
> if I need more information from you.
>
>
> Regards,
> Mike, Google Ads API Team
>
> ref:_00D1U1174p._5004Q2ewsYl: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/0f130990-bb2b-435b-b8a0-60b85d2356dbn%40googlegroups.com.

Re: Rest API refresh token. revoked in 1 hour

[Duvan Felipe Buritica Cardona]

hello dears,

According to this example, because this request only returns the access
token and not the refresh token.

https://accounts.google.com/o/oauth2/v2/auth?

 scope=https%3A//www.googleapis.com/auth/adwords&

 access_type=offline&

 include_granted_scopes=true&

 response_type=code&

 state=*state*&

 redirect_uri=*https://app.roalytics.com/auth
**&*


 client_id=10836400011x

x


the scope  scope=https%3A//www.googleapis.com/auth/drive.metadata.readonly&


This does return both tokens.


thanks

El vie, 4 nov 2022 a las 3:34, Google Ads API Forum Advisor
() escribió:

> Hi,
>
> Thank you for the reply.
>
> As stated by my colleague Yasar, "*you may use our client libraries
>  where
> refresh tokens do not expire for a long time if your OAuth app is already
> verified and it does handle access tokens itself*,"  and since you
> mentioned that your backend is Python (API Python), then I would recommend
> you check this documentation
> 
> as it has the instructions on how to generate an OAuth2 refresh token and
> set up the configuration file for your client.
>
> Best regards,
> [image: Google Logo]
> Heidi
> Google Ads API Team
>
>
> ref:_00D1U1174p._5004Q2fp4Ks: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/CAD86o6A35Sxxm1_%3D5GNhtfsu_wM%2B-yPjsZ6ar9iCviW93yO7FA%40mail.gmail.com.

Re: Trying to Reproduce the Payload for Getting a Refresh Token

[Chad Wood]

An example of the payload I'd like to reproduce (values changed slightly 
for security):
you can see at index 2 in f.req, also at

{'f.req': [True,
  
'!ChRxa0FhVGI1X294dHwOOsPwQrVIMxIfZ3g3TmFyZklDMFlTa013TWpqbVNUV1h5Vk17D3KqZw∙AD98QVYAY3VIexEJuF7PQTpFZd2Q1Zaaw8v28Dg4',
  None,
  None,
  ['gf.sad', ['https://www.googleapis.com/auth/adwords'], [], []],
  [None,
  
 '916612797391-ne8g1sk544gd9vj85ci37elkdmf936nn.apps.googleusercontent.com',
   ['https://www.googleapis.com/auth/adwords'],
  
 
'!ChRxa0FhVGI1X294dHwOOsPwQrVIMxIfZ3g3TmFyZklDMFlTa013TWpqbVNUV1h5Vk17D3KqZw∙AD98QVYAY3VIexEJuF7PQTpFZd2Q1Zaaw8v28Dg4,
   None,
   None,
   None,
   None,
   None,
   None,
   None,
   'http://127.0.0.1:8080',
   None,
   False,
   None,
   None,
   None,
   True,
   None,
   None,
   None,
   None,
   14,
   None,
   True,
   [],
   False,
   False,
   True,
   None,
   [['https://www.googleapis.com/auth/adwords', 1200, False, False]],
   None,
   True,
   None,
   1,
   True,
   None,
   None,
   2,
   False,
   None,
   False]],
 'at': 'AFofLUWPdG5b6SxxxapPWk_JaKsQI9uqcA:1643372251920'} 

On Tuesday, November 15, 2022 at 3:10:02 PM UTC-8 Chad Wood wrote:

> https://groups.google.com/g/adwords-api/c/bAgqtTr5OoY
> This issue has branched into a follow up question that should probably be 
> handled separately.
>
> I'm investigating the process of requesting refresh tokens. I use the 
> client library for Python titled "generate_user_credentials.py" for Desktop 
> app flow. In truth, the app is just querying data from Ads and using it for 
> internal reporting.
>
> The library spins up a server that waits for a callback with a string 
> query specifying:
> 1. state
> 2. code
> 3. scope
>
> State and Scope are easy to get, as they're provided in the original oauth 
> link used to authenticate. Code is much more difficult to reproduce, though 
> it seems that you guys actually generate that on your end and send back in 
> one of the page's POST requests.
>
> So I investigated that POST request, which goes to "
> https://accounts.google.com/signin/oauth/consent/approval";. It appears to 
> require the following:
> *params:*
> 1. authuser
> *headers:*
> 1.Content-Type
> 2.Cookie
> *payload:*
> f.req = some_array
> at = some_string
>
> Most of these seem to be constants, but I am struggling with the *some_array 
> *and *some_string* values.
>
> *some_array *contains a token that begins with "!ChR" + a ' ∙ ' separator 
> for a second value, and I can not reproduce it so far. It must be generated 
> client-side, as I have checked all incoming data for this token and can not 
> find it. I have the feeling it's a hash of something else, but when 
> reviewing the javascript I was completely lost. I don't know javascript, so 
> it's difficult to read (on top of there being A LOT of js to sort through).
>
> I haven't gotten to the *at *variable that contains its own token yet, 
> but I'll need to understand how this is generated as well.
>
> Can someone help me get to a point where I can reproduce the token 
> beginning with "!ChR"? Also the value for "at" in the payload.
>
> Thank you
>
>

-- 
-- 
=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~
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/e6587b9f-e46d-46f5-9b65-9c81b9116458n%40googlegroups.com.

Re: Trying to Reproduce the Payload for Getting a Refresh Token

[Chad Wood]

See, if I break the process down into steps:

1. Your application redirects a browser to a Google URL
1a. the URL includes query parameters that indicate the type of access 
being requested
1b. importantly, this includes "scope" and "state"

2. You select the Google Account you want to authorize
3. You review the app permissions
4. You hit "Confirm"

5. Your browser compiles a payload to be sent to Google authorization 
server.
5a. this payload is, in part, used to verify the type of access and 
verify that the request is valid--not a bad actor
5b. this payload includes two REQUIRED variables, "f.req" and "at"
5c. this variable "f.req" contains a bunch of data (in a "list") 
specifying everything about the request, to include a token that begins 
with "!ChR"at index 1
5d. If I were to manually send this same request inside my program, I 
could collect the same response from your validation server--giving tighter 
control over the process

So addressing 5d. I want to be able to manually send the request. This 
means that I need to manually reproduce the variables required by your 
authorization server. 
By my tests, only "f.req" and "at" are required for a valid response. 

So to reproduce "f.req", it's actually pretty simple for the most part. *Where 
the problem arises is the value at index 1. I can not figure out where it 
comes from.*

Here's what I think I know about this value:
1. It is not in any responses from the Google server that come as a result 
of completing steps 1-5. I have searched ALL responses, and this value is 
not in them.
2. Therefore, I believe the value is generated by my browser. 
3. Since this is a Google protocol, Google created the functions that 
output this value, to send to the authorization server. Google put them in 
the webpages files, and it instructs my browser on how to generate the code.

I just want more info on how to do it manually, rather than allowing my 
browser to do it.

On Thursday, November 17, 2022 at 8:14:48 AM UTC-8 Chad Wood wrote:

> Thanks, and you are right that the access token and refresh token is 
> generated by Google side.
>
> About this: "the URL includes query parameters that indicate the type of 
> access being requested"
> This is also correct. Here's what the url would look like:
>
> https:// accounts. google. com/o/oauth2/auth?
> response_type=code&
> client_id=
> 995929737391-l3og1l1d44gpf4985e0l7elkk4b26nn.apps.googleusercontent.com&
> redirect_uri=http%3A%2F%2F127.0.0.1%3A8080&
> scope=https%3A%2F%2Fwww.googleapis.com
> %2Fauth%2Fadwords&state=efcck0648b44377bedj20e97d2eca2745ba5979cf2cfa4sk30d2da6365sk2681&
> access_type=offline&prompt=consent&
> include_granted_scopes=true
>
> See the parameters it's talking about here are:  response_type, client_id, 
> redirect_uri, scope,  access_type, and  include_granted_scopes 
>
> What I'm talking about goes deeper into the process than any documentation 
> covers though. See, on my side of things, the browser actually generates a 
> "code" that it eventually sends to your server once I hit the "Confirm" 
> button.
> That "code" is what I showed in the picture from my last message (section 
> three). This code is basically verified by your server, as a type of 
> security feature I assume. As it would likely be very difficult for a bad 
> actor to get all the input data needed to reproduce that "code".
>
> But I am not a bad actor. I basically want to reproduce that "code" inside 
> my own personal program--not inside a browser. This way, I can send 
> authorization requests to your server manually.
> I have tested ripping the payload from the browser and sending it in my 
> program. In this case, your server WILL respond with the redirect URL 
> containing the refresh token. This is confirmed working.
> The only issue is that it requires me to manually rip the payload, which 
> defeats the entire purpose. 
>
> Now, I can reproduce most of the payload. The only part I can not 
> reproduce is the "code" I am referring to. It is at index 1 of the "f.req" 
> variable inside the payload.
> Somehow, my browser is generating this "code" using the page's JavaScript 
> instruction to do so. Then it places the "code" inside an array labeled 
> "f.req" and sends that to your server. Your server validates it and 
> responds with the refresh token stuff.
>
> I only want to understand how that "code" is created. What is my browser 
> doing? Is it hashing cookie variables? If so, what type of hash and which 
> variables?
> Again, it is the token that always begins with "!ChR" at index 1 of 
> variable "f.req" in the payload that gets sent to your authorization server 
> for the refresh token.
>
> Can I have more insight on how my browser generates this code/token? I 
> tried reviewing the JavaScript in the page, but it's a mile long and none 
> of the function names appear meaningful--so it is very difficult to figure 
> out,
> On Wednesday, November 16, 2022 at 5

Re: Trying to Reproduce the Payload for Getting a Refresh Token

[Chad Wood]

 See, if I break the process down into steps:

1. Your application redirects a browser to a Google URL
1a. the URL includes query parameters that indicate the type of access 
being requested
1b. importantly, this includes "scope" and "state"

2. You select the Google Account you want to authorize
3. You review the app permissions
4. You hit "Confirm"

5. Your browser compiles a payload to be sent to Google authorization 
server.
5a. this payload is, in part, used to verify the type of access and 
verify that the request is valid--not a bad actor
5b. this payload includes two REQUIRED variables, "f.req" and "at"
5c. this variable "f.req" contains a bunch of data (in a "list") 
specifying everything about the request, to include a token that begins 
with "!ChR"at index 1
5d. If I were to manually send this same request inside my program, I 
could collect the same response from your validation server--giving tighter 
control over the process

So addressing 5d. I want to be able to manually send the request. This 
means that I need to manually reproduce the variables required by your 
authorization server. 
By my tests, only "f.req" and "at" are required for a valid response. 

So to reproduce "f.req", it's actually pretty simple for the most part. *Where 
the problem arises is the value at index 1. I can not figure out where it 
comes from.*

Here's what I think I know about this value:
1. It is not in any responses from the Google server that come as a result 
of completing steps 1-5. I have searched ALL responses, and this value is 
not in them.
2. Therefore, I believe the value is generated by my browser. 
3. Since this is a Google protocol, Google created the functions that 
output this value, to send to the authorization server. Google put them in 
the webpages files, and it instructs my browser on how to generate the code.

I just want more info on how to do it manually, rather than allowing my 
browser to do it.


On Thursday, November 17, 2022 at 8:14:48 AM UTC-8 Chad Wood wrote:

> Thanks, and you are right that the access token and refresh token is 
> generated by Google side.
>
> About this: "the URL includes query parameters that indicate the type of 
> access being requested"
> This is also correct. Here's what the url would look like:
>
> https:// accounts. google. com/o/oauth2/auth?
> response_type=code&
> client_id=
> 995929737391-l3og1l1d44gpf4985e0l7elkk4b26nn.apps.googleusercontent.com&
> redirect_uri=http%3A%2F%2F127.0.0.1%3A8080&
> scope=https%3A%2F%2Fwww.googleapis.com
> %2Fauth%2Fadwords&state=efcck0648b44377bedj20e97d2eca2745ba5979cf2cfa4sk30d2da6365sk2681&
> access_type=offline&prompt=consent&
> include_granted_scopes=true
>
> See the parameters it's talking about here are:  response_type, client_id, 
> redirect_uri, scope,  access_type, and  include_granted_scopes 
>
> What I'm talking about goes deeper into the process than any documentation 
> covers though. See, on my side of things, the browser actually generates a 
> "code" that it eventually sends to your server once I hit the "Confirm" 
> button.
> That "code" is what I showed in the picture from my last message (section 
> three). This code is basically verified by your server, as a type of 
> security feature I assume. As it would likely be very difficult for a bad 
> actor to get all the input data needed to reproduce that "code".
>
> But I am not a bad actor. I basically want to reproduce that "code" inside 
> my own personal program--not inside a browser. This way, I can send 
> authorization requests to your server manually.
> I have tested ripping the payload from the browser and sending it in my 
> program. In this case, your server WILL respond with the redirect URL 
> containing the refresh token. This is confirmed working.
> The only issue is that it requires me to manually rip the payload, which 
> defeats the entire purpose. 
>
> Now, I can reproduce most of the payload. The only part I can not 
> reproduce is the "code" I am referring to. It is at index 1 of the "f.req" 
> variable inside the payload.
> Somehow, my browser is generating this "code" using the page's JavaScript 
> instruction to do so. Then it places the "code" inside an array labeled 
> "f.req" and sends that to your server. Your server validates it and 
> responds with the refresh token stuff.
>
> I only want to understand how that "code" is created. What is my browser 
> doing? Is it hashing cookie variables? If so, what type of hash and which 
> variables?
> Again, it is the token that always begins with "!ChR" at index 1 of 
> variable "f.req" in the payload that gets sent to your authorization server 
> for the refresh token.
>
> Can I have more insight on how my browser generates this code/token? I 
> tried reviewing the JavaScript in the page, but it's a mile long and none 
> of the function names appear meaningful--so it is very difficult to figure 
> out,
> On Wednesday, November 16, 2022 at

Re: Trying to Reproduce the Payload for Getting a Refresh Token

[Chad Wood]

 See, if I break the process down into steps:

1. Your application redirects a browser to a Google URL
1a. the URL includes query parameters that indicate the type of access 
being requested
1b. importantly, this includes "scope" and "state"

2. You select the Google Account you want to authorize
3. You review the app permissions
4. You hit "Confirm"

5. Your browser compiles a payload to be sent to Google authorization 
server.
5a. this payload is, in part, used to verify the type of access and 
verify that the request is valid--not a bad actor
5b. this payload includes two REQUIRED variables, "f.req" and "at"
5c. this variable "f.req" contains a bunch of data (in a "list") 
specifying everything about the request, to include a token that begins 
with "!ChR"at index 1
5d. If I were to manually send this same request inside my program, I 
could collect the same response from your validation server--giving tighter 
control over the process

On Thursday, November 17, 2022 at 8:14:48 AM UTC-8 Chad Wood wrote:

> Thanks, and you are right that the access token and refresh token is 
> generated by Google side.
>
> About this: "the URL includes query parameters that indicate the type of 
> access being requested"
> This is also correct. Here's what the url would look like:
>
> https:// accounts. google. com/o/oauth2/auth?
> response_type=code&
> client_id=
> 995929737391-l3og1l1d44gpf4985e0l7elkk4b26nn.apps.googleusercontent.com&
> redirect_uri=http%3A%2F%2F127.0.0.1%3A8080&
> scope=https%3A%2F%2Fwww.googleapis.com
> %2Fauth%2Fadwords&state=efcck0648b44377bedj20e97d2eca2745ba5979cf2cfa4sk30d2da6365sk2681&
> access_type=offline&prompt=consent&
> include_granted_scopes=true
>
> See the parameters it's talking about here are:  response_type, client_id, 
> redirect_uri, scope,  access_type, and  include_granted_scopes 
>
> What I'm talking about goes deeper into the process than any documentation 
> covers though. See, on my side of things, the browser actually generates a 
> "code" that it eventually sends to your server once I hit the "Confirm" 
> button.
> That "code" is what I showed in the picture from my last message (section 
> three). This code is basically verified by your server, as a type of 
> security feature I assume. As it would likely be very difficult for a bad 
> actor to get all the input data needed to reproduce that "code".
>
> But I am not a bad actor. I basically want to reproduce that "code" inside 
> my own personal program--not inside a browser. This way, I can send 
> authorization requests to your server manually.
> I have tested ripping the payload from the browser and sending it in my 
> program. In this case, your server WILL respond with the redirect URL 
> containing the refresh token. This is confirmed working.
> The only issue is that it requires me to manually rip the payload, which 
> defeats the entire purpose. 
>
> Now, I can reproduce most of the payload. The only part I can not 
> reproduce is the "code" I am referring to. It is at index 1 of the "f.req" 
> variable inside the payload.
> Somehow, my browser is generating this "code" using the page's JavaScript 
> instruction to do so. Then it places the "code" inside an array labeled 
> "f.req" and sends that to your server. Your server validates it and 
> responds with the refresh token stuff.
>
> I only want to understand how that "code" is created. What is my browser 
> doing? Is it hashing cookie variables? If so, what type of hash and which 
> variables?
> Again, it is the token that always begins with "!ChR" at index 1 of 
> variable "f.req" in the payload that gets sent to your authorization server 
> for the refresh token.
>
> Can I have more insight on how my browser generates this code/token? I 
> tried reviewing the JavaScript in the page, but it's a mile long and none 
> of the function names appear meaningful--so it is very difficult to figure 
> out,
> On Wednesday, November 16, 2022 at 5:41:44 PM UTC-8 adsapi wrote:
>
>> Hi Chadwood,
>>
>> Thank you for getting back to us.
>>
>> Thank you for providing us your main goal. Please note that Google the 
>> access token and refresh token is generated by Google side. Based on this 
>> article 
>>  "The 
>> authorization sequence begins when your application redirects a browser to 
>> a Google URL; the URL includes query parameters that indicate the type of 
>> access being requested. Google handles the user authentication, session 
>> selection, and user consent. The result is an authorization code, which the 
>> application can exchange for an access token and a refresh token.
>>
>> You may check this article 
>> 
>>  for 
>> more information.
>>
>>
>> Kind regards, 
>> [image: Google Logo] 
>> Sherwin Vincent 
>> Google Ads API Team 
>>   
>>
>> ref:_00D

In-Market & Affinity Campaign Targeting

[Adam Walters]

Hello, 

I have been trying to find examples, but have been unable to find any. What 
is the proper way to add an In-Market audience to a campaign via API v11, 
python?

I have tried reworking other targeting criteria examples but have been 
unsuccessful.

Thank you,
Ada,

-- 
-- 
=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~
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/5c509956-c8ee-4a98-88f0-81a6bae3a0e4n%40googlegroups.com.