Renaming, merging and deleting Google Ads campaigns from chat

Names like “Campaign 3 copy (new)” make an account unreadable within a month. A good convention carries channel, goal, region and campaign type in the name, for example “TR | Search | Brand | Conversion”. Filtering reports, moving budgets and talking to an assistant all get far easier under that structure.

In Tecrube renaming is one request: “rename all search campaigns to this pattern”. The preview shows old and new names side by side; no name changes until you approve. Renaming does not affect performance; you change the label and the history stays intact.

In Google Ads an ad group cannot be moved from one campaign to another. What we call a “merge” is really this: new ad groups with the same structure are created in the target campaign, keywords and ads are copied, and the source campaign is paused. Quality score history does not travel with the ad group, so merge only structures that genuinely duplicate each other.

Tecrube collects that flow in a single preview in chat: groups to create, keywords to copy, source to pause. You review the table and approve. The source campaign is paused, not removed; a week later, once the new structure has settled, you make the removal decision separately.

After a merge the target campaign's budget usually needs to go up. Tecrube rejects any single-step budget increase above fifty percent. A campaign on $100 a day cannot jump to $400 in one move; you raise it in two or three steps and see each one.

The rule can feel inconvenient, but its purpose is clear: to stop a mistyped figure or a misread request from draining the account overnight. Raising budgets in planned steps also suits the algorithm's learning phase better.

Before deciding to merge, ask four questions. Are the targeting settings of source and target (region, language, device, schedule) identical? If not, the merge degrades one side's performance. Are the bidding strategies compatible? Moving a target-CPA campaign into a manual-bid one resets learning.

Are the negative lists the same on both sides? If the source's campaign-level negatives are missing on the target, waste returns after the merge. Finally, conversion goals: if campaign-level goals differ, the merge muddles the reports.

In Tecrube, “compare these two campaigns' settings side by side” answers all four in one table. No differences means the merge is safe; differences mean the target's settings need fixing first, with a preview.

A removed Google Ads campaign cannot be restored. Its historical data remains in reports, but the campaign itself, its settings and ads can never be edited again. That is why the removal preview in Tecrube carries an explicit “this cannot be undone” warning and asks for a separate confirmation.

The practical rule: pause first, wait thirty days, then remove. A paused campaign does not clutter the account; a removed campaign is simply gone when you need it.

The most common mistake is not noticing that campaigns labelled “low performers” actually serve support roles such as brand search or remarketing. Before removing anything, ask in chat for “this campaign's conversion contribution and assisted conversions over the last 90 days”.

Every approved change is written to Tecrube's activity log. A week later the answer to “who changed what last week?” is waiting in the panel; within a team or in a client conversation, that record shortens the argument.

Do the clean-up in sequence rather than all at once: rename first (no risk), pause second (reversible), remove last (permanent). Leaving a few days between steps stops you moving on before you have seen the effect of a mistake. You can try the whole flow on your own account with the 75 free credits, no card required.