MutateJobService not passing Adgroup ID with DUPLICATE_ADGROUP_NAME error in v201502

[Janak Prajapati]

Hi,

We have migrated to v201502 recently and we noticed that, when we get DUPLICATE_ADGROUP_NAME error through MutateJobService, the error detail not including respective Adgroup ID. In the earlier API versions, we were getting Adgroup ID along with the DUPLICATE_ADGROUP_NAME error.

Here is part of the Soap response with v201502,

<errors xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:type="AdGroupServiceError">
    <fieldPath>operations[38].operand.name</fieldPath>
    <trigger>Adgroup Name Here</trigger>
    <errorString>AdGroupServiceError.DUPLICATE_ADGROUP_NAME</errorString>
    <ApiError.Type>AdGroupServiceError</ApiError.Type>
    <reason>DUPLICATE_ADGROUP_NAME</reason>
</errors>

The Adgroup ID in the error notification was very helpful for our automated script so, wanted to confirm about this change. With this change, we need to made a separate API call to get Adgroup ID of the duplicate adgroup so that, the automated script can continue insertion of Keywords and Ads in the same adgroup.

Please confirm, is this a bug in v201502 or a permanent change?


Thanks

[Josh Radcliff (AdWords API Team)]

Hi,

I'm not aware of any changes around this logic in v201502. Populating the ad group ID in the error has always been done on a best-efforts basis, so there hasn't been a guarantee that this will always occur.

If the ad group ID is critical to your processing, it would be more reliable to use the operations index (38 in your example) to look up the corresponding operation in your mutate job request, and then use the ad group ID contained in that operation.

Thanks,

Josh, AdWords API Team

[Janak Prajapati]

Hi Josh,

Thanks for your reply.

I think you misunderstood my query. I am getting the DUPLICATE_ADGROUP_NAME error when I am trying to create a new Adgroup so, in that case the MutateJob operation itself do not have the Adgroup ID. As we know, once we create the Adgroup, we get respective Adgroup ID from Adwords.

In earlier API versions, we were getting Adgroup ID in the error response if we try to create a adgroup which already exist in the Adwords account. This behavior helped us to know the Adgroup ID of the duplicate Adgroup (without any additional step for finding the Adgroup ID), the automated script stores it and continue the insertion of the Ads and keywords in that Adgroup using the Adgroup ID. If this behavior is not changed in v201502, with the MutateJobService, there might be some technical issue in the API system. Can you please confirm it.

For now, as a workaround, we have applied edits in our automated script which makes separate API call to get Adgroup ID of the respective Adgroup name, if MutateJobService gives the mentioned error. It will help if we can prevent this extra API call.


Thanks,
Janak

[Josh Radcliff (AdWords API Team)]

Hi Janak,

You're right - I didn't realize that you were referring to new ad groups. Thanks for clarifying that point.

I'm following up to determine if there were any recent changes that would prevent us from providing the ID of the existing ad group with the same name. I'll post back once I have more information.

Cheers,

Josh, AdWords API Team

[adwor...@summitmedia.com]

Hi there I also have exactly the same problem

In order to keep our system synchronized we are getting the id from the API response to set on DB when something occurred and we lost that id and therefore tried to insert an existent AdGroup

That field is EXTREMELY useful.

Please advice what can be done or if that field will be re incorporated.

Thanks

Best Regards,

Gustavo  Schlaien

[Josh Radcliff (AdWords API Team)]

Hi Gustavo,

At this time we do not plan to reintroduce this field, so when handling errors you will have to look up the ad group ID from the corresponding operation. In the case of an ADD where the failure is due to an existing ad group with the same name, please use AdGroupService or the ADGROUP_PERFORMANCE_REPORT to look up the ID of the existing ad group by name.

We'll be updating our v201502 migration guide to reflect this change soon.

[adwor...@summitmedia.com]

Hi Josh,

Thanks for promptly response.

If we have a limited amount of requests we can send to the API this can be a problem since the number of those can get drastically increased because of this property gone. Well.... 

Cheers

Best Regards,

Gustavo Schlaien

[Josh Radcliff (AdWords API Team)]

Hi Gustavo,

If you use the reporting approach I mentioned, hopefully you won't run into any limits since the report limits are separate from the SOAP service limits.