How to use the Campaign Naming Convention Generator.
A naming system should support the reports the team actually uses. Document allowed values and separators so names stay consistent as campaigns grow.
Make the workflow fit your task.
Choose the reporting dimensions the team needs and define their order, separator and allowed values. Generate sample names, including an edge case, then document how new markets or objectives should be added.
- What you provide
- Channels, markets and reporting needs.
- What you get
- Naming rules with worked examples.
See the input and the result.
Illustrative input and output · a teaching example, not a live WebAct run
Example input
Create names using channel_market_objective_YYYYMM. Approved channels: search, social. Markets: us, uk. Objectives: trial, demo. Campaigns: US search trial and UK social demo, both October 2026.
Completed example
search_us_trial_202610 social_uk_demo_202610 Field order: channel, market, objective, month. Use lowercase approved values and underscores; add new values to the shared reference before using them.
Load this input into the prompt, then copy it to WebAct to try the task. Your result may differ from the illustration.
Decisions and troubleshooting.
Should campaign names contain every available detail?
Include stable fields that help reporting and identification. Put frequently changing or lengthy information in dedicated metadata where available.
Why can the same name be interpreted in two ways?
Use controlled values and an unambiguous separator. Document field order so a label is not mistaken for a market or objective.
Try it with your own source.
Replace the example with your material in the task prompt. Keep the requirements you need, then copy the task into WebAct.
Customize and copy the task ↑