ᴎils rooijmans

Stop revenue loss due to disapproved products in the Google Merchant Center.

My inbox is bursting at the seams with evidence of people suffering >10% drop in Google Shopping performance due to product disapprovals, _without them noticing for weeks or even months_!

If you are running Shopping ads, I bet you, at least every now and then one or more products will get disapproved.
No exceptions.

The same goes for products in your Performance Max campaigns.

This is the nature of the beast; products in your shopping feed get disapproved for all sorts of reasons, at times you least expect it.

• • Your product could be missing a critical attribute value.
  • There can be a mismatch between your product data in the feed and the listing on your site (price, availability, color, …).
  • Or someone, somewhere, added a sales discount to your images.(Google will not allow it)
  • Or Google decided to change their policy for the gazillionth time.
  • Or…

The list goes on and on.

Here’s the thing:
When you fail to identify a top-performing product being disapproved, sales and revenues crash like the TSLA stock after a Musk tweet.

Keeping up with disapproved products is a MUST!
Continue reading “Google Ads Script – Disapproved Products Alerts”

Since June 30 2022, advertisers are no longer able to create or edit Expanded Text Ads (ETAs) in Google Ads.
Responsive Search Ads (RSAs) are the new default.

According to many PPC practitioners, ETAs get fewer impressions than RSAs for the same set of keywords and bids.

So, unless you want to limit your growth opportunity, you need to add RSAs to each and every ad group.

Identifying ad groups that have zero RSAs can be a bit jarring, so I decided to create a script to identify ad groups without any active RSA’s.

The following script creates a Google Sheet reporting ad groups that have less than the required number of Respsonsive Search Ads (RSAs).
If there is at least one ad group that has too little RSA’s the script will send an email with a link to the report.

Continue reading “Google Ads Script – Report Ad Groups that don’t have RSA’s”

Back in 2015, the guys at Brainlabs created a very popular script that allows you to analyze n-grams in your search term data.

An n-gram is a phrase made of n words: a 1-gram is a single word, a 2-gram is a phrase made of two words, and so on. For example, “this four word phrase” contains three 2-grams (“this four,” “four word,” “word phrase”) and two 3-grams (“this four-word” and “four word phrase”).

The script adds up the clicks, impressions, cost, converted clicks and conversion value of each query containing the n-grams — and calculates the click-through rate, cost per click, conversion rate, CPA and value/cost — so you can see their impact.

If the performance is good, you might want to make new ad groups around the n-gram; if the performance is bad, you might want to exclude the n-gram as a negative phrase-match keyword.

If you’re using the Google Ads n-gram script (aka ‘Search Query Mining Tool’) you may have noticed it’s not working in the new Google Ads scripts experience.

It throws an error like:

InputError: shared_criterion.keyword.text || shared_criterion.placement.url || etc.

The issue is caused by an AWQL query that is not compatible with the new script environment.

To fix the issue I’ve updated the script so that it now uses GAQL to retrieve the data.

For instructions on how to use the script, please visit the original post at SearchEngineLand .

Here’s the updated code:

Continue reading “Brainlab’s Search Query Mining for N-gram Analysis (Updated) for new script environment”