Conversion Action Naming Convention
Why It Matters
Naming conventions for conversion actions follow the same logic as the naming-conventions check for GTM tags: the name is the primary auditor signal, and consistency speeds every governance cycle. The recommended pattern in measurement teams is <Event>. <Source> (e.g. "Purchase. Website," "Lead. Salesforce Import"). When the same account mixes "Purchase," "purchase-web," "Website Purchase," and "purchase_web_v2," every audit costs more time than it should, and similarly-named actions get confused with each other in campaign goal setup.
How To Fix It
Adopt and document the
<Event>. <Source>convention.Rename existing actions in batches. Renaming is non-destructive and preserves all historical data.
Treat naming as a publish-gating governance check at the team level.
New conversion actions should follow the convention by default.
Example
Inconsistent: Purchase, purchase-web, Website Purchase, purchase_v2
Consistent: Purchase. Website, Purchase. Offline, Purchase. AppGoogle Ads conversion actions with inconsistent naming patterns. Measurement-governance best practice, conversion action names should follow a consistent <Event>. <Source> pattern to speed audits and reduce campaign-goal-misassignment risk. Fix: adopt the convention, rename existing actions, and treat naming as a governance gating check. Source: support.google.com/google-ads/answer/6095821.
Drop this paragraph into your client deliverable. Sources back to the canonical platform documentation linked below.