Death by alerts.

Will your custom AdWords tool monitor AdWords performance?

You could use the AdWords API to watch out for landing page errors, ad disapprovals, low impressions, ad spend etc. You can save loads of time by automating the daily checks a human would do.

But, it's surprisingly difficult to work out when your monitoring system should warn your users.

  • If your app sends too many false-positive alerts they will eventually be dismissed unread.

  • If the app misses out on a real problem the user will stop trusting it.


Some notifications are easy. You definitely want to tell a user when there is a disapproved ad, a broken landing page or a failed payment.

It's much more difficult to decide which performance changes are normal and which warrant an alert.

Here are a couple of principles to guide you as you design an AdWords monitoring system.

Set sensible defaults.

Perhaps your app has a budget pacing feature. It will alert the user if their ad spend is going to be over or under a monthly budget. You know ad spend varies by day so you have a threshold for triggering an alert. Say 10% over budget or under budget.

You could ask the user to set the threshold when they first use the app. At this stage they're probably going to get it wrong and get too many or too few alerts. Neither is good.

It’d be better if you calculate a sensible default and set it for the user. They can change it if they need to.

Allow for normal fluctuations.

Clicks, conversions etc fluctuate wildly from day to day. You'll send a lot of false alerts if you consider only one day's performance. It's better to account for normal fluctuations using trends, rolling or weighted averages.

Give context in the alert.

Your user must decide if your alert is a real problem or a blip. Give them the data they need to make the distinction.

If you’re sending alerts by email, you can give it to them in the alert message. If you’re using Slack or SMS, give them a link that’ll take them to a page in your app with the necessary data in a useful format.

Link to where the action is.

Give your user a link directly to the page in your app or in AdWords where they'll take action. For instance, if you're alerting about under spending, give them a link to where they can adjust the daily budget.

Need help with the Google Ads API? Email me (me@pete-bowen.com) for a no-cost, no-obligation chat. I’m always happy to talk Google Ads and code.

AdWords API: Authorization for multiple users.

Here's how you handle authorization for multiple users of your AdWords API tool.

Building custom tools with the Google Ads API.

You run an digital marketing agency. You’re thinking about building a custom Google Ads tool using the API. Here are some of the things that trip people up.

Choosing a domain name for your Google Ads tool.

I bumped into an unexpected problem when I chose the Ad-Minister.app domain.

Death by alerts.

Will your custom AdWords tool monitor AdWords performance? It's surprisingly difficult to work out when your monitoring system should warn your users. Read on for guidelines on alerts and notifications.

Designing custom AdWords tools.

The AdWords interface is awful. You can fix this in your AdWords tool. Here are a handful of principles to guide you as you design your custom AdWords API based tool.

How to use the Google AdWords API to do keyword research.

You’re thinking of building a custom keyword research tool using the AdWords API. Read on to see where to start and what to watch out for.

Where can I find a programmer to help implement the Google AdWords API?

Good news is that you don’t a programmer who is an expert at the AdWords API because the programming constructs that the API uses are well known. For instance, the API uses OAuth for authentication which is very common.