unexpected behaviour with MCC Shared Negative Sets

[Christian H.]

Hi,

when I request Shared Negative Sets from an account, I also get the account's MCC sets. However, the resource name of these sets doesn't indicate that they are MCC shared sets.

e.g. requestId o9xduABzBOz-FCMeBYDU6A, in account AAAAA

SELECT shared_set.resource_name, shared_set.name
  FROM shared_set
 WHERE shared_set.type = NEGATIVE_KEYWORDS
   AND shared_set.status = ENABLED

returns the id of the account from which the request was made in the resource name

shared_set {
   resource_name: "customers/AAAAA/sharedSets/MCC_SET_ID"
   name: "MCC Shared Negative Keywords Set"
}

although the returned set doesn't belong to account AAAAA.

The problem occurs when I try to modify elements of this set,
e.g. requestID b0g-htio8CeorF4uJIEvpQ

operations {
  remove: "customers/AAAAA/sharedCriteria/MCC_SET_ID~KEYWORD_ID"
}

fails with "MutateError.RESOURCE_NOT_FOUND - Resource was not found., at operations[0].remove"

The software doesn't know that the set doesn't belong to the account, so it always gets an error when it tries to change its content.

Could you please return the account ID of the account that owns the shared set in the resource name?

[Google Ads API Forum Advisor]

Hi,

Thank you for reaching out to the Google Ads API support team.

From the provided logs, I understand that you are getting a "RESOURCE_NOT_FOUND" error while trying to remove the shared set. which means the request referred to a resource that could not be found or malformed. 

I could see that you have provided partial logs which are not sufficient to investigate the issue further, provide us with the complete API logs (request and response with request-id and request header) generated at your end so that we can better assist you.

If you are using a client library and haven't enabled the logging yet, I would request you to enable logging for the specific client library that you are using. You can refer to the guides Java, .Net, PHP, Python, Ruby or Perl to enable logging at your end. For REST interface requests, you can enable logging via the curl command by using the -i flag.

You can send the details via Reply privately to the author option, or direct private reply to this email.
 

This message is in relation to case "ref:!00D1U01174p.!5004Q02tJDhQ:ref" (ADR-00238484)

Thanks,
 

Google Ads API Team

[Oliver]

We're having a similar issue.  Any update on how to fix this please?

Christian, did you manage to find a solution?

Thanks

Oliver

[Google Ads API Forum Advisor]

Hi Oliver,

This feature is still not available in the API. However, I have updated the feature request to reflect the fact that additional developers are asking for this. Thank you for letting us know this is an important feature to you as this helps with prioritization.

 

This message is in relation to case "ref:!00D1U01174p.!5004Q02tJDhQ:ref" (ADR-00238484)

Thanks,
 

Devin Chasanoff Google Ads API Team