Negative keyword conflicts scripts (V2.0 & V2.1) are not working as intended.

[Leon Latypov]

Hi Google script team,

I hope all is well. The negative keyword conflicts scripts (V2.0 & V2.1) are not working as intended. This has been an issue for over 6 months now and has not been resolved and is causing a lot of confusion for our search teams.

The NKC script seems to be calling out search terms rather than keywords that are being blocked. Meaning that the script that supposed to be calling out conflicts in case we have keywords that are being blocked from serving due to a negative keyword, is now instead calling out missed opportunities based on search terms from users.

That is clearly not what the script was originally intended to do and a lot less valuable information than automatically calling out actual keyword conflicts. At this point the script seems to just be telling us that negative keywords are successfully blocking ads from showing to user who are searching specific search terms that match our negative keywords. This is not how the script used to function and not how it was intended to work. 

None of the "keywords" in the "Blocked keywords" column of the script results spreadsheet are actual Keywords set on any of our accounts. They are search terms. So the script results are not calling out "CONFLICTS" rather just generating daily false negative reports with false information. 



Please let me know if you want the account info so that you can look into some specific example of scripts we're currently using. 

I understand that development / engineering resources might currently be working on other projects like the NEW SA360, or GA4, but a lot of your Google ads users are being left high and dry without working Negative keyword conflicts scripts and MCC level link checker scripts that they have relied on for accurate daily callouts for the past 7+ years. 



Thank you.

[Nils Rooijmans]

do V2.0 and V2.1 produce the same output for you?

[Leon Latypov]

Hi Nils,

Thanks for your response. I'm actually going to have to backpedal what I said in my original post. We have hundreds of NKC 2.0 scripts that are showing the issues I described above and and only 2 accounts that are using the new 2.1 script. 1 of those 2 accounts is having an issue where it's calling out search terms that are not keyword conflicts, and the other new test account that I created for this test seems to not be having this issue.

I'll need to do more testing and get back to you. These might be 2 separate issues that I'm not able to tell apart yet. 

[Google Ads Scripts Forum Advisor]

Hi,

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

After reviewing your concern, I understand that the negative keyword conflicts scripts (V2.0 & V2.1) are not working as intended. Kindly note that, regardless of match type, negative keywords are intended to prevent ads from showing on irrelevant search queries and what is shown in the 'Blocked' column will be uploaded as negative keywords. 

Also, please check this section on How it works as it is stated there that a broad match negative keyword like ‘silk scarves’ would block any normal keyword (regardless of match type) that contains the words 'silk' and 'scarves' in any order.

If the issue still persists, kindly provide us with the following details to further investigate your concern: 

• Google Ads account ID / CID
• Name of the affected script
• If the script uses a spreadsheet, please provide a shareable link to the spreadsheet. You can follow this guide to share a file publicly.

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:_00D1U1174p._5004Q2ozNgw:ref"

Thanks,
 

Google Ads Scripts Team

 

[Leon Latypov]

Hi Scripts team. 

Just following up here to let you know that the new 2.1 NKC script does fix the issue that I described in my first post. 

Thank you,