Designing custom AdWords tools.

The AdWords interface is awful.

I’m not talking about the new UI vs the old UI. Both are terrible, and when version 3 is forced on us in a few years it will be no less unpleasant to use.

The AdWords interface has to do too much for it ever to be great software.

It can’t favour the way you work over the way someone else works. It can't prioritise the data you want over the data other advertisers use. It can't optimise for campaigns on the display network at the expense of campaigns on the search network.

It has to be all things to everyone. It has to be multi-purpose. It's a Swiss army knife.

You can use a Swiss army knife to fell a tree, rescue a baby deer from a snare, change a plug or tighten the screws on your glasses. It’s not a great tool for any of these jobs, but it’s usable if you don't have anything else.

AdWords is the same. It can do everything but it's not comfortable to use. Finding data takes too many clicks. Regular workflows are spread out across many screens. The display is cluttered and noisy.

Here's how you can design a great custom Google Ads tool.

Build less.

You know the 80:20 rule? It’s valid for AdWords too. 80% (or more) of the time you spend in AdWords is spent looking at the same few columns and doing the same handful of tasks.

Start by polishing out the friction from the every-day tasks. Every click you shave off, every calculation you automate, every complex workflow you trigger with one button will repay you in time saved, mistakes avoided and general happiness.

There is a temptation to build everything AdWords can do, to make your tool complete. Don't do it. You'll end up with a poorly implemented multi-purpose tool - a knock off Swiss army knife.

Accept that you'll have to make the occasional visit to AdWords. When you get back you'll appreciate the simplicity of your tool even more.

Put the data you need to make a decision on one screen.

Let me explain what I mean with an example.

My regular workflow includes a deep look at keywords with a higher than average CPA. I need the following data to guide my decisions.

This data is scattered all over AdWords. You can consolidate it into a single screen in your custom tool. You still have to apply experience and good judgement to decide if the higher CPA is a problem, why it's higher and what to do about it. But, you don't have to spend a hundred clicks gathering the data before you start work.

Show less data.

The more data you show on a screen, the harder it is to interpret. Your brain has to filter the signal from the noise. Show only the data you need to guide the decision at hand.

You may need extra data when the main metrics don't give a definitive answer. You can handle this by having a button to show secondary data. Better - (but more expensive to build - is to have your tool know when you need the extra data and show it automagically.

Pre-filter everything you can.

Sticking with the same workflow example - examining keywords with higher than average CPA.

Your tool could have a screen that shows keywords ranked by CPA. It's already faster than the equivalent workflow in AdWords:

  1. Create and save custom set of columns.
  2. Choose the column set.
  3. Select the appropriate date range.
  4. Find the average CPA for the campaign.
  5. Set a filter for CPA > the average CPA.

But it could be better. Your tool could show only keywords that had a higher than average CPA. You're removing some noise from the screen. That gives prominence to the keywords that need action.

By definition are always going to be some keywords with a high than average CPA. They don’t all need attention and you’re still asking the to decide which keywords are OK and which are a problem.

You can take this decision away from the user by setting a threshold at which high CPA becomes a problem. Say any keyword where the CPA is higher than 15% above average deserves a look.

Now you’ve only got keywords the user needs to pay attention to on the list. No noise, all signal. Every decision you remove makes your software better.

Set sensible defaults.

If you normally make decisions on the last 30 days data, set your tool to default the last 30 days data. Good software requires as few non-core decisions as possible. You can always offer a discrete date range selector if the default isn't right often enough.

You’d do the same for other settings. If you normally opt out of search partners on new campaigns, default to that. It might even be worth not exposing the option at all. On the odd occasion that you need to opt into search partners you can do that via the regular interface.

This make sense to you? Read this next: How to use the AdWords API to automate AdWords.

Want higher conversion rates?

I’ve seen conversion rates double, triple and even 10X after a few quick and easy changes to the enquiry form.

Subscribe now and I'll send you a free copy of my in-depth ebook High-Converting Enquiry Forms.

You're already paying for clicks. Now turn them into conversions.

Privacy policy. Unsubscribe at any time.


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 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.