#1 Copy and paste script from the WeDiscover Github profile
Find the script hosted on the Public WeDiscover GitHub here.
#2 Add to scripts section within the account
You can add this script either at an individual account or MCC level.
Navigate to Tools (top right corner of your screen when in Google Ads) > Bulk Actions > Scripts.
Click on the blue “+” icon to create a new script.
Be sure to delete anything that is already in the box for the script insertion in Google Ads first, then copy and paste the full script from GitHub into Google Ads.
You may choose to edit the script name at the top. This will allow you to easily differentiate between the different scripts you enter.
You can add this script using the new Google Ads beta experience (currently available at individual account level only, not MCC), if you wish to.
#3 Specify your criteria
Near the top of the script, you will see an area that says “Edit Me”, running from lines 11-15 and highlighted in the yellow box in the screenshot below.
Here you must enter one of ‘true’ or ‘false’, to specify where and how you want your script to run. Selecting each will work as follows:
True: check for ad groups without RSAs in paused campaigns
False: only check for ad groups without RSAs in enabled campaigns
True: check for paused ad groups without RSAs
False: only check for ad groups without RSAs in enabled ad groups
True: paused RSAs will be counted as existing coverage, and the script will skip these ad groups
False: ad groups that contain paused RSAs will be counted as lacking RSA coverage, and the sheet will output new copy for them
True: copy will be pulled into the output sheet from paused ETAs (as well as enabled ones)
False: copy will be pulled into the output sheet from only enabled ETAs
#4 Run the script
Save your script, authorise it and then press preview or run (and then select preview, as shown below).
Once the script has finished running, click on to the ‘Logs’ section at the bottom of the screen. Here you will see a top-level breakdown of the findings of your script, including the number of ad groups that have been found without RSAs.
If running the script at MCC level, the logs will show a breakdown of findings by account. Be aware here that as scripts only have 30 mins to run, for exceptionally large MCCs there is a small chance it may time out before completing all of its checks. In these instances, you’ll need to add the script to individual accounts instead.
The final line of your logs will provide you with a link to an output GSheet. Copy and paste this into your browser to open it.
If no ad groups missing RSAs are found, the logs will say this on their final line, and no GSheet link will be provided.