Attribution Taxonomy & Terminology

UTM & Tracking Glossary

Factual, engineering-grade definitions and compliance rules for digital marketing parameters.

utm_source

Core UTM Parameter
Required
Technical Definition: Identifies the specific platform, advertiser, publisher, or digital property transmitting traffic to your website.
Analytics Impact: Mandatory in GA4 and universal analytics engines. Without utm_source, tracking libraries cannot classify the session referrer.
// Syntax Example:utm_source=google | utm_source=facebook | utm_source=newsletter_weekly
Implementation Standard: Always use strict lowercase. Represent the platform itself (e.g. 'google', 'meta', 'linkedin'), not the ad creative type.

utm_medium

Core UTM Parameter
Required for GA4
Technical Definition: Identifies the high-level advertising or marketing medium (e.g., cost-per-click, banner, email, organic social).
Analytics Impact: Essential for GA4 Default Channel Grouping. GA4 applies regex rules to utm_medium to categorize traffic into 'Paid Search', 'Paid Social', 'Email', etc.
// Syntax Example:utm_medium=cpc | utm_medium=email | utm_medium=paid_social | utm_medium=affiliate
Implementation Standard: Stick strictly to recognized GA4 medium values. Using custom non-standard mediums (e.g., 'sponsored_post') forces traffic into the 'Unassigned' channel.

utm_campaign

Core UTM Parameter
Recommended
Technical Definition: Identifies the specific promotional campaign, seasonal push, product launch, or strategic marketing initiative.
Analytics Impact: Recommended. Groups all inbound visits under a single strategic umbrella in attribution dashboards.
// Syntax Example:utm_campaign=summer_sale_2026 | utm_campaign=q3_leadgen_us
Implementation Standard: Establish a company-wide taxonomy (e.g., [Year]_[Season]_[Geo]_[Promo]). Replace spaces with underscores or hyphens.

utm_term

Core UTM Parameter
Optional
Technical Definition: Captures paid search keywords or audience targeting criteria responsible for triggering the ad click.
Analytics Impact: Optional. Primarily used for manual paid search tagging on non-Google networks (Bing Ads, Baidu, DuckDuckGo).
// Syntax Example:utm_term=running_shoes | utm_term=enterprise_crm_software
Implementation Standard: URL-encode multi-word terms with plus signs or underscores. Do not use for Google Ads if Auto-Tagging (GCLID) is active.

utm_content

Core UTM Parameter
Optional
Technical Definition: Differentiates ad variations, creative formats, or multiple links pointing to the same destination URL within a single email/ad.
Analytics Impact: Optional. Crucial for conversion rate optimization (CRO) and multivariate A/B testing.
// Syntax Example:utm_content=hero_blue_button | utm_content=textlink_footer | utm_content=300x250_banner
Implementation Standard: Use descriptive descriptors to isolate layout elements, creative sizes, or specific value propositions.

utm_id

GA4 Extended Parameter
GA4 Extended
Technical Definition: The unique Campaign ID used to join offline campaign cost and revenue data with Google Analytics 4 via Data Import.
Analytics Impact: Optional. Required when using GA4 CSV cost data import or connecting external BI reporting warehouses.
// Syntax Example:utm_id=camp_784912
Implementation Standard: Match this exact ID with your internal marketing database primary key or ad server campaign identifier.

utm_source_platform

GA4 Extended Parameter
GA4 Extended
Technical Definition: Identifies the digital platform or media-buying suite managing the campaign (e.g. Search Ads 360, DV360, Meta Ads Manager).
Analytics Impact: Optional. Provides granularity when multiple buying tools deliver campaigns on the same publisher.
// Syntax Example:utm_source_platform=sa360 | utm_source_platform=meta_business_suite
Implementation Standard: Standardize platform abbreviations across marketing teams to maintain clean segmentation.

utm_creative_format

GA4 Extended Parameter
GA4 Extended
Technical Definition: Identifies the structural type or creative specification of the marketing asset.
Analytics Impact: Optional. Introduced in GA4 to analyze creative format effectiveness (video vs image vs carousel).
// Syntax Example:utm_creative_format=video_vertical | utm_creative_format=carousel | utm_creative_format=stories
Implementation Standard: Keep format definitions consistent across channels so creative performance can be aggregated globally.

GCLID, GBRAID & WBRAID

Click Identifiers
Google Auto-Tagging
Technical Definition: Cryptographic click identifiers appended automatically by Google Ads. GCLID is standard click tracking; GBRAID and WBRAID are privacy-preserving identifiers developed for iOS 14.5+ App-to-Web and Web-to-Web attribution.
Analytics Impact: Automatic when Google Ads Auto-Tagging is enabled. Transmits cost, keyword, and match type without manual UTM strings.
// Syntax Example:?gclid=EAIaIQobChMI... | ?wbraid=CjgKCAjw...
Implementation Standard: Ensure server redirects do not strip these parameters; stripping them causes Google Ads conversion tracking to fail.

Provider Token (pt) & Campaign Token (ct)

App Attribution
iOS App Store
Technical Definition: Apple App Store analytics tokens used to attribute iOS app downloads and subscriptions in Apple App Store Connect.
Analytics Impact: Required for App Store marketing links. 'pt' identifies your 6-digit Apple developer account; 'ct' contains a campaign slug (up to 40 alphanumeric characters).
// Syntax Example:https://apps.apple.com/app/id123456789?pt=118234&ct=summer_promo&mt=8
Implementation Standard: Apple strictly limits 'ct' to 40 characters without spaces or special symbols. Use ValidateURL's iOS Campaign Validator to check tokens.

Google Play Install Referrer

App Attribution
Android Google Play
Technical Definition: The nested query string parameter used by Google Play Store to pass acquisition data to Android apps post-installation via the Play Install Referrer API.
Analytics Impact: Required for Android marketing attribution. Encapsulates standard UTM parameters inside an encoded 'referrer=' parameter.
// Syntax Example:https://play.google.com/store/apps/details?id=com.app&referrer=utm_source%3Dgoogle%26utm_medium%3Dcpc
Implementation Standard: The nested UTMs must be URL-encoded (using %3D for '=' and %26 for '&'). Double-escaping breaks Android SDK parsing.

Audit Your Marketing Links

Now that you know the parameters and naming standards, check your campaigns with our instant URL validator.