Seeking help while developing a script for automatically filter "Conflicting Negative Keywords"

[Lutfor Rahman Raju]

Hi,
I'm actually working on a report where I can get the Conflicting Negative Keywords of my google ads and I'm accessing that using my main MCC account.

Is there any way to directly get the Conflicting Negative Keywords using GOOGLE ADS API?

Thank You.

Regards___
Lutfor Raju

[Google Ads API Forum Advisor]

Hi Lutfor,

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

To fetch the negative keywords at the campaign level, you may use the below query with campaign_criterion report:

SELECT campaign_criterion.negative, campaign_criterion.type, 
campaign_criterion.keyword.text, campaign_criterion.keyword.match_type, campaign.id 
FROM campaign_criterion 
WHERE campaign_criterion.type='KEYWORD'"
}

Also, you can get the negative keywords at the ad group level using the ad_group_criterion report: 

SELECT ad_group_criterion.negative, ad_group_criterion.keyword.match_type, 
ad_group_criterion.type, ad_group_criterion.keyword.text, ad_group.id 
FROM ad_group_criterion 
WHERE ad_group_criterion.type = 'KEYWORD'

On the other hand, customer_negative_criterion is indeed a negative criterion for exclusions at the customer level.

If you are not looking for the above reports, please share the uncropped screenshot of the Google Ads UI by highlighting the specific fields of the report that you are trying to fetch via the Google Ads API?

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.!5004Q02vGrVi:ref" (ADR-00280578)

Thanks,
 

Google Ads API Team

Feedback
How was our support today?

               

[Lutfor Rahman Raju]

Hi,

I hope this message finds you well.

We are managing over 200 ad accounts under our MCC account and are looking to automate the process of fetching all "Conflicting Negative Keywords" for these accounts. Our goal is to generate a consolidated report that includes this data for all the ad accounts within the MCC.

Could you kindly provide guidance on how we can achieve this using the Google Ads API? Specifically, we would appreciate:

1. The necessary API queries to identify and retrieve conflicting negative keywords.
2. Best practices for automating this process across multiple ad accounts under the MCC.
3. Any additional considerations or resources to facilitate this implementation.

Thank you in advance for your support and expertise.

Best regards,
Lutfor Raju

[Google Ads API Forum Advisor]

Hi Lutfor,

Please find the below responses for your queries:

1) In order to assist you further, please share the earlier requested uncropped screenshot of the Google Ads UI by highlighting the negative keywords that you want to retrieve via the Google Ads API?

2) You can utilize the MCC account to manage access to all the child accounts and please use the CustomerService to retrieve a list of all child accounts under your MCC.

3) Kindly refer to the document API Limits and Quotas to get more information on the limits on API operations, such as the number of operations that can be sent to a single mutate request.

I hope this helps! Feel free to get back to us in case of any further queries.

[Lutfor Rahman Raju]

Hi,
I hope this message finds you well.

For your convenience, I've attached a couple of screen-shots.

Recap::::
For a quick update, basically I want to know all the Conflicting Negative Keywords for all of my child accounts at once using my MCC. I want help from you guys on that, how I can get the Conflicting Negative Keywords for each of my child accounts.

Thanks_____
Best regards,
Lutfor Raju

[Google Ads API Forum Advisor]

Hi,

Kindly note that currently there is no resource or field in the Google Ads API to fetch conflicting negative keywords. As this feature is available in the UI, I will raise a feature request to make conflicting negative keywords accessible via the Google Ads API. However, I cannot provide a scheduled timeline for its availability. I would recommend monitoring our blog post and release notes for updates regarding future changes.