Build campaign URLs with properly formatted UTM parameters using the form above, then validate them against GA4 conventions — lowercase, no spaces, no special characters. Each URL gets a severity rating and an automatic fix you can copy.
Build campaign URLs with correct UTM parameters, then validate them below before launch.
A ready-to-use CSV with naming conventions for every major channel. Share it with your team so everyone builds UTM links the same way.
A well-built UTM link has three required parameters — utm_source identifies the traffic source (e.g. google, linkedin), utm_medium describes the marketing channel (e.g. cpc, email, social), and utm_campaign names the specific campaign. Two optional parameters — utm_content and utm_term — let you track creative variants and paid keywords.
The most common mistakes are mixed case (e.g. Google vs google), spaces in values, and non-standard medium names that cause GA4 to bucket traffic as "Unassigned." This builder validates every parameter in real time.
Use this page when you need to create tracking links before launching a campaign: paid search ads, newsletter links, creator collaborations, product launches, partner referrals, or any link that needs clean reporting in GA4. The goal is not just to add parameters, but to keep the naming consistent before traffic starts coming in.
If you already have a spreadsheet of links, paste them into the checker after building your first URL. You can catch missing campaign names, mixed capitalization, and values that will break GA4 channel grouping before those links are sent to customers.
google, linkedin, or newsletter.cpc, email, social, or referral.spring_launch_2026.Yes. A basic campaign URL builder creates a tagged link. This page also validates the final URL against GA4 naming rules, so you can spot values that may create messy reports.
No. Most campaigns only need utm_source, utm_medium, andutm_campaign. Use utm_content for creative variants andutm_term for paid keyword tracking.
Yes. The checks are designed around GA4 reporting habits, especially lowercase naming, consistent medium values, and avoiding traffic being grouped as Unassigned.
We are exploring bulk validation APIs, shared team naming policies, and scheduled campaign checks. Tell us your use case below.