Call extensions bug

[Roman Bondarenko]

Hello team! 

Recently a bug was found. 

When you add a new Call Extension and have Conversion Action field active - you choose "Use account settings" as option. Then you click "Save" button. Everything goes well and extension is saved. (pic. 1)

Account level "conversionType" key is None (pic. 2)

But after that you want to make some changes for this field and pick another option - custom conversion which is called "Phone" and it has id - 372280497. (pic. 3)

And you click "Save" button again - everything goes well. It is saved. 

But after that you decided to change back again to Account settings. You pick this option from available and click "Save" again... it seems good. On Platform it is saved (pic. 4)

But when you try to fetch data from API it sends wrong data - (pic. 5) Which is last choice option ... 

But account level should use "conversionTypeId" = 179. (or None as it was when we just created extension... I am not sure what defaults you use guys... )

But when you decide to change "Conversion action" field to option "Calls from Ads" instead of "Use Account settings" (pic. 6) it sends data back as expected (pic. 7)

So that means - option "Use Account level" only change how things are displayed on platform UI and that's all. And it is broken when you decide to change option for "Conversion action" field it at least once.

Or maybe "Use Account level" should not save field "conversionType" as None but provide with account default value which is 179 for this account.

Hope I did a good job explaining the issue. Thank you!

[Google Ads API Forum Advisor Prod]

Hi Roman,

Thanks for your investigation. I'll need to take a closer look into this. Can you provide me some of the logs from these API calls? Please do so using reply privately to author.

Regards,
Anthony
Google Ads API Team

ref:_00D1U1174p._5004Q23Ivfv:ref

[Roman Bondarenko]

Yes, I could provide logs, of course :) But firstly would like to point at some fact... 

All changes to extensions were made through platform UI but not API... with API I only fetched updated data from you guys) Please, note that as well. 

There are other extensions, ad groups, ads in log file (because it's sync and all data are fetching) but I believe you will find there call extensions ) 

Hope it helps! 

Thanks!

[Google Ads API Forum Advisor Prod]

Hi Roman,

Please try to use the CustomerExtensionsSettingService and see if your extensions return properly with this service.

[Pete Lavetsky (AdWords API Guru)]

Was there any resolution to this? We're running into the same thing.

On an existing CallFeedItem, we are changing the CallConversionReportingState to USE_ACCOUNT_LEVEL_CALL_CONVERSION_ACTION via setCallConversionReportingState ( Google Ads API Client Library for Java v 15.0.0 ) 

This mutate succeeds and the field mask for the reporting state is part of the mutate

On a subsequent get via the API, the reporting state has not changed ( it's still USE_RESOURCE_LEVEL_CALL_CONVERSION_ACTION )

We've verified that the Call Extension value did not change in the UI ( or the API )

Is there another level that needs to be pulled if the CallConversionReportingState is changed via the API?

MethodName: google.ads.googleads.v8.services.ExtensionFeedItemService/MutateExtensionFeedItems

Endpoint: googleads.googleapis.com:443

Headers: {developer-token=REDACTED, login-customer-id=ABC, x-goog-api-client=gl-java/1.8.0_161 gapic/ gax/2.5.0 grpc/1.40.1}

Body: customer_id: "ABC"

operations {

  update {

    resource_name: "customers/ABC/extensionFeedItems/XYZ"

    call_feed_item {

      call_conversion_reporting_state: USE_ACCOUNT_LEVEL_CALL_CONVERSION_ACTION

      phone_number: "(ABC)766-7318"

      country_code: "US"

      call_tracking_enabled: true

      call_conversion_tracking_disabled: false

    }

    extension_type: CALL

  }

  update_mask {

    paths: "resource_name"

    paths: "extension_type"

    paths: "call_feed_item.phone_number"

    paths: "call_feed_item.country_code"

    paths: "call_feed_item.call_tracking_enabled"

    paths: "call_feed_item.call_conversion_tracking_disabled"

    paths: "call_feed_item.call_conversion_reporting_state"

  }

}

partial_failure: true

Response

--------

Headers: Metadata(content-disposition=attachment,content-type=application/grpc,request-id=K1gd1cwA7wE53NnLo9D2fw,date=Tue, 28 Sep 2021 18:21:52 GMT,alt-svc=h3=":443"; ma=2592000,h3-29=":443"; ma=2592000,h3-T051=":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")

Body: results {

  resource_name: "customers/ABC/extensionFeedItems/XYZ"

}

Thanks

Pete

[Google Ads API Forum Advisor]

Hi Pete,

Thank you for posting your reply on this forum post.

To investigate the issue and to address it, could you provide the complete request and response logs with request ID generated on your end without updated fields?

Please provide also the screenshot of the UI where the API request did not reflect.

You can provide the requested details 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 Blanca Tacata Google Ads API Team

ref:_00D1U1174p._5004Q23Ivfv:ref