Why do you need Direct Commander if there is a web interface?

For the sake of mass operations. Editing one ad is more convenient in the interface, editing three hundred is only in Commander: there it is one operation instead of three hundred open-edit-save cycles. The threshold after which it pays off occurs at about tens of elements.

What operations are performed most often in Commander?

Bulk replacement of text in ads, replacement of links and UTM tags, copying campaigns between accounts, adding negative keywords to several campaigns at once, editing sample bids and transferring groups between campaigns.

Is it possible to cancel bulk edits in Commander?

There is no full history of cancellation there. The only reliable insurance is to upload the current state to a file before starting work. Then the damaged campaign can be restored from the copy.

Why don't changes from Commander appear in the interface?

Because Commander works with a local copy of the data until you push changes to the server. Until the submission is complete, the edits only exist on your computer.

What would happen if campaigns were controlled simultaneously in the interface and in Commander?

Sending from Commander will overwrite the server data with your local version, and edits made in the interface after the last synchronization will be lost. Therefore, before work, they always receive up-to-date data from the server.

Is Commander suitable for small accounts?

For one campaign with a dozen ads, it is excessive: the time spent on development will not pay off. It starts to pay off where there are dozens or hundreds of elements of the same type, or when you need to transfer the structure between accounts.

All articles

PerformanceSeptember 5, 20268 min

Direct Commander: massive operations, which is why it is needed

Commander is needed where the interface can no longer cope: editing hundreds of ads, moving campaigns, mass replacement of links and tags. I’ll look at five operations for which it’s worth mastering, and the rules that will protect you from spoiling your campaigns.

Commander looks like a heavy program for agencies and often remains so - until the first moment when you need to change the same link in two hundred ads. After this, the question “why is it needed” closes itself.

The web interface is convenient for one ad. Commander - for two hundred. This makes all the difference, and the threshold comes faster than it seems.

1. Five operations worth mastering

Operation	In the interface	In Commander
Replacing text in ads	One at a time	Mass replacement by sample
Changing links and UTM	One at a time	One operation for everything
Copying campaigns	Limited	Between campaigns and accounts
Negative keywords in several campaigns	By campaign	Immediately for sampling
Editing bets by condition	By group	For any sample

The second line is the most common reason why Commander is still downloaded. Changing the analytics system or adding a new tag to the markup turns editing links into many hours of work if done manually.

What exactly should be in these labels so that they do not have to be changed again in a month - in the analysis UTM schemas.

2. A rule that should be created before the first edit

Upload the current state to a file. Always, before any mass operation, without exception.

The reason is simple: mass edits are applied instantly and to everything selected, but there is no full history of undoing many steps back in Commander. If the operation did not work as you expected, you will have to restore from a copy - or manually.

Unloading takes half a minute. Restoring three hundred damaged advertisements in a day.

3. Two copies of data to remember

The commander works with a local copy. Until you click submit, your edits only exist on your computer, but the same on the campaign server. This is the first thing people stumble over: “I changed it, but nothing has changed in the interface.”

The reverse situation is more dangerous. If someone edited campaigns through the web interface after you received the data, your local copy is out of date. Submitting will overwrite the server data with your version, and other people's edits will disappear.

Hence the order: get current data → edit → send. The first step is skipped most often, and it is the one that leads to the most unpleasant losses.

4. Check the selection, not the result

The bulk operation applies to the entire selection. The selection easily captures more than is visible on the screen: you sort the list, click, drag, and the selection includes what went beyond the window border.

A habit that saves nerves: before performing an operation, look at the number of selected elements. If you expected twenty, but one hundred and forty were allocated, it is too early to perform the operation.

5. Run on one campaign

Before you apply an edit to your entire account, you should make it on one small campaign and send it. This takes a minute and shows that the operation does exactly what you intended.

This is especially true for replacing text: substrings are found where they were not expected, and “replacing a word in headings” sometimes touches the middle of another word.

6. What the Commander is not

Analytics tool. It shows the structure and allows you to change it, but making decisions on it is inconvenient and unnecessary: reports live in the web interface and in Metrica.

A typical mistake is to try to evaluate effectiveness in the same window where you are editing. The division is simple: look in the interface, change in Commander.

7. When it's not needed

One campaign, a dozen ads, edits once a month. Here, the time spent on development will not pay off, and the risk of spoiling a mass operation is greater than the gain.

Guideline: if there are dozens of elements of the same type, or if the structure is to be transferred between accounts, it’s worth it. If not, the interface is enough.

8. Summary

The commander solves the problem of scale, not the problem of quality. It won't make the campaign better - it will make possible edits that would otherwise take a day.

Three rules that eliminate almost all risks: unloading before work, obtaining current data before editing, checking the number of selected elements before operation.