Naming Convention Validator
Define a regex schema, paste names, get violations with reasons
Define your naming convention as a regex (or use a preset), paste your campaign / ad-group / asset-group names, and get a line-by-line pass/fail report. The thing you wish your team had been doing for the last two years.
- Pick a preset (BRAND_GEO_CAMPAIGNTYPE_MATCHTYPE, BRAND_VERTICAL_FUNNEL, etc.) or write your own regex.
- Paste names into the input — one per line.
- Output: each name tagged Pass or Fail with the specific token that failed and the position.
- Copy the failing names for re-naming, or copy a "campaigns to rename" report for the account lead.
Failing names — copy to rename
Paste names to validate.
Why this exists
Naming conventions are the unsung backbone of every reporting pipeline. Teams set them, then drift, then nothing aggregates correctly two years later. This is the validator that catches the drift in a five-second paste.
Frequently asked
What is a good Google Ads naming convention?
BRAND_REGION_CHANNEL_OBJECTIVE is the most common starting point: "ACME_US_SEARCH_LEADGEN". The exact tokens depend on the account — multi-brand teams add brand, e-commerce teams add product line, B2B SaaS teams add funnel stage. The non-negotiable rule is: every token must be parseable without lookups.
Why use a regex to validate names?
A regex turns the convention into a single source of truth that any team member can run. Without it, the convention lives in a Notion doc that drifts. With it, you can paste 200 campaign names and get back a list of violations in seconds.
Can I edit the regex for my own convention?
Yes. The presets are starting points; the regex field is fully editable. Anything that runs in JavaScript RegExp constructor works.