{"id":829,"date":"2026-04-17T09:00:00","date_gmt":"2026-04-17T14:00:00","guid":{"rendered":"https:\/\/tolinku.com\/blog\/?p=829"},"modified":"2026-03-07T03:33:51","modified_gmt":"2026-03-07T08:33:51","slug":"utm-parameter-strategy","status":"publish","type":"post","link":"https:\/\/tolinku.com\/blog\/utm-parameter-strategy\/","title":{"rendered":"UTM Parameter Strategy for Mobile Deep Links"},"content":{"rendered":"\n

UTM parameters are the standard way to track where your traffic comes from. They work well on the web, but mobile deep links introduce complications: links pass through app stores, redirect chains, and cross-device flows. Without a deliberate strategy, your UTM data ends up messy and unreliable.<\/p>\n\n\n\n

This guide covers how to build a UTM strategy that works specifically for mobile deep link campaigns.<\/p>\n\n\n\n

\"Tolinku\nThe analytics dashboard with date range selector, filters, charts, and breakdowns.<\/em><\/p>\n\n\n\n

UTM Basics (Quick Refresher)<\/h2>\n\n\n\n

UTM parameters are query string tags appended to URLs. There are five standard parameters defined by Google's campaign URL builder<\/a>:<\/p>\n\n\n\n

\n\n\n\n\n\n\n\n
Parameter<\/th>\nRequired<\/th>\nPurpose<\/th>\nExample<\/th>\n<\/tr>\n<\/thead>\n
utm_source<\/td>\nYes<\/td>\nWhere the traffic comes from<\/td>\nemail<\/code>, facebook<\/code>, partner_blog<\/code><\/td>\n<\/tr>\n
utm_medium<\/td>\nYes<\/td>\nThe marketing medium<\/td>\ncpc<\/code>, social<\/code>, email<\/code>, referral<\/code><\/td>\n<\/tr>\n
utm_campaign<\/td>\nYes<\/td>\nThe specific campaign<\/td>\nsummer_sale_2026<\/code>, onboarding_v2<\/code><\/td>\n<\/tr>\n
utm_term<\/td>\nNo<\/td>\nPaid search keywords<\/td>\nrunning_shoes<\/code>, budget_app<\/code><\/td>\n<\/tr>\n
utm_content<\/td>\nNo<\/td>\nDifferentiates ad variations<\/td>\nhero_image<\/code>, sidebar_cta<\/code>, blue_button<\/code><\/td>\n<\/tr>\n<\/tbody><\/table><\/figure>\n\n\n\n

A fully tagged deep link looks like:<\/p>\n\n\n\n

https:\/\/go.yourapp.com\/summer-sale?utm_source=email&utm_medium=newsletter&utm_campaign=summer_sale_2026&utm_content=hero_cta\n<\/code><\/pre>\n\n\n\n
For the basics of adding UTM parameters to short links, see UTM Parameters and Short Links<\/a>.<\/p>\n\n\n\n
Why Mobile Needs a Different Strategy<\/h2>\n\n\n\n
On the web, UTM parameters flow cleanly: user clicks a link, lands on a page, and your analytics tool reads the URL parameters. Done.<\/p>\n\n\n\n
On mobile, the flow is more complex:<\/p>\n\n\n\n
    \n
  1. User clicks a link with UTM parameters<\/li>\n
  2. The deep linking platform processes the click and records the parameters<\/li>\n
  3. If the app is installed: the app opens, but the URL the app receives may or may not include the original UTM parameters (depends on the OS and link type)<\/li>\n
  4. If the app is not installed: the user is redirected to the app store, installs the app, and opens it. The original UTM parameters are only available through deferred deep linking<\/li>\n<\/ol>\n\n\n\n
    This means you can't just append UTM parameters and hope they make it through. You need to ensure your deep linking platform captures and preserves them through every possible routing path.<\/p>\n\n\n\n
    Building Your Naming Convention<\/h2>\n\n\n\n
    Inconsistent naming is the number one UTM problem. "Email" and "email" and "EMAIL" are three different sources in your analytics. "facebook" and "Facebook" and "fb" and "meta" are four.<\/p>\n\n\n\n
    Rules<\/h3>\n\n\n\n
      \n
    1. Lowercase everything<\/strong>: email<\/code>, not Email<\/code> or EMAIL<\/code><\/li>\n
    2. Use underscores for spaces<\/strong>: summer_sale<\/code>, not summer sale<\/code> or summer-sale<\/code><\/li>\n
    3. Be specific but concise<\/strong>: partner_techcrunch<\/code>, not partner<\/code> or techcrunch_sponsored_article_july_2026<\/code><\/li>\n
    4. Use consistent vocabulary<\/strong>: If email is email<\/code>, always call it email<\/code>, not newsletter<\/code> or mail<\/code><\/li>\n
    5. Document everything<\/strong>: Maintain a shared reference document with approved values<\/li>\n<\/ol>\n\n\n\n
      Source Values<\/h3>\n\n\n\n
      Standardize source names:<\/p>\n\n\n\n
      \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
      Source<\/th>\nutm_source<\/th>\n<\/tr>\n<\/thead>\n
      Email campaigns<\/td>\nemail<\/code><\/td>\n<\/tr>\n
      Facebook (organic)<\/td>\nfacebook<\/code><\/td>\n<\/tr>\n
      Facebook (paid)<\/td>\nfacebook_ads<\/code><\/td>\n<\/tr>\n
      Instagram (organic)<\/td>\ninstagram<\/code><\/td>\n<\/tr>\n
      Instagram (paid)<\/td>\ninstagram_ads<\/code><\/td>\n<\/tr>\n
      Twitter\/X<\/td>\ntwitter<\/code><\/td>\n<\/tr>\n
      TikTok<\/td>\ntiktok<\/code><\/td>\n<\/tr>\n
      Google Ads<\/td>\ngoogle_ads<\/code><\/td>\n<\/tr>\n
      Apple Search Ads<\/td>\napple_search<\/code><\/td>\n<\/tr>\n
      SMS<\/td>\nsms<\/code><\/td>\n<\/tr>\n
      Push notifications<\/td>\npush<\/code><\/td>\n<\/tr>\n
      QR codes<\/td>\nqr<\/code><\/td>\n<\/tr>\n
      Partner sites<\/td>\npartner_{name}<\/code><\/td>\n<\/tr>\n
      Influencers<\/td>\ninfluencer_{name}<\/code><\/td>\n<\/tr>\n
      Internal (cross-promo)<\/td>\ninternal<\/code><\/td>\n<\/tr>\n<\/tbody><\/table><\/figure>\n\n\n\n
      Medium Values<\/h3>\n\n\n\n
      Use the standard medium taxonomy:<\/p>\n\n\n\n
      \n\n\n\n\n\n\n\n\n\n\n\n\n
      Medium<\/th>\nutm_medium<\/th>\n<\/tr>\n<\/thead>\n
      Paid ads<\/td>\ncpc<\/code><\/td>\n<\/tr>\n
      Organic social<\/td>\nsocial<\/code><\/td>\n<\/tr>\n
      Email<\/td>\nemail<\/code><\/td>\n<\/tr>\n
      Referral links<\/td>\nreferral<\/code><\/td>\n<\/tr>\n
      Push notifications<\/td>\npush<\/code><\/td>\n<\/tr>\n
      SMS\/messaging<\/td>\nsms<\/code><\/td>\n<\/tr>\n
      QR codes<\/td>\nqr<\/code><\/td>\n<\/tr>\n
      Display ads<\/td>\ndisplay<\/code><\/td>\n<\/tr>\n
      Affiliate<\/td>\naffiliate<\/code><\/td>\n<\/tr>\n
      In-app banners<\/td>\nin_app<\/code><\/td>\n<\/tr>\n<\/tbody><\/table><\/figure>\n\n\n\n
      Campaign Naming<\/h3>\n\n\n\n
      Campaign names should be descriptive and follow a pattern:<\/p>\n\n\n\n
      {type}_{name}_{date}\n<\/code><\/pre>\n\n\n\n
      Examples:<\/p>\n\n\n\n