Lag in Google Ads API Rename Account Name

[Vijay Bang]

Hi,

We are facing lag in renaming google account using google ads api.

New Account Name is not getting reflected although call is Successful.

Checking after 5 mins Account name got reflected.

curl --location --request POST 'https://googleads.googleapis.com/v10/customers/1807819439:mutate?access_token=${access_token}' \
--header 'login-customer-id: 7766387250' \
--header 'developer-token: ${developer_token}' \
--header 'Content-Type: application/json' \
--data-raw '{
    "validate_only": false,
    "operation": {
        "update": {
            "resourceName": "customers/1807819439",
            "descriptiveName": "Test dukan-rem account"
        },
        "updateMask" : "descriptiveName"
    },
    "customer_id": "1807819439"
}'

[Google Ads API Forum Advisor]

Hi Vijay,

Could you confirm if the lag in the update is observed through the Google Ads UI or the Google Ads API?

I asked because through a separate Google Ads API request, you should be able to perform a succeeding customer report request to check whether the updates to the said customer have already reflected.

For lags observed in the Google Ads UI, you may clarify this with the Google Ads Product support team, via this link.

Best regards,

Peter Laurence Google Ads API Team

ref:_00D1U1174p._5004Q2YsSJt:ref

[Vijay Bang]

Hi,

Lag is present in account rename Google Ads API.

My Concern is, If we are  updating Account using Google Ads API then Updated Account details should relfect is in google ads API fetch.

Currently Lag is present in both customer as well as customer_client API.

Also let us know, how much amount of lag can occur to reflect in this both fetch API's after Account rename

[Google Ads API Forum Advisor]

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 and response logs with request ID and request header generated on your end for updating the name with timestamp
• complete request and response logs with request ID and request header generated on your end for the initial report where updated name could not be seen with timestamp
• complete request and response logs with request ID and request header 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,

Ernie John Google Ads API Team

ref:_00D1U1174p._5004Q2YsSJt:ref

[Google Ads API Forum Advisor]

Hi Vijay,

Thank you for providing more details to your concern.

I would like to inform you that I am going to remove your latest post as it contains generated logs. However, allow me to paste below your reply without attached files:

"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"

Allow me to raise the issue to my team to further investigate. Rest assured that we will provide updates when available.

[Google Ads API Forum Advisor]

Hi Vijay,

Thanks for sharing all of this information. So far we've been unable to reproduce this behavior, so I wonder if there might be something network related going on. First, a couple questions:

1. Does this behavior occur with other resources? For example campaigns, ad_groups, etc?
2. Are you running these requests from a network that might have some kind of response caching enabled? If you test this from a different network, is the behavior different?

Thanks,
Ben, Google Ads API Team

ref:_00D1U1174p._5004Q2YsSJt:ref

[Vijay Bang]

Hi Google Team,

Replying inline to the questions

On Friday, April 1, 2022 at 11:02:23 PM UTC+5:30 adsapi wrote:

Hi Vijay,

Thanks for sharing all of this information. So far we've been unable to reproduce this behavior, so I wonder if there might be something network related going on. First, a couple questions:

1. Does this behavior occur with other resources? For example campaigns, ad_groups, etc?

=> We havn't yet identified such  behavior in other resources like campaigns

1. Are you running these requests from a network that might have some kind of response caching enabled? If you test this from a different network, is the behavior different?

=> No We are not doing these requests from any caching enabled network, Also We are calling directly to the google ads api through curl command as shared above, also response-Id in header is different in each subsequent requests.

Please let us know in case more details are required.

[Google Ads API Forum Advisor]

Hi Vijay,

Thanks for confirming this. Just to double-check, does this for all of your accounts, or only specific ones? And does it happen consistently any time you update, or just occassionaly? I'm going to share these details internally to see if there's an explanation.

Best,

[Vijay Bang]

Hi Google Team,

This issue is still present and happening very frequently for many accounts.

[Google Ads API Forum Advisor]

Hi Vijay,

Thanks for confirming - we're looking into the issue and will follow up here with more details as soon as possible.

[Vijay Bang]

Hi Google Team,

any updates?

[Google Ads API Forum Advisor]

Hi Vijay,

Apologies for the delay, I'm still coordinating internally to determine a root cause. I will follow up here as soon as I have more information.

[Vijay Bang]

Hi Google Team,

Any updates?

By when can we expect a fix here?  Adwords API are already deprecated now.

[Google Ads API Forum Advisor]

Hello Vijay,

I'm taking over this thread from Ben. This is currently still under investigation. I'll continue to keep an eye on it.

Regards,

Nadine Wang Google Ads API Team

ref:_00D1U1174p._5004Q2YsSJt:ref

[Vijay Bang]

Hi Google Team,

Any updates?

By when can we expect a fix here?

[Google Ads API Forum Advisor]

Hello Vijay,

Thanks for checking in! Based on talking with the folks who are working on this, this appears to be quite challenging to resolve, and we don't have a date for when it will be resolved. There are multiple cases where this is happening. The case where accounts were going dormant and not being reflected in the query is now working. We're still working through resolving your use case.

[Google Ads API Forum Advisor]

Hi Vijay,

Apologies for the delayed response here. I found a cause for this issue, and have a strategy for you to avoid the delay when updating client account details.

First, here's the cause. Say, for example, you have an account tree like the below:

M0 -> M1 -> M2 -> C0

Where each M node is a manager, and the C node is a client. In your requests to update the name of C0, it appears as though you're authenticating as M0 by using that MCCID as the login_customer_id. Subsequently, when generating the customer report, you're using M1. The way the backend is set up this is actually expected. The date propagation is immediate for M0 and C0 since they were part of the mutate request, however there is a delay for the other Ms in the tree.

If you want to resolve the delay, you would need to us M0 to generate the customer report. There is an effort to resolve the consistency issue for all nodes in the tree, but it's not clear when it will be released to the API.

Thanks,

Ben Karl Google Ads API Team

ref:_00D1U1174p._5004Q2YsSJt:ref