How to Prevent UTM Tracking Issues: The Complete Pre-Launch Checklist

The Cost of Broken UTM Tracking

A single misconfigured campaign URL can waste thousands in ad spend while providing zero attribution data.

Consider this scenario: You launch a $10,000 Facebook campaign. The ads perform well - high CTR, strong engagement. But in GA4? Direct / (none). No source. No medium. No campaign data. Just "Direct" traffic that can't be attributed to your investment.

The culprit? A simple # placed before the ? in your landing page URL. Five minutes of validation would have caught it.

This guide will help you prevent that.

Why Prevention Beats Troubleshooting

Prevention takes 5 minutes. Troubleshooting takes hours.

The math is simple: Spending 10 minutes validating before launch prevents:

• Lost attribution data you can never recover
• Wasted ad spend with no ROI visibility
• Emergency troubleshooting sessions
• Explaining to stakeholders why the data is missing
• Re-running campaigns with correct tracking

Prevention is not optional. It's foundational to reliable analytics.

The UTM Prevention Framework

This framework ensures reliable campaign tracking across all channels and platforms.

Three pillars:

1. Validate: Check URL structure before launch
2. Test: Verify tracking works in real conditions
3. Monitor: Catch issues immediately if they occur

Each pillar has specific steps, tools, and success criteria.

Pillar 1: Pre-Launch Validation

Validation catches structural and formatting issues before any URLs go live.

The Essential Validation Checklist

Run every campaign URL through this checklist: (click to enlarge - right click to open in a new tab)

1. UTM Parameter Presence

What to check:

• utm_source is present
• utm_medium is present
• utm_campaign is present
• Optional parameters (utm_content, utm_term) if using them

Why this matters: GA4 requires utm_source and utm_medium for proper channel grouping. Missing either parameter results in "Unassigned" traffic.

Common mistakes:

X Missing medium:
example.com/page?utm_source=newsletter&utm_campaign=jan_sale

X Misspelled parameter:
example.com/page?utm_source=email&utm_medum=newsletter

X Using non-UTM names:
example.com/page?source=email&medium=newsletter

Correct format:

OK All required parameters present:
example.com/page?utm_source=newsletter&utm_medium=email&utm_campaign=jan_sale

Pro tip: Always include utm_campaign even though it's technically optional. It's essential for campaign-level reporting and ROI analysis.

2. Fragment Placement

What to check:

• UTM parameters come after the ?
• UTM parameters come before any # fragment
• Only one ? character in the URL
• Fragment identifier (if present) is at the end

Why this matters: Browsers don't send anything after # to servers. Parameters after the fragment are invisible to GA4.

Wrong examples:

X UTMs after fragment:
example.com/page#section?utm_source=email&utm_medium=email

X Multiple question marks:
example.com/page?tab=pricing?utm_source=email&utm_medium=email

X Fragment in middle of query string:
example.com/page?utm_source=email#section&utm_medium=email

Correct examples:

OK UTMs before fragment:
example.com/page?utm_source=email&utm_medium=email#section

OK No fragment (also fine):
example.com/page?utm_source=email&utm_medium=email

OK Fragment at end:
example.com/pricing?utm_source=email&utm_medium=email&utm_campaign=q1#plans

Visual rule: The order must always be: domain/path?parameters#fragment

3. Value Formatting

What to check:

