Shared negative keyword list usage isn't reflected between the UI and API

[Demi Yo]

All of our campaigns are supposed to use a shared list of "global" negative keywords. We have a utility script that runs through all of our campaigns to make sure we added the list to them manually. This has worked flawlessly for a long time, until recently something odd popped out. The ads UI (on Google) tells us a single campaign is missing the shared list, but the API says the campaign is using it. So which is it? My question in a broad sense is: does Google have a cache gap between the UI and the API? We don't mutate campaigns through the API, we have humans do things manually through the UI, so it couldn't be anything on our end. The bug persisted across multiple days.

We use the following GAQL, and we do not cache the result:

SELECT

  campaign.name,

  shared_set.id
FROM

  campaign_shared_set
WHERE
  campaign.status = ENABLED
  AND campaign.advertising_channel_type IN (SEARCH,SHOPPING)

ORDER BY
  campaign.name

This reported that the campaign in question was using the "global" shared negative keyword list, but the UI said the opposite. The API and UI seem to be in conflict with each other, and it caused a bit of confusion.

Any insight would be helpful, thanks.

[Google Ads API Forum Advisor]

Hello Demi,

Thank you for reaching out to us.

As for your concern with regard to the conflict between the UI and the API. This is odd since the results coming from the API should be the same with what's in the UI. For us to better check on the issue, could you share with us the following details below?

• Screenshots (from the UI) showing the discrepancies
• Complete logs (request and response with request-id) generated from the API

Please send the requested details via the Reply privately to author option. If this option is not available, you may send the details directly to our googleadsa...@google.com alias instead.

Regards,

Mark Kevin Albios Google Ads API Team

ref:_00D1U1174p._5004Q2KbjkB:ref

[Demi Yo]

The issue resolved itself within about a week, I don't have any screencaps or logs since I can't duplicate the issue now. Maybe it was a fluke, who knows. If it pops up again I'll continue this thread. Thanks for the insight.

[Google Ads API Forum Advisor]

Hi Demi,

Glad to hear that the issue was resolved.

Just to add, and also to help with troubleshooting, you can enable logging of your API requests by navigating to the Client libraries > Your client library (ex. Java) > Logging documentation, which you can access from this link.

Best regards,

Peter Laurence Napa Oliquino Google Ads API Team

ref:_00D1U1174p._5004Q2KbjkB:ref