Skip to main content

UTM Builder

Build URLs with standard UTM tags for Google Ads, Meta Ads, email, and other channels

Required parameters

Optional parameters

Result
Fill in the page URL and required UTM fields

ValueTrack parameters (Google Ads only)

Recommended ValueTrack tokens

Advanced ValueTrack parameters

Google Ads ValueTrack parameters reference
  • {adgroupid}Ad group ID. Use when tracking is configured at the account or campaign level.
  • {adposition}Ad position on the page (e.g. 1t2 = page 1, top of search results, position 2).
  • {campaignid}Campaign ID.
  • {creative}Unique ID of the ad.
  • {device}Device type that generated the click (mobile, desktop, tablet).
  • {feeditemid}ID of the extension the user clicked.
  • {keyword}Keyword that triggered the ad.
  • {loc_interest_ms}Location ID from locations of interest in the user's search query.
  • {loc_physical_ms}Geographic location ID where the click originated.
  • {lpurl}Final URL. Escaped (URL-encoded) unless placed at the beginning of the tracking template.
  • {matchtype}Keyword match type.
  • {merchant_id}Google Merchant Center account ID.
  • {network}Where the click came from: Google Search, search partners, Display Network, YouTube, or Performance Max.
  • {placement}Website where the ad was clicked.
  • {product_channel}Product sales channel type.
  • {product_country}Country where the product is sold.
  • {product_id}Product ID from the Merchant Center feed.
  • {product_language}Language of the product information.
  • {product_partition_id}Unique ID of the product group.
  • {store_code}Unique store code for local inventory ads.
  • {targetid}ID of the keyword, dynamic search ad target, remarketing list, or product group that triggered the ad.
  • {target}Placement category for placement-targeted campaigns.
  • {adtype}Product ad type in Shopping campaigns: pla, pla_multichannel, pla_with_promotion, or pla_with_pog.
  • {devicemodel}Device model of the user (e.g. Apple+iPhone). Available on Display Network campaigns only.
  • {param1}Custom parameter #1 — for advanced Google Ads tracking only.
  • {param2}Custom parameter #2 — for advanced Google Ads tracking only.

Frequently asked questions

What are UTM parameters?

UTM parameters are tags appended to a URL (utm_source, utm_medium, utm_campaign, utm_term, utm_content) that tell analytics where a click came from. GA4 reads them at session start and attributes traffic to a campaign. Without UTM tags, paid, email, and social traffic often collapses into generic source / medium rows such as google / cpc or facebook / paid with no campaign detail.

How do ValueTrack parameters differ from standard UTM tags?

ValueTrack parameters are Google Ads placeholders like {keyword} or {campaignid} replaced with real values at click time. Standard UTM values are universal static tags for any channel. ValueTrack works only in Google Ads and does not apply to Meta Ads, email, or organic links.

Do UTM parameters affect SEO?

UTM parameters by themselves neither help nor hurt your search rankings. The real risk is different: Google treats a URL with query parameters as a separate address, so tagged links can end up indexed as duplicates of the clean page. A canonical tag pointing to the clean URL prevents that. UTM tags exist for tracking and attribution, not for SEO.

Which characters should not be used in UTM parameters?

Avoid spaces (use underscores instead) and unencoded #, ?, &, and = inside parameter values, since they break the URL. Common practice is to keep values in lowercase Latin characters: GA4 is case-sensitive, so Google and google become two separate sources. Non-Latin characters work technically but turn into percent-encoded strings that are hard to compare in reports. Stick to a team naming convention.

Last updated: August 13, 2026

What are UTM parameters and why they matter

UTM parameters reveal which source, campaign, and ad actually brought a user to a conversion. Without them, Google Analytics may group paid visits, email clicks, and social posts into vague channels or classify some sessions as direct. Traffic attribution then becomes unreliable: the marketer can see a sale but cannot confidently connect it to a specific campaign. Consistent tagging makes campaign tracking useful for optimization and provides the dependable acquisition data required for end-to-end analytics.

The five standard UTM parameters and their roles

The five UTM parameters describe a click from its channel down to a specific creative. utm_source identifies the source, such as google, facebook, or newsletter; utm_medium defines the traffic type, such as cpc, paid_social, or email. utm_campaign stores a stable campaign name, for example brand_search_uk. Optional utm_content differentiates banners, ads, or calls to action, while utm_term carries a keyword or audience label. Standard UTM parameters are platform-independent: use them with Google Ads, Meta Ads, email, partner content, and organic posts. Define readable values before launch rather than trying to decode them after data has accumulated.

Google Ads ValueTrack parameters for dynamic tracking

ValueTrack parameters automatically attach actual Google Ads click details to the destination URL. Placeholders such as {campaignid}, {keyword}, {matchtype}, {device}, and {creative} are replaced at click time, allowing one template to support hundreds of ads. This is specific to Google Ads; Meta Ads, email platforms, and other channels do not process these tokens. ValueTrack complements rather than replaces static utm_source, utm_medium, and utm_campaign values. A practical setup keeps a readable name in utm_campaign and sends the dynamic campaign ID in a separate parameter. This makes records easier to reconcile across Google Analytics, Google Ads, and the CRM.

Common UTM tagging mistakes

Inconsistent values damage reports more often than missing UTM parameters. Google Analytics treats google and Google, or paid_social and paid-social, as separate rows, fragmenting one campaign across multiple sources. Spaces, mixed alphabets, improvised names, and reversed source and medium values make traffic attribution harder to maintain. Another common error is defining the same parameters in both the final URL and a tracking template, where the outcome depends on platform precedence rules. Before launch, open the generated link, test every redirect, and confirm that all parameter values reach analytics unchanged.

How to build a team naming convention

A shared vocabulary and naming template keep data clean when several specialists launch campaigns. Document the allowed utm_source and utm_medium values, the utm_campaign format, and the order of components—for example, country_product_objective_period. Use lowercase Latin characters and choose one separator, either underscores or hyphens. Define what belongs in utm_content and utm_term, then provide two or three valid examples for every channel. Keep the rules in a shared document, assign an owner for changes, and regularly audit new campaigns in Google Analytics. This turns the naming convention into an operating standard rather than forgotten documentation.

How to use the PPC-Hub UTM Builder

The PPC-Hub UTM Builder creates a ready-to-use tracking URL as soon as you enter the destination URL, utm_source, utm_medium, and utm_campaign. Add utm_content, utm_term, or custom parameters when more detail is required. For Google Ads campaigns, quick-insert buttons add recommended ValueTrack parameters, while the advanced list includes Shopping and Merchant Center tokens. Copy the result, test the visit, and place the URL in the platform according to its requirements. After tracking is configured, validate campaign economics with the PPC calculators; when preparing search keywords, use the keyword match type generator. This preserves a clear workflow from campaign structure and tagging to performance analysis.