Hi, As requested, sharing more details for futher investigation. Please find log attachment as below
- Update Rename Call : "customer_rename_post_call.txt" - Fetch Call for customer_client, inital report: "customer_rename_fetch_call_not_updated.txt" - Fetch Call for customer_client, updated name report: "cutomer_rename_fetch_call_updated.txt" This time it took around 20 mins to get updated in report, Let us know in case more details required On Thursday, March 31, 2022 at 5:53:45 AM UTC+5:30 adsapi wrote: > Hi Vijay, > > Thank you for the reply. I am also a member of the Google Ads API team and > let me provide support to your concern. > > I tried changing the name of my test client and requested a report to get > the updated name, however, I wasn't able to replicate the issue on my end > as the update reflected immediately. With this, could you provide the > following details to further investigate? > > - complete request > > <https://developers.google.com/google-ads/api/docs/concepts/field-service#request> > and response > > <https://developers.google.com/google-ads/api/docs/concepts/field-service#response> > logs with request ID > > <https://developers.google.com/google-ads/api/docs/concepts/call-structure#request-id> > and request header > > <https://developers.google.com/google-ads/api/docs/concepts/call-structure#request_headers> > generated > on your end for updating the name with timestamp > - complete request > > <https://developers.google.com/google-ads/api/docs/concepts/field-service#request> > and response > > <https://developers.google.com/google-ads/api/docs/concepts/field-service#response> > logs with request ID > > <https://developers.google.com/google-ads/api/docs/concepts/call-structure#request-id> > and request header > > <https://developers.google.com/google-ads/api/docs/concepts/call-structure#request_headers> > generated > on your end for the initial report where updated name could not be seen > with timestamp > - complete request > > <https://developers.google.com/google-ads/api/docs/concepts/field-service#request> > and response > > <https://developers.google.com/google-ads/api/docs/concepts/field-service#response> > logs with request ID > > <https://developers.google.com/google-ads/api/docs/concepts/call-structure#request-id> > and request header > > <https://developers.google.com/google-ads/api/docs/concepts/call-structure#request_headers> > generated > on your end for the report executed after 5 minutes and the updated name > could be seen with timestamp > > > You can provide it via *Reply privately to author* option. If this option > is not available, then send it instead on this email address > googleadsa...@google.com. > > Regards, > [image: Google Logo] > Ernie John > Google Ads API Team > > > ref:_00D1U1174p._5004Q2YsSJt: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/7f4bcc11-fee3-42a9-9d40-7f0e5ff05d64n%40googlegroups.com.
$ curl -v --request POST 'https://googleads.googleapis.com/v10/customers/7971990847:mutate?access_token=__ACCESS_TOKEN__' \ > --header 'login-customer-id: 7766387250' \ > --header 'developer-token: __DEV_TOKEN__' \ > --header 'Content-Type: application/json' \ > --data-raw '{ > "validate_only": false, > "operation": { > "update": { > "resourceName": "customers/7971990847", > "descriptiveName": "Test dukan-rem account" > }, > "updateMask" : "descriptiveName" > }, > "customer_id": "7971990847" > }' Note: Unnecessary use of -X or --request, POST is already inferred. * Trying 172.217.174.74:443... * TCP_NODELAY set * Connected to googleads.googleapis.com (172.217.174.74) port 443 (#0) * ALPN, offering h2 * ALPN, offering http/1.1 * successfully set certificate verify locations: * CAfile: /etc/ssl/certs/ca-certificates.crt CApath: /etc/ssl/certs * TLSv1.3 (OUT), TLS handshake, Client hello (1): * TLSv1.3 (IN), TLS handshake, Server hello (2): * TLSv1.3 (IN), TLS handshake, Encrypted Extensions (8): * TLSv1.3 (IN), TLS handshake, Certificate (11): * TLSv1.3 (IN), TLS handshake, CERT verify (15): * TLSv1.3 (IN), TLS handshake, Finished (20): * TLSv1.3 (OUT), TLS change cipher, Change cipher spec (1): * TLSv1.3 (OUT), TLS handshake, Finished (20): * SSL connection using TLSv1.3 / TLS_AES_256_GCM_SHA384 * ALPN, server accepted to use h2 * Server certificate: * subject: CN=upload.video.google.com * start date: Mar 17 11:24:21 2022 GMT * expire date: Jun 9 11:24:20 2022 GMT * subjectAltName: host "googleads.googleapis.com" matched cert's "*.googleapis.com" * issuer: C=US; O=Google Trust Services LLC; CN=GTS CA 1C3 * SSL certificate verify ok. * Using HTTP2, server supports multi-use * Connection state changed (HTTP/2 confirmed) * Copying HTTP/2 data in stream buffer to connection buffer after upgrade: len=0 * Using Stream ID: 1 (easy handle 0x559a410bce30) > POST /v10/customers/7971990847:mutate?access_token=__ACCESS_TOKEN__ HTTP/2 > Host: googleads.googleapis.com > user-agent: curl/7.68.0 > accept: */* > login-customer-id: 7766387250 > developer-token: __DEV_TOKEN__ > content-type: application/json > content-length: 269 > * We are completely uploaded and fine * TLSv1.3 (IN), TLS handshake, Newsession Ticket (4): * TLSv1.3 (IN), TLS handshake, Newsession Ticket (4): * old SSL session ID is stale, removing * Connection state changed (MAX_CONCURRENT_STREAMS == 100)! < HTTP/2 200 < request-id: hAiKJM7lp6T-zLG5aUpMCQ < content-type: application/json; charset=UTF-8 < vary: X-Origin < vary: Referer < vary: Origin,Accept-Encoding < date: Thu, 31 Mar 2022 09:05:50 GMT < server: ESF < cache-control: private < x-xss-protection: 0 < x-frame-options: SAMEORIGIN < x-content-type-options: nosniff < alt-svc: h3=":443"; ma=2592000,h3-29=":443"; ma=2592000,h3-Q050=":443"; ma=2592000,h3-Q046=":443"; ma=2592000,h3-Q043=":443"; ma=2592000,quic=":443"; ma=2592000; v="46,43" < accept-ranges: none < { "result": { "resourceName": "customers/7971990847" } } * Connection #0 to host googleads.googleapis.com left intact
vijay.bang@dell-Inspiron-3501:~$ curl -v --request POST 'https://googleads.googleapis.com/v10/customers/9657529098/googleAds:search?access_token=__ACCESS_TOKEN__' --header 'login-customer-id: 7766387250' --header 'developer-token: __DEV_TOKEN__' --header 'Content-Type: application/json' --data-raw '{ "pageSize": 1, "query": "SELECT customer_client.descriptive_name, customer_client.id FROM customer_client WHERE customer_client.id = 7971990847" }' Note: Unnecessary use of -X or --request, POST is already inferred. * Trying 142.250.67.138:443... * TCP_NODELAY set * Connected to googleads.googleapis.com (142.250.67.138) port 443 (#0) * ALPN, offering h2 * ALPN, offering http/1.1 * successfully set certificate verify locations: * CAfile: /etc/ssl/certs/ca-certificates.crt CApath: /etc/ssl/certs * TLSv1.3 (OUT), TLS handshake, Client hello (1): * TLSv1.3 (IN), TLS handshake, Server hello (2): * TLSv1.3 (IN), TLS handshake, Encrypted Extensions (8): * TLSv1.3 (IN), TLS handshake, Certificate (11): * TLSv1.3 (IN), TLS handshake, CERT verify (15): * TLSv1.3 (IN), TLS handshake, Finished (20): * TLSv1.3 (OUT), TLS change cipher, Change cipher spec (1): * TLSv1.3 (OUT), TLS handshake, Finished (20): * SSL connection using TLSv1.3 / TLS_AES_256_GCM_SHA384 * ALPN, server accepted to use h2 * Server certificate: * subject: CN=upload.video.google.com * start date: Mar 17 11:24:21 2022 GMT * expire date: Jun 9 11:24:20 2022 GMT * subjectAltName: host "googleads.googleapis.com" matched cert's "*.googleapis.com" * issuer: C=US; O=Google Trust Services LLC; CN=GTS CA 1C3 * SSL certificate verify ok. * Using HTTP2, server supports multi-use * Connection state changed (HTTP/2 confirmed) * Copying HTTP/2 data in stream buffer to connection buffer after upgrade: len=0 * Using Stream ID: 1 (easy handle 0x562ca16f4e30) > POST /v10/customers/9657529098/googleAds:search?access_token=__ACCESS_TOKEN__ > HTTP/2 > Host: googleads.googleapis.com > user-agent: curl/7.68.0 > accept: */* > login-customer-id: 7766387250 > developer-token: __DEV_TOKEN__ > content-type: application/json > content-length: 148 > * We are completely uploaded and fine * TLSv1.3 (IN), TLS handshake, Newsession Ticket (4): * TLSv1.3 (IN), TLS handshake, Newsession Ticket (4): * old SSL session ID is stale, removing * Connection state changed (MAX_CONCURRENT_STREAMS == 100)! < HTTP/2 200 < request-id: vigdLb1JRNR1gxLhd0HTGQ < content-type: application/json; charset=UTF-8 < vary: X-Origin < vary: Referer < vary: Origin,Accept-Encoding < date: Thu, 31 Mar 2022 09:25:31 GMT < server: ESF < cache-control: private < x-xss-protection: 0 < x-frame-options: SAMEORIGIN < x-content-type-options: nosniff < alt-svc: h3=":443"; ma=2592000,h3-29=":443"; ma=2592000,h3-Q050=":443"; ma=2592000,h3-Q046=":443"; ma=2592000,h3-Q043=":443"; ma=2592000,quic=":443"; ma=2592000; v="46,43" < accept-ranges: none < { "results": [ { "customerClient": { "resourceName": "customers/9657529098/customerClients/7971990847", "descriptiveName": "Test dukan-rem account", "id": "7971990847" } } ], "fieldMask": "customerClient.descriptiveName,customerClient.id" } * Connection #0 to host googleads.googleapis.com left intact
$ curl -v --request POST 'https://googleads.googleapis.com/v10/customers/9657529098/googleAds:search?access_token=__ACCESS_TOKEN__' \ > --header 'login-customer-id: 7766387250' \ > --header 'developer-token: __DEV_TOKEN__' \ > --header 'Content-Type: application/json' \ > --data-raw '{ > "pageSize": 1, > "query": "SELECT customer_client.descriptive_name, customer_client.id FROM > customer_client WHERE customer_client.id = 7971990847" > }' Note: Unnecessary use of -X or --request, POST is already inferred. * Trying 172.217.166.74:443... * TCP_NODELAY set * Connected to googleads.googleapis.com (172.217.166.74) port 443 (#0) * ALPN, offering h2 * ALPN, offering http/1.1 * successfully set certificate verify locations: * CAfile: /etc/ssl/certs/ca-certificates.crt CApath: /etc/ssl/certs * TLSv1.3 (OUT), TLS handshake, Client hello (1): * TLSv1.3 (IN), TLS handshake, Server hello (2): * TLSv1.3 (IN), TLS handshake, Encrypted Extensions (8): * TLSv1.3 (IN), TLS handshake, Certificate (11): * TLSv1.3 (IN), TLS handshake, CERT verify (15): * TLSv1.3 (IN), TLS handshake, Finished (20): * TLSv1.3 (OUT), TLS change cipher, Change cipher spec (1): * TLSv1.3 (OUT), TLS handshake, Finished (20): * SSL connection using TLSv1.3 / TLS_AES_256_GCM_SHA384 * ALPN, server accepted to use h2 * Server certificate: * subject: CN=upload.video.google.com * start date: Mar 17 11:24:21 2022 GMT * expire date: Jun 9 11:24:20 2022 GMT * subjectAltName: host "googleads.googleapis.com" matched cert's "*.googleapis.com" * issuer: C=US; O=Google Trust Services LLC; CN=GTS CA 1C3 * SSL certificate verify ok. * Using HTTP2, server supports multi-use * Connection state changed (HTTP/2 confirmed) * Copying HTTP/2 data in stream buffer to connection buffer after upgrade: len=0 * Using Stream ID: 1 (easy handle 0x56298f4eae30) > POST /v10/customers/9657529098/googleAds:search?access_token=__ACCESS_TOKEN__ > HTTP/2 > Host: googleads.googleapis.com > user-agent: curl/7.68.0 > accept: */* > login-customer-id: 7766387250 > developer-token: __DEV_TOKEN__ > content-type: application/json > content-length: 148 > * We are completely uploaded and fine * TLSv1.3 (IN), TLS handshake, Newsession Ticket (4): * TLSv1.3 (IN), TLS handshake, Newsession Ticket (4): * old SSL session ID is stale, removing * Connection state changed (MAX_CONCURRENT_STREAMS == 100)! < HTTP/2 200 < request-id: RYYi0EAliuSwnUCUZp79Kg < content-type: application/json; charset=UTF-8 < vary: X-Origin < vary: Referer < vary: Origin,Accept-Encoding < date: Thu, 31 Mar 2022 09:06:06 GMT < server: ESF < cache-control: private < x-xss-protection: 0 < x-frame-options: SAMEORIGIN < x-content-type-options: nosniff < alt-svc: h3=":443"; ma=2592000,h3-29=":443"; ma=2592000,h3-Q050=":443"; ma=2592000,h3-Q046=":443"; ma=2592000,h3-Q043=":443"; ma=2592000,quic=":443"; ma=2592000; v="46,43" < accept-ranges: none < { "results": [ { "customerClient": { "resourceName": "customers/9657529098/customerClients/7971990847", "descriptiveName": "OS-Adwords-Account-Pool Asia/Kolkata INR", "id": "7971990847" } } ], "fieldMask": "customerClient.descriptiveName,customerClient.id" } * Connection #0 to host googleads.googleapis.com left intact
