Do you need to know exactly when your campaigns are starting to run out of budget?
Not after they’ve overspent when it’s already too late, but when you’re getting alarmingly close?
This budget depletion warning script might just do the trick for you.
As you probably know, Google can spend twice your daily budget to help reach your goals. That’s all well and good, but sometimes you need to be a bit more restrictive with your spend and avoid overspending at all costs. I’ve already shared a script that can pause campaigns when spend goes too far over budget, but this one is a preventative measure if your budget is more limited.
[Note: As of September 2019, this script will no longer function due to an update to the Google Ads platform.]
For example, if your budget is close to getting exhausted, you might also want to figure out until when in the day it lasts, without manually looking at the reports every day (especially if you’ve got shared budgets across campaign). This will help you monitor overspending trends on a day to day basis.
How to use it?
In a nutshell, the script warns you when your spend has reached a certain percentage of your daily budget, as chosen by you.
First, you’ll need to copy the script below into your account (in Tools, under Bulk Actions in the Google Ads interface) and set an hourly run schedule.
Choose the campaigns that the script should look at by editing the CAMPAIGN_NAME_CONTAINS and CAMPAIGN_NAME_EXCLUDES settings, to include or exclude specific campaigns in your account (e.g. only checking brand campaigns). You can also leave those variables blank to include all campaigns.
Then, set a percentage cap in WARNING_PERCENTAGE_CAP to determine the percentage of the budget that needs to have been spent for the tool to warn you.
The tool will then email all the addresses provided in the EMAILS variable with a table of the campaigns that have exceeded the budget cap.
It looks a little something like this:
All that’s left to do is to make sure you actually check your inbox once in a while!
Opinions expressed in this article are those of the guest author and not necessarily Search Engine Land. Staff authors are listed here.