Google Ads Campaign Naming Conventions for Target CPA and Target ROAS

If you run both Target CPA and Target ROAS campaigns, your account can quickly become a mess if you can't tell at a glance which bid strategy is running where. This naming convention fixes that.

Why naming matters

Campaign names are the first thing you see in every list, filter, and report. When they're ambiguous, you waste time opening campaigns, you risk editing the wrong one, and you make it harder for anyone else to understand the account. A disciplined naming structure embeds the bidding strategy and the campaign's job in a way you can parse instantly.

How to name Target CPA and Target ROAS campaigns

Follow these steps in order. Each step builds on the one before it.

1. Start with the bid strategy abbreviation. Use tCPA or tROAS as the first token in the name. This way every list sorts by strategy automatically. Expected outcome: you can group and filter by strategy without opening a single campaign.

2. Add the campaign type or channel. Specify whether it's Search, Shopping, PMax, etc. Expected outcome: you know where the campaign runs without needing to look.

3. Add the product, market, or objective. Use a short, consistent label like Shoes, US, or LeadGen. Expected outcome: you know what the campaign is advertising and for whom.

4. Add the target value if you want to see the goal in the name. For example, tCPA20 for a $20 target CPA, or tROAS400 for a 400% target ROAS. Expected outcome: you can compare actual performance against your target directly from the campaign list.

5. Use a consistent separator. Pick a delimiter like a pipe | or a dash - and stick to it across the entire account. Expected outcome: no parsing ambiguity when you scan or export the names.

6. Assemble the full name. Combine all parts in a fixed order. For example: tCPA|Search|Shoes|US|20 or tROAS - Shopping - Apparel - 400. Expected outcome: a complete name that tells you the strategy, channel, product, market, and target.

7. Append a version if you run iterations. Use v2, v3, etc., when you test changes. Expected outcome: you can tell which iteration is which without relying on dates.

Example naming convention

Here's what a set of named campaigns looks like with this convention:

• tCPA|Search|Shoes|US|20
• tROAS|PMax|Apparel|US|400
• tCPA|LeadGen|Legal|CA|40

Each name instantly tells you the bidding strategy, campaign type, offer, market, and target. That's enough information to make a first pass on performance without opening the campaign.

Pitfalls to avoid

• Don't bury the bid strategy in the middle or end. Put it first, or you'll have to read the whole name.
• Don't use inconsistent case. Pick one convention—lowercase, uppercase, or CamelCase—and use it everywhere. Inconsistent case breaks sorting and filtering.
• Don't use spaces as separators. Spaces make names harder to parse and can break in exports. Use a delimiter like | or -.
• Don't rely solely on names. Naming is the first line of defense, but combine it with labels for even cleaner reporting. Labels let you group campaigns across naming schemes without renaming anything.

A clean naming convention is a small investment that pays off every time you open the account. It's also one of the structural details that keeps large accounts manageable, especially when you're balancing efficiency (Target CPA) against revenue (Target ROAS) across multiple campaigns.