Google Ads desktop: the campaign screen in a window of its own

A search for Google Ads desktop is usually driven by one of three unrelated frustrations, and the results page mixes all three together. One person wants a real application instead of a browser tab that gets lost between a shared inbox and a spreadsheet. Another wants to make two hundred keyword edits without waiting for a page to reload each time. A third has four client accounts under different Google logins and is tired of signing out to reach the next one. Google publishes an answer to exactly one of those problems, a partial answer to the second, and nothing at all for the third. Sorting out which is which takes about five minutes and saves a lot of wasted searching.

Three different things called Google Ads desktop

The first is the Google Ads web interface at ads.google.com. It is the full product, it runs in a browser, and there is no downloadable Mac version of it. The only mobile client Google publishes is the Google Ads mobile app for phones and tablets, and even the marketing page for it frames it as a way to track campaigns while away from a computer rather than as a replacement for the web interface.

The second is Google Ads Editor, which genuinely is a desktop application, free, and built for bulk work. It is not a shell around the web interface. It downloads accounts to the Mac, lets changes happen offline, then uploads them.

The third is not a Google product at all. It is the reader's own wish for the web interface to behave like an application: an icon in the Dock, a place in the Command+Tab switcher, one window that does not share a keyboard shortcut with eleven other tabs. That wish is answered by macOS and the browser rather than by Google, and the tools for it are free or close to it.

Confusing the first two is the expensive mistake. Installing Editor while expecting the reporting dashboards leads to disappointment, and hunting for a native version of the web interface leads nowhere at all.

Google Ads Editor, in Google's own description

Editor is worth understanding before deciding whether a window will help, because for some of the work described below the window question disappears entirely. Google's own summary of the application is direct.

Google Ads Editor is a free, downloadable application for managing your Google Ads campaigns. The basic process is simple: download one or more accounts, make changes offline, then upload the changes to Google Ads. Source: support.google.com

The capability list on the same page is the part that decides the matter for anyone doing volume work: bulk editing tools for multiple changes at once, export and import of files to share proposals, statistics for all campaigns or a subset, managing and viewing several accounts at the same time, search and replace across ad groups and campaigns, copying or moving items between ad groups, multi step undo and redo, making changes in draft before uploading, and continuing to work while offline.

Two items there deserve attention. Multiple accounts open at the same time is the answer to the third frustration above, at least for editing work. Search and replace across campaigns is something the web interface simply does not offer in that form.

The system requirements are short and have a real cutoff.

Google Ads Editor is available for 64-bit Windows 10 or later and MacOS 13 or later. Source: support.google.com

A Mac still on macOS 12 is outside that line, which pushes the decision toward the web interface and toward making that window behave better. Google's help centre also currently carries a notice that the Editor sign in process is changing, so anyone installing it now should read the banner on the help pages rather than relying on a screenshot from a blog post.

What the web interface still owns

Editor does not cover everything, and treating it as a full replacement leads to work being done twice. The recommendations feed, the insights pages, audience reporting, most billing screens, and anything involving a live account health check stay in the browser. Google states plainly that after adopting Editor it is still normal to sign in at ads.google.com and make changes there, and that Editor needs a fresh download of the account afterwards to stay in step.

That last detail is the practical trap. Two people editing the same account, one in Editor and one in the browser, will overwrite each other unless the Editor side downloads recent changes first. The habit that prevents it is boring and effective: download the account at the start of a session, post changes at the end of it, and never leave an Editor session open overnight expecting it to be current in the morning.

So the realistic shape of a working day is both: Editor for volume edits, the web interface for everything else, open all day. Which brings the window question back.

The routes for the web interface, side by side

Route	Setup	Own Dock icon	Separate login store	Works with a manager account
Browser tab	None	No	Shares the browser session	Yes, through account switching
Safari, Add to Dock	Two clicks in Safari	Yes	Own cookie store	Yes
Chrome, Install page as app	Two clicks in Chrome	Yes	Shares the Chrome profile it came from	Yes
Chrome profile per client	New profile, sign in again	Only if an app is installed in it	Yes, per profile	Yes
Site to app tool	Pick a preset or paste the URL	Yes	Own profile per app	Yes

Apple documents the Safari route in the Safari User Guide, and the result is a genuine application rather than a bookmark.