• All values are lowercase
• No spaces in any parameter value
• No special characters (&, =, ?, #)
• Delimiters are hyphens (-) or underscores (_)
• No leading or trailing whitespace

Why this matters:

• GA4 is case-sensitive: Email != email != EMAIL
• Spaces can break URL parsing or create encoding issues
• Special characters interfere with query string structure
• Inconsistent formatting fragments your reporting

Check out our in-depth guide on GA4 case sensitivity to learn more.

Common mistakes:

X Mixed case:
utm_source=Newsletter&utm_medium=Email

X Spaces:
utm_campaign=summer sale 2024

X Special characters:
utm_content=cta&button

X Plus signs (treated as spaces):
utm_campaign=new+product

Correct format:

OK Lowercase with hyphens:
utm_source=newsletter&utm_medium=email&utm_campaign=summer-sale-2024

OK Lowercase with underscores:
utm_source=newsletter&utm_medium=email&utm_campaign=summer_sale_2024

OK Simple descriptive values:
utm_source=facebook&utm_medium=paid_social&utm_campaign=q1_promo

Best practices:

• Pick one delimiter (hyphen or underscore) and use it consistently
• Use lowercase for everything to avoid case-sensitivity issues
• Keep values descriptive but concise (avoid overly long strings)
• Use consistent naming conventions across all campaigns

4. URL Structure

What to check:

• Valid protocol (http:// or https://)
• Valid domain name (no spaces, proper TLD)
• Total URL length under 2,048 characters
• Special characters properly URL-encoded
• No malformed encoding (broken % sequences)

Why this matters: Invalid URLs won't load. Overly long URLs may be truncated by browsers, email clients, or platforms.

URL length limits:

• Browsers: 2,048 characters (practical limit)
• Internet Explorer: 2,083 characters (if you still support it)
• Email clients: Variable, but stay under 2,000 to be safe
• Social platforms: Often impose shorter limits (500-1000 chars)

Common mistakes:

X No protocol:
example.com/page?utm_source=email

X Broken encoding:
example.com/page?utm_campaign=50%off

X Unencoded spaces:
example.com/page?utm_campaign=summer sale

X Invalid domain:
https://example .com/page?utm_source=email

Correct format:

OK Valid protocol and domain:
https://example.com/page?utm_source=email&utm_medium=email

OK Properly encoded special chars:
https://example.com/page?utm_campaign=50%25off

OK Clean, valid structure:
https://www.example.com/landing?utm_source=facebook&utm_medium=cpc

Encoding guidelines:

• Don't encode UTM parameter names: Use utm_source, not utm%5Fsource
• Don't encode delimiters: Use ? and & directly
• Do encode special chars in values: 50% -> 50%25, & -> %26
• Most URL builders handle encoding: Use tools rather than manual encoding

5. Parameter Quality

What to check:

• No empty parameter values
• Values are descriptive and meaningful
• Consistent naming taxonomy across campaigns
• Values match GA4 default channel groupings (when applicable)
• No duplicate parameters with different values

Why this matters: Poor parameter quality leads to:

• "Unassigned" traffic in GA4
• Fragmented reporting (same campaign, different names)
• Inability to analyze performance across campaigns
• Confusion when reviewing historical data

Common mistakes:

X Empty values:
utm_source=newsletter&utm_medium=&utm_campaign=jan_sale

X Non-descriptive values:
utm_source=source1&utm_medium=medium1&utm_campaign=campaign1

X Inconsistent naming:
utm_campaign=jan_sale (one URL)
utm_campaign=january_sale (another URL, same campaign)
utm_campaign=JanSale (yet another URL)

X Non-standard medium for channel:
utm_source=google&utm_medium=search (should be cpc/ppc for paid)

Best practices:

OK Descriptive, consistent values:
utm_source=newsletter&utm_medium=email&utm_campaign=jan_sale

OK Aligned with GA4 channels:
utm_source=google&utm_medium=cpc&utm_campaign=brand_search
utm_source=facebook&utm_medium=paid_social&utm_campaign=spring_promo

OK Structured taxonomy:
utm_campaign={season}_{year}_{product}
Example: utm_campaign=spring_2024_running_shoes

GA4 channel grouping guide:

Taxonomy recommendations:

• Document your naming conventions: Create a shared spreadsheet
• Use a controlled vocabulary: Define allowed values for each parameter
• Version your campaigns: Include date/version in campaign names
• Be consistent across channels: Same campaign = same campaign name

If you want to learn more about GA4's default channel groupings, check out our GA4 channel grouping guide.

6. Redirect Chain Testing

What to check:

• URL shorteners preserve query parameters
• Landing page redirects maintain UTM parameters
• Multi-hop redirects pass parameters through each step
• Server-side redirects include [QSA] flag or equivalent
• JavaScript redirects include window.location.search

Why this matters: Redirects are the #1 cause of UTM parameter loss. A single misconfigured redirect can strip all your tracking data.

How to test:

Test 1: URL Shortener

1. Create a shortened URL with full UTM parameters
2. Paste the short URL into a browser
3. Hit Enter and watch the address bar
4. Verify all UTM parameters appear in the final destination URL

Test 2: Landing Page Redirects

1. Navigate to your landing page with UTM parameters
2. Watch the address bar during page load
3. Check if parameters survive any redirects
4. Verify final URL includes all original UTMs

Test 3: Multi-Hop Chain

1. Map out your complete redirect chain
2. Test each hop individually
3. Verify parameters pass through each transition
4. Document any hops that strip parameters

Common redirect issues:

X WordPress Redirection plugin (default settings):
Original: example.com/landing?utm_source=email
After: example.com/new-page (UTMs gone!)

X JavaScript redirect without search params:
window.location.href = '/new-page';

X .htaccess without [QSA] flag:
RewriteRule ^old$ /new [R=301,L]

Correct configurations:

OK WordPress Redirection (enable "Pass query parameters")

OK JavaScript redirect with params:
window.location.href = '/new-page' + window.location.search;

OK .htaccess with [QSA] flag:
RewriteRule ^old$ /new [R=301,L,QSA]

OK URL shorteners with parameter forwarding enabled

Pro tip: Create a test suite of URLs with UTMs and run them through your redirect chain regularly, especially after infrastructure changes.

7. Platform Compatibility Check

What to check:

• Email ESP supports UTM parameters
• Social media platforms don't strip parameters
• URL length fits platform constraints
• No conflicts with platform-specific tracking (fbclid, gclid)
• Landing page CMS preserves query strings

Why this matters: Each platform has quirks that can break tracking:

• Email clients may rewrite URLs
• Social apps may strip parameters during app-to-web transitions
• Platforms may have character limits
• Some platforms add their own tracking parameters

Platform-specific validation:

Email (Mailchimp, Klaviyo, etc.):

• Don't use merge tags in UTM values
• Test click tracking doesn't strip parameters
• Verify across Gmail, Outlook, Apple Mail
• Check Safe Links compatibility

Social (Facebook, Instagram, LinkedIn):

• URL length under platform limits
• Test in-app browser behavior
• Verify UTMs work with platform pixels
• Check app-to-browser transitions

Google Ads:

• Manual UTMs don't conflict with auto-tagging
• ValueTrack parameters placed correctly
• Final URL includes manual UTMs if using both

URL Shorteners:

• Query string preservation enabled
• Custom domains don't add redirects
• Analytics don't interfere with UTMs

Best practices:

• Test on the actual platform: Don't assume desktop behavior = mobile app behavior
• Document platform quirks: Keep notes on what works/doesn't work
• Use platform auto-tagging when available: fbclid, gclid supplement manual UTMs
• Monitor for platform changes: Platforms update frequently; retest periodically

Pillar 2: Cross-Platform Testing

Validation checks structure. Testing verifies tracking actually works.

The Testing Protocol

For every campaign, test in the environments where users will actually click your links.

Email Campaign Testing

Test matrix:

Testing steps:

1. Send test email to yourself across all clients
2. Click the link from each client
3. Check browser address bar for UTM parameters
4. Verify session appears in GA4 Realtime with correct attribution
5. Document any clients that strip or modify parameters

What to watch for:

• Outlook Safe Links: May redirect through Microsoft's proxy
• Apple Mail Privacy Protection: May prefetch links
• Gmail: Generally preserves parameters well
• Link protection services: Corporate email may add additional layers

Example test document:

Campaign: Jan Newsletter
Send Date: 2024-01-15
URL: example.com/offer?utm_source=newsletter&utm_medium=email&utm_campaign=jan_sale

Test Results:
OK Gmail Desktop - Parameters preserved, GA4 tracking works
OK Gmail Mobile - Parameters preserved, GA4 tracking works 
! Outlook Desktop - Safe Links enabled, parameters stripped
OK Outlook Mobile - Parameters preserved (Safe Links not active)
OK Apple Mail Desktop - Parameters preserved
OK Apple Mail Mobile - Parameters preserved, some prefetching

Action: Configure ESP to work with Outlook Safe Links

Social Media Testing

Test matrix:

Testing steps:

1. Post test link on platform (use private/draft if possible)
2. Click from mobile app -> Note if opens in-app browser or external
3. Check if UTMs survive in address bar
4. Click "Open in Safari/Chrome" (if applicable)
5. Verify UTMs survive the app-to-browser transition
6. Check GA4 Realtime for proper attribution

Platform-specific notes:

Facebook/Instagram:

• Generally preserve UTMs well
• fbclid auto-appended (doesn't interfere with UTMs)
• In-app browser usually preserves parameters
• Test app-to-Safari/Chrome transition

LinkedIn:

• Good parameter preservation
• Professional context = desktop testing important
• In-app browser behavior varies by platform version

TikTok:

• Variable behavior across app versions
• Test thoroughly in actual TikTok app
• Consider using TikTok's built-in tracking alongside UTMs

Twitter/X:

• Generally reliable
• t.co shortener preserves parameters
• Test both app and web versions

Paid Search Testing

Test scenarios:

Testing steps:

1. Create test ad with UTMs:

Final URL: example.com/landing?utm_source=google&utm_medium=cpc&utm_campaign=test

2. Preview the ad:

• Use Google Ads preview tool
• Click through from preview
• Verify UTMs in landing page URL

3. Check auto-tagging interaction:

• If auto-tagging enabled: Look for gclid parameter
• Verify manual UTMs still present
• Check GA4 attribution (should use Google Ads data)

4. Test ValueTrack parameters (if using):

Final URL: example.com/landing?utm_source=google&utm_medium=cpc&utm_campaign={campaignid}&utm_content={creative}

• Preview should show actual values replaced
• Verify in GA4 that values are populated

Best practices:

• Use auto-tagging: More reliable than manual UTMs for Google Ads
• Keep manual UTMs: Useful for non-Google reporting platforms
• Don't override: Let auto-tagging take precedence in GA4
• Test before full launch: Preview every ad before activation

Website & Landing Page Testing

Test checklist:

Infrastructure tests:

• Landing page loads with UTM parameters
• No redirects strip parameters
• GA4 tag fires on page load
• Cookie consent doesn't block tracking (or Consent Mode works)
• No JavaScript errors interfere with tracking
• Parameters survive across page navigation (SPA)

Testing steps:

Test 1: Basic tracking

1. Open DevTools (F12) -> Network tab
2. Enable "Preserve log"
3. Navigate to: yoursite.com/page?utm_source=test&utm_medium=test&utm_campaign=test
4. Look for GA4 collect request
5. Verify UTM parameters in request payload

Test 2: Consent management

1. Open incognito window
2. Navigate to URL with UTMs
3. Reject all cookies
4. Check if GA4 fired (should depend on Consent Mode setup)
5. Accept cookies and verify tracking resumes

Test 3: Cross-page preservation (for SPAs)

1. Land on page with UTMs
2. Navigate to another page via internal link
3. Check if campaign attribution persists in GA4 session
4. Verify session source/medium doesn't change

Test 4: Mobile responsiveness

1. Test on actual mobile devices
2. Check URL parameter handling on small screens
3. Verify tracking works in mobile browsers
4. Test orientation changes don't affect tracking

What to look for in DevTools:

Request URL: https://www.google-analytics.com/g/collect?...

Query Parameters:
 v: 2
 tid: G-YOURMEASUREMENTID
 en: page_view
 _p: [random]
 sr: [screen resolution]
 
 # UTM parameters (may be prefixed):
 utm_source: test
 utm_medium: test
 utm_campaign: test
 
 # Or in session parameters:
 _ss: 1
 _fv: 1
 sid: [session id]
 sct: 1
 seg: 1

The 24-Hour Testing Window

Best practice: Test every campaign 24 hours before launch.

Why 24 hours?

• Gives time to fix issues without delaying launch
• Allows testing across time zones if relevant
• Provides buffer for unexpected problems
• Reduces launch day stress

24-hour testing protocol:

T-24 hours: Initial validation

• Run URLs through validation tool
• Fix any structural issues
• Update campaign in platform

T-12 hours: Platform testing

• Test in relevant email clients
• Test on social platforms
• Test paid search previews
• Verify landing page behavior

T-6 hours: Final verification

• Spot-check random URLs
• Verify fixes from earlier tests
• Do one last GA4 Realtime check
• Get final approval from stakeholders

T-0 hours: Launch with confidence

• All testing complete
• Issues documented and resolved
• Monitoring plan in place
• Ready to launch

Pillar 3: Post-Launch Monitoring

Prevention catches most issues. Monitoring catches the rest.

Immediate Monitoring (First 5 Minutes)

As soon as the campaign launches:

Minute 0-1: Initial check

1. Click your campaign link from the actual source
2. Verify landing page loads correctly
3. Check UTMs are in browser address bar

Minute 1-3: GA4 Realtime check

1. Open GA4 -> Reports -> Realtime
2. Look for your session
3. Verify correct source/medium/campaign
4. Check geographic location makes sense

Minute 3-5: Verification

1. Click again from different device
2. Verify tracking still works
3. Check multiple entry points (if applicable)
4. Screenshot Realtime data for records

What you should see in Realtime:

Active users: 1 (or more if others are testing)
Event name: page_view
Event count: 1
Source: [your utm_source]
Medium: [your utm_medium] 
Campaign: [your utm_campaign]
Landing page: [your landing page]

Red flags in first 5 minutes:

• X No session appears
• X Session shows as "Direct / (none)"
• X Source/medium incorrect
• X Campaign name missing or wrong
• X Landing page shows as different URL

If you see red flags: STOP the campaign immediately and investigate.

First Hour Monitoring

What to monitor:

Volume check:

• Are sessions appearing at expected rate?
• Is traffic volume consistent with sends/impressions?
• Any unusual traffic patterns?

Attribution check:

• All sessions showing correct source/medium/campaign?
• No sessions showing as Direct that should be attributed?
• Channel grouping correct in GA4?

Engagement check:

• Bounce rate reasonable?
• Time on page normal?
• Conversions starting to appear?

Sample monitoring checklist:

Campaign: Jan Email Newsletter
Launch: 10:00 AM
Send volume: 50,000 emails

10:05 - Realtime check: 12 sessions, correct attribution OK
10:15 - Realtime check: 89 sessions, all email channel OK
10:30 - Realtime check: 156 sessions, 2 showing as Direct !
10:45 - Investigation: 2 Direct likely mobile app handoff, acceptable OK
11:00 - Volume check: 300 sessions, tracking at ~0.6% CTR OK

Daily Monitoring (First Week)

Day 1 checklist:

• Review Realtime data every few hours
• Check total session volume
• Verify conversion tracking
• Compare to expected performance
• Document any anomalies

Day 2-7 checklist:

• Check once daily
• Review source/medium report
• Verify campaign appears in reports
• Check for "Direct" traffic spikes
• Monitor conversion rate trends

What to look for:

Attribution drift:

Day 1: 95% email channel, 5% Direct
Day 2: 90% email channel, 10% Direct 
Day 3: 85% email channel, 15% Direct

Warning: Attribution drift detected
Possible causes: 
- Email forwards losing UTMs
- Shared links without parameters 
- Mobile app issues

Traffic volume anomalies:

• Sudden drop: Tracking may have broken
• Sudden spike: Could indicate issue (bots?) or viral sharing
• Inconsistent patterns: May indicate intermittent tracking problems

Conversion tracking:

• Are conversions being attributed to campaign?
• Conversion rate in line with expectations?
• Any conversions showing as Direct that should be campaign?

Setting Up Automated Alerts

GA4 Insights & Anomaly Detection:

Create custom insight for UTM tracking:

1. Go to GA4 -> Reports -> Insights
2. Click "Create custom insight"
3. Set up alert conditions:

Alert 1: Direct traffic spike

Condition: Direct traffic increases >30% day-over-day
Why: May indicate UTM parameters being stripped
Action: Investigate immediately

Alert 2: Campaign traffic drop

Condition: Campaign traffic decreases >50% hour-over-hour
Why: Tracking may have broken mid-campaign
Action: Check tracking setup

Alert 3: Unassigned traffic spike

Condition: Unassigned channel traffic increases >20%
Why: UTMs may not match GA4 channel rules
Action: Review UTM taxonomy

Email notification setup:

• Configure email alerts for critical insights
• Include key stakeholders
• Set appropriate thresholds (not too sensitive)
• Test alerts before relying on them

Weekly & Monthly Audits

Weekly audit checklist:

• Review all campaign attribution
• Check for Unassigned traffic patterns
• Verify new campaigns tracking correctly
• Document any tracking issues
• Update tracking documentation

Monthly audit checklist:

• Full taxonomy review (naming consistency)
• Redirect chain testing
• Platform compatibility recheck
• GTM configuration review
• Update validation rules based on learnings

Quarterly deep audit:

• Complete infrastructure review
• Test all platforms and channels
• Review and update documentation
• Training for new team members
• Evaluate new tools and approaches

Platform-Specific Prevention Strategies

Email Marketing Platforms

Mailchimp prevention:

OK Use static values in UTM parameters
X Don't use: utm_campaign=*|MC:SUBJECT|*
OK Do use: utm_campaign=jan_newsletter

OK Enable parameter preservation in click tracking
OK Test merge tags in non-UTM fields only
OK Use Mailchimp's campaign name in utm_campaign consistently

Klaviyo prevention:

OK Configure click tracking to preserve query strings
OK Use Klaviyo's native UTM builder when available
OK Test across email clients before major sends
OK Monitor for ESP updates that might affect tracking

General ESP best practices:

• Always use ESP's native URL builder if available
• Test click tracking configuration
• Verify parameter preservation settings
• Monitor for ESP platform updates
• Document ESP-specific quirks

Social Media Platforms

Facebook/Instagram prevention:

OK Keep URLs under 500 characters for safety
OK Use Meta's auto-tagging (fbclid) alongside manual UTMs
OK Test in actual mobile apps, not just desktop
OK Accept that app-to-web transitions may lose some UTMs
OK Use Facebook pixel for additional attribution data

LinkedIn prevention:

OK Test both mobile and desktop versions
OK Keep UTM values professional and clear
OK Use LinkedIn's Campaign Manager UTM builder
OK Test in-app browser behavior
OK Monitor for LinkedIn platform changes

Twitter/X prevention:

OK t.co shortening preserves parameters (verify periodically)
OK Test both app and web posting
OK Keep total URL length reasonable
OK Use Twitter's analytics alongside GA4

General social media best practices:

• Accept platform limitations (some UTM loss is normal)
• Use platform-specific tracking (pixels, IDs) as backup
• Test in actual apps, not mobile browsers
• Monitor for platform updates
• Document which platforms work reliably

URL Shorteners

Bitly prevention:

OK Ensure "Query parameter forwarding" is enabled
OK Test shortened links before use
OK Use Bitly's analytics alongside GA4
OK Document shortener configuration

Custom domain shorteners:

OK Verify redirect configuration preserves query strings
OK Test multi-hop redirect chains
OK Monitor for DNS/CDN changes
OK Document redirect logic

General shortener best practices:

• Always test before campaign launch
• Verify query string preservation
• Keep shortener configuration documented
• Have backup shortener option
• Monitor for service changes

WordPress & CMS Platforms

WordPress prevention:

OK Configure Redirection plugin: Enable "Pass query parameters"
OK Yoast SEO redirects: Verify parameter preservation
OK .htaccess rules: Always use [QSA] flag
OK Test redirects after plugin updates
OK Document all redirect rules

Shopify prevention:

OK Liquid templates: Preserve {{ request.query_string }}
OK App redirects: Verify query parameter handling
OK Theme changes: Retest tracking after updates
OK Checkout flow: Ensure UTMs persist through checkout

General CMS best practices:

• Test tracking after any CMS updates
• Document all redirect rules
• Verify query parameter preservation
• Test across different page types
• Monitor for theme/plugin conflicts

Creating a Campaign Tracking Runbook

Document your specific setup:

Example Runbook Template

# UTM Tracking Runbook - [Your Company]
 
## Campaign Setup Standards
 
### Required Parameters
- utm_source: [allowed values]
- utm_medium: [allowed values]
- utm_campaign: [naming convention]
 
### Naming Conventions
- Format: {channel}_{quarter}_{initiative}
- Example: email_q1_product_launch
- Always lowercase
- Use underscores, not spaces or hyphens
 
## Validation Process
 
### Pre-Launch Checklist
- [ ] Run through UTM Guard validator
- [ ] Test in relevant email clients (Gmail, Outlook)
- [ ] Verify redirect chain preserves parameters
- [ ] Check GA4 Realtime with test click
- [ ] Get approval from analytics team
 
### Platform-Specific Notes
- Mailchimp: Don't use merge tags in UTMs
- Bitly: Query forwarding enabled OK
- WordPress: Redirection plugin configured OK
- Facebook: fbclid auto-appended (expected)
 
## Testing Protocol
 
### Email Campaigns
1. Send to test list 24 hours before launch
2. Click from Gmail, Outlook, Apple Mail
3. Verify UTMs in browser URL
4. Check GA4 Realtime attribution
5. Document any issues
 
### Social Campaigns
1. Create test post (private/draft)
2. Click in mobile app
3. Verify in-app browser preserves UTMs
4. Test app-to-browser transition
5. Check GA4 Realtime
 
## Monitoring
 
### First Hour
- Check GA4 Realtime every 15 minutes
- Verify source/medium/campaign correct
- Monitor for Direct traffic spikes
 
### First Week
- Daily GA4 report review
- Check for attribution drift
- Monitor conversion tracking
- Document any issues
 
## Issue Response
 
### If UTMs Not Showing
1. Check browser URL - are parameters present?
 - No: Redirect chain issue -> check redirects
 - Yes: GA4 tracking issue -> check GTM
 
2. Check GA4 Realtime
 - No session: GA4 not firing -> check consent, GTM
 - Wrong attribution: Check URL structure
 
3. Emergency contacts:
 - Analytics lead: [name/email]
 - Developer: [name/email]
 - Platform admin: [name/email]
 
## Tools & Resources
 
- UTM Guard validator: https://utmguard.webiq.app/validator
- GA4 Realtime: [direct link]
- GTM Preview: [direct link]
- Bitly dashboard: [link]
- Email ESP: [link]
 
## Update Log
 
- 2024-01-15: Initial runbook created
- 2024-02-01: Added social media testing protocol
- 2024-03-01: Updated email client list

Tools & Automation

Validation Tools

UTM Guard (Recommended):

• Automated URL validation
• Batch processing for large campaigns
• GA4 compatibility checks
• Export validation reports

Google's Campaign URL Builder:

• Simple UTM generation
• Good for one-off URLs
• No validation or testing

Spreadsheet validation:

• Use formulas to check structure
• Good for template-based campaigns
• Requires manual maintenance

Testing Tools

GA4 Realtime Report:

• Free, built-in to GA4
• Real-time session tracking
• Limited to current traffic

GA4 DebugView:

• Detailed event inspection
• Requires debug mode enabled
• Great for troubleshooting

GTM Preview Mode:

• Tag firing verification
• Variable inspection
• Essential for GTM debugging

Browser DevTools:

• Network tab for request inspection
• Console for JavaScript errors
• Free and powerful

Monitoring Tools

GA4 Insights:

• Built-in anomaly detection
• Custom alert creation
• Free with GA4

Third-party monitoring:

• Supermetrics (data export)
• Looker Studio (dashboards)
• Custom scripts (API-based)

Automated reporting:

• Daily campaign summary emails
• Weekly attribution reports
• Monthly audit reports

ROI of Prevention

Time investment:

• Initial setup: 2-4 hours (one-time)
• Per campaign validation: 5-10 minutes
• Per campaign testing: 15-30 minutes
• Total per campaign: 20-40 minutes

Prevented costs:

• Lost attribution data: Priceless (can't be recovered)
• Emergency troubleshooting: 2-4 hours x hourly rate
• Wasted ad spend: $100-$10,000+ per campaign
• Stakeholder confidence: Hard to quantify, critical for career

Example calculation:

Campaign spend: $5,000
Prevention time: 30 minutes
Emergency troubleshooting time: 3 hours

If tracking breaks:
- Lost: All attribution data for the campaign
- Cost: 3 hours troubleshooting x $100/hr = $300
- Risk: Campaign continues with broken tracking
- Impact: Can't optimize, can't prove ROI

Prevention ROI:
- Time invested: 30 minutes x $100/hr = $50
- Data preserved: $5,000 worth of campaign insights
- Peace of mind: Priceless
- ROI: 100:1 minimum

Prevention is always cheaper than troubleshooting.

Summary: Your Prevention Checklist

Before Every Campaign

Validate:

• UTM parameters present and correct
• Query string structure valid (? before #)
• Values formatted properly (lowercase, no spaces)
• URL length reasonable
• Redirect chain tested

Test:

• Relevant email clients
• Social media platforms
• Mobile devices
• Landing page behavior
• GA4 Realtime verification

Document:

• Campaign details recorded
• Platform-specific notes
• Known issues documented
• Testing results saved

First 5 Minutes After Launch

• Click campaign link
• Check GA4 Realtime
• Verify attribution correct
• Screenshot for records
• Monitor for issues

First Week After Launch

• Daily attribution check
• Monitor for drift
• Review conversion data
• Document any issues
• Update runbook if needed

Final Thoughts

Prevention is not perfection. You won't catch every issue. Some platform behaviors are outside your control. App-to-web transitions will sometimes strip parameters. Email clients will occasionally rewrite URLs.

That's okay.

The goal is to catch 90%+ of preventable issues before they cost you data and budget.

The key principles:

1. Validate structure before launch (5 minutes per campaign)
2. Test in real conditions (15 minutes per campaign)
3. Monitor immediately (5 minutes at launch)
4. Document everything (ongoing)

This 25-30 minute investment per campaign prevents hours of troubleshooting and preserves irreplaceable attribution data.

Make prevention a habit, not an afterthought.

Next Steps

• Validate your next campaign now - Free UTM validation tool
• Need to fix broken tracking? - 5-minute troubleshooting guide
• Learn all 7 common issues - Comprehensive reference
• Fix GA4 Unassigned traffic - Channel grouping solutions

UTM Guard helps marketing teams prevent tracking issues before launch. Validate campaign URLs in seconds, catch errors automatically, and ensure accurate attribution in GA4.