DeFi Campaign Naming Convention Template
Inconsistent campaign names are the #1 reason crypto marketing data becomes unusable. This free template gives your team a shared naming standard for UTM parameters, ad campaigns, and tracking links—so every channel rolls up cleanly in analytics.
The Naming Convention
Every campaign name follows one format:
Examples:
| Campaign Name | Chain | Channel | Type | Date |
|---|---|---|---|---|
| ethereum_twitter_token-launch_2026-03_v1 | Ethereum | Twitter/X | Token Launch | Mar 2026 |
| arbitrum_kol_defi-promo_2026-03_alpha | Arbitrum | KOL | DeFi Promo | Mar 2026 |
| base_discord_airdrop_2026-04_announce | Base | Discord | Airdrop | Apr 2026 |
What's Inside the Template
Naming Rules
The master tab with field definitions, allowed values for each segment, and formatting rules (lowercase, no spaces, hyphens within words).
Examples — DeFi, NFT, Token Launch
Pre-filled examples for common Web3 campaign types so your team can see the convention in action across different verticals.
UTM Parameter Guide
Maps each naming field to the correct UTM parameter. Shows exactly how a campaign name like "base_twitter_airdrop_2026-03_v1" becomes utm_source, utm_medium, and utm_campaign values.
Quick Reference
A one-page cheat sheet with the format, field options, and dos/don'ts. Print it or pin it in your team's Slack channel.
Common Naming Mistakes
Inconsistent casing
"Twitter" vs "twitter" vs "TWITTER" creates three separate sources in every analytics tool. Always use lowercase.
No date stamps
Without dates, you can't tell Q1 campaigns from Q3. Include YYYY-MM so campaigns sort chronologically and you can filter by time.
Too vague names
"campaign1" or "test" tells you nothing 3 months later. Be specific: chain, channel, and purpose should be obvious from the name alone.
Mixing languages and formats
Some teams mix English and local terms, or switch between "paid-social" and "ads". Pick one glossary and enforce it in the template.
Why Naming Conventions Matter for Attribution
Attribution tools—including Web3 Trackers—group conversions by campaign name. If two team members tag the same campaign differently, your data splits into separate buckets. You see half the conversions under one name and half under another.
A shared naming convention ensures every UTM link, ad campaign, and tracking event uses the same identifiers. When your data is consistent, attribution tools can accurately credit each channel and campaign for on-chain conversions.
Web3 Trackers works best with clean, consistent campaign names. Pair this template with our UTM Builder and KOL tracker to build an attribution stack that scales with your marketing.
FAQs
Why do campaign naming conventions matter?
Inconsistent names make it impossible to filter, group, or compare campaigns in analytics. "eth_twitter_airdrop" and "Twitter - Airdrop ETH" look like different campaigns even though they're the same. A naming convention fixes this permanently.
Should I use underscores or hyphens?
Use underscores (_) to separate fields and hyphens (-) within multi-word values. For example: ethereum_twitter_token-launch_2026-03_v1. This makes it easy to split fields programmatically.
How do naming conventions connect to UTM parameters?
Your naming convention defines the values you put into utm_source, utm_medium, and utm_campaign. If everyone follows the same rules, your analytics data stays clean and filterable across every tool.
What if my team already has messy campaign names?
Start the convention going forward—don't try to rename historical data. Document the new rules in this template, share with everyone who creates campaigns, and enforce it in review. Clean data starts accumulating immediately.
Can I customize this template for my project?
Absolutely. The template includes editable fields for chain names, channel lists, and campaign types. Adapt it to your specific protocols, chains, and marketing channels. The structure stays the same.
Clean names, clear attribution
Naming conventions are the foundation. Web3 Trackers builds on that foundation by connecting your consistently-named campaigns to actual on-chain conversions—swaps, mints, and transfers attributed to every source.