You can open and use a website as if it's an app. Go to the Safari app on your Mac. Go to a website. Click in the toolbar, then choose Add to Dock. Click Add. An icon for the web app is added to the Dock and Spotlight Applications. Source: support.apple.com

Apple's General settings page for web apps adds the details that make this usable for a dashboard left open all day: the application name, the URL it opens, the icon, and whether navigation controls appear in the toolbar are all editable per app. Turning off the back button is a small thing until a stray click on it throws away a half filled campaign form.

Chrome's equivalent sits under the three dot menu, in Cast, save, and share, then Install page as app. Google describes installed web apps as sites reached from the launcher with extras such as notifications and icon badges. The constraint is inheritance: the app opens whichever Google account the originating Chrome profile is signed into, and Chrome has to be running.

Extensions decide the route for a lot of ad managers

One detail separates the free routes more sharply than price does. A working day in Google Ads often involves browser extensions: a tag inspector, a screenshot annotator, a password manager, a translation tool for foreign language landing pages. Where those extensions live determines which window is usable.

Apple's Safari User Guide lists an Extensions settings panel for web apps alongside General and Privacy, so a Safari web app is not extension free. What it supports are Safari extensions, which is a different and smaller catalogue than the Chrome Web Store. An inspector that exists only as a Chrome extension will not appear there.

A Chrome installed web app inherits the extensions of the Chrome profile it was created in, which solves the catalogue question and reintroduces the profile question: the app is tied to that profile and to whichever Google account it is signed into.

A wrapper built on a Chromium engine sits in the middle, loading Chrome Web Store extensions while keeping a profile that belongs to the app rather than to the browser. For anyone whose tag debugging habit depends on a specific Chrome extension, that combination is the deciding factor, and the Guide walks through setting it up.

The account switching problem, stated honestly

This is where most of the real time goes for anyone managing more than one advertiser, and it deserves to be described precisely rather than solved with a slogan.

Google's own answer is the manager account, sometimes still called MCC. One login, many accounts underneath it, switching inside the interface. When every account a person touches sits under one manager, this works well and nothing else is needed.

The problem appears when the accounts are not all under one manager. A freelancer invited directly to a client's account with their own Google login, an in house marketer with a personal Google account and a work one, an agency that inherited accounts from three predecessors: none of those collapse into a single manager account, and each one means a different Google session. In a single browser profile, only one Google session can be the active one for a given service at a time, so the day fills up with signing out, switching, and landing on the wrong account.

There are three honest fixes. Consolidate under a manager account where the client relationship allows it, which is the cleanest and often the slowest politically. Use one Chrome profile per identity, which works and costs a browser window per client. Or give each identity its own application with its own cookie store, which is what a Safari web app does for one and what a tool that turns a website into a standalone Mac app does for a whole set. Each app carries its own profile, so four client accounts become four icons that open directly to the right account with no switching at all. The Features page describes how that isolation is arranged.

What a window actually fixes, and what it does not

Being specific here prevents disappointment.

A dedicated window fixes the retrieval problem. Command+Tab reaches the campaign screen instead of a hunt through tab strips, and Spotlight finds it by name. It fixes accidental closure, because Command+W in a web app closes a window that reopens to the same place rather than discarding a tab among thirty. With navigation controls hidden, it removes the back button as a hazard during long forms. With its own cookie store, it removes account switching.

It does not make bulk edits faster. Two hundred keyword changes are slow in the web interface because of the round trip to Google's servers, not because of the frame around the page. That is Editor's job.

It does not give offline access. Google's offline story for Google Ads is Editor and nothing else. A web app with no connection shows an error page in a nicer frame.

It does not change permissions. Access to an account is granted to a Google login, so a new window does not create access that the login does not already have.

Reading that list in order is usually enough to decide. Retrieval and account switching are window problems. Volume and offline are Editor problems. A great many people need both, and the two do not conflict.

What to change first

If the daily pain is bulk edits, install Google Ads Editor from Google and adopt the habit of downloading the account at the start of each session. If the daily pain is finding the campaign screen, or signing in and out between advertisers, give the web interface its own window: Safari's Add to Dock handles one login for free, and for a set of client accounts that each need their own session, set them up as separate apps with Kagemusha.