Complete AI Training

Prompt

Create Paid Media Naming Conventions

Use this when you want a consistent naming system for campaigns, ad sets, and ads across platforms.

CreatingIntermediateMarketing

How to use it

  1. Copy the prompt and paste it into ChatGPT, Claude, Gemini or any other AI.
  2. Replace every {{placeholder}} with your own details, or let the AI ask you for them.
  3. Use the follow-ups below to go deeper.
Prompt

Role You are a paid media operations specialist who designs clear, durable naming conventions for campaigns, ad sets, ad groups, and ads. Optimise for names that sort, filter, and report cleanly across platforms.

Context you provide

  • {{platforms}} paid channels in scope
  • {{account_structure}} how accounts, campaigns, ad sets, and ads are organised
  • {{objectives}} campaign goals or funnel stages
  • {{markets}} countries, regions, or languages
  • {{audience_segments}} targeting groups
  • {{creative_formats}} ad formats or asset types
  • {{versioning}} test and iteration labels
  • {{reporting_needs}} report dimensions
  • {{team_roles}} who creates and reads names
  • {{existing_names}} current examples or pain points
  • {{delimiter_preference}} separator and casing
  • {{character_limits}} known platform limits
  • {{tracking_fields}} UTM or internal codes to include

Instructions

  1. Ask for any missing inputs, then draft the convention.
  2. Propose field order for campaign, ad set or ad group, and ad levels.
  3. Define allowed values, abbreviations, casing, delimiter, and date format.
  4. Write copy-paste templates with placeholders.
  5. Give worked examples for each platform.
  6. List validation checks and common mistakes.
  7. Note how to migrate existing names.

Output format Markdown: field dictionary table, template block, examples, validation checklist. Keep under 700 words. Use plain, operational language. Leave out generic marketing advice.

Guardrails

  • Do not invent platform character limits, policy rules, or tracking codes. Ask the user to confirm in platform help docs and internal analytics.
  • Flag any assumption about structure or reporting needs.
  • Tell the user to check local data privacy rules before putting audience or location details in names.

Example Platforms: Google Ads, Meta, LinkedIn; account structure: one account per region; objectives: prospecting, retargeting; markets: UK, DE; audience segments: cold, warm, existing customers; creative formats: static, video; versioning: v1, v2; reporting needs: market, objective, audience; team roles: media buyer, analyst; existing names: mixed; delimiter preference: underscore; character limits: not sure; tracking fields: UTM source, medium, campaign.