Where do I add UTM parameters in Meta Ads Manager?

In Meta Ads Manager, add UTM parameters in the 'URL Parameters' field at the ad level - not in the Destination URL field directly. The URL Parameters field is specifically designed for tracking parameters and dynamic tokens. It appends your parameters to the landing page URL automatically. Using the URL Parameters field (rather than manually editing the destination URL) preserves compatibility with Meta's click tracking and dynamic URLs.

What are Meta dynamic URL parameters?

Meta dynamic URL parameters are special tokens wrapped in double curly braces ({{ }}) that Meta Ads automatically replaces with real campaign data when an ad is clicked. For example, {{campaign.name}} is replaced with your actual campaign name, {{ad.id}} with the numeric ad ID, and {{site_source_name}} with 'fb', 'ig', 'msg', or 'an' depending on where the ad was shown. They enable ad-level attribution in GA4 without creating separate URLs for every variation.

Facebook Ads UTM Builder & Meta URL Generator

Destination URL *

Paste your destination URL

⚠️ Please enter a valid URL (e.g. https://domain.com/path)

Quick fill:

Campaign Source * utm_source

Source is required for GA4 attribution.

Campaign Medium * utm_medium

Medium is required (e.g. cpc, email, social).

Campaign Name * utm_campaign

Campaign Term utm_term (optional)

Campaign Content utm_content (optional)

Campaign ID utm_id (GA4 campaign identifier)

Dynamic & Custom Query Parameters

⚙️ Sanitization & Formatting Options ▼

Auto Lowercase (Recommended)

Space Replacement:

Auto Prepend https:// Strip Existing UTMs

LIVE PREVIEW

Generated Campaign URL

Real-time normalized URL with syntax highlighting & validation.

Ready

Your tracked URL will appear here in real-time...

0 chars Standard limit < 2048 chars

GA4 Compatibility 100 / 100

Want to verify in GA4? How to check in GA4 →

DISTRIBUTION

Mobile QR Code

High-resolution vector SVG and PNG for print & outdoor media.

Preview (Blurred)

Instant high-res SVG & PNG

Meta Ads Dynamic URL Parameters - Complete Reference

Meta dynamic parameters use double curly braces {{ }} syntax. They are evaluated when the ad is served, replacing the token with real campaign data. Unlike Google's ValueTrack which uses single braces, Meta uses a different notation that is not URL-encoded at ad creation time.

Dynamic Token	Replaced With	Best UTM Field
`{{campaign.id}}`	Numeric Campaign ID	utm_id
`{{campaign.name}}`	Campaign name as set in Ads Manager	utm_campaign
`{{adset.id}}`	Numeric Ad Set ID	utm_content
`{{adset.name}}`	Ad Set name	utm_content
`{{ad.id}}`	Numeric Ad ID	utm_content
`{{ad.name}}`	Ad name as set in Ads Manager	utm_content
`{{site_source_name}}`	`fb` (Facebook), `ig` (Instagram), `msg` (Messenger), `an` (Audience Network)	utm_source or utm_content
`{{placement}}`	Specific placement type (e.g. feed, story, reels)	utm_content

Where to Add UTM Parameters in Meta Ads Manager

⚠️ Critical: Use the URL Parameters Field, NOT the Destination URL

A very common and costly mistake is adding UTM parameters directly to the Final URL / Destination URL field in Meta Ads Manager. For campaigns with multiple placements or dynamic creative, Meta may override or strip parameters added to the Destination URL. Always add UTM parameters using the dedicated URL Parameters field at the ad level.

Step-by-Step: Adding UTMs via URL Parameters Field

In Meta Ads Manager, navigate to the Ad level (not campaign or ad set level)

Scroll to the Destination section and look for URL Parameters

Click "Build a URL Parameter" or paste your tracking string directly

Enter only the query string - do not include the ? or the base URL:

utm_source=facebook&utm_medium=paid_social&utm_campaign={{campaign.name}}&utm_content={{adset.name}}_{{ad.name}}&utm_id={{campaign.id}}

Meta will preview the combined URL - verify the structure looks correct

Run the Meta pixel helper Chrome extension to confirm UTMs are being sent to your site after publishing

iOS 14 Impact on Meta UTM Attribution

Apple's App Tracking Transparency (ATT) framework introduced with iOS 14 significantly reduced Meta's ability to track users across apps and websites. This directly affects attribution data visible in Meta Ads Manager. UTM parameters remain unaffected - they travel with the URL and are captured server-side by your analytics platform regardless of device privacy settings.

Attribution Data	Impact of iOS 14 ATT	UTM Parameters Affected?
Meta Ads Manager reporting	Reduced - modeled conversions fill gaps	No - UTMs still passed in URLs
GA4 Traffic Acquisition (UTM-based)	Minimal - UTMs are URL parameters, not cookies	Not impacted
Meta Pixel events	Limited on iOS 14+ devices without ATT consent	N/A - separate tracking system
View-through conversions	Severely limited on iOS 14+	N/A - UTMs are click-based only

💡 UTMs + Conversions API = Full Attribution

Combine manual UTM tracking with Meta's Conversions API (CAPI) for a dual-track attribution setup. UTMs provide click-level data in GA4. CAPI provides server-side event data directly to Meta. Together, they give you the most complete picture of ad performance even in a post-iOS 14 world.

Frequently Asked Questions - Meta & Facebook Ads UTM Tracking

Why is my Facebook traffic showing as Direct or Organic Social in GA4?

This happens when UTM parameters are missing from your ad URLs, Meta's in-app browser strips UTM strings, or users land on your page from a saved or shared link without UTMs. Always add UTM parameters to every Meta ad creative. For the in-app browser issue, use the Meta Pixel + UTM combination and consider enabling CAPI for server-side event capture.

Should utm_source be "facebook" or "meta"?

Use facebook as the utm_source value. GA4's built-in channel grouping rules recognize facebook as a social network source. "meta" is not in GA4's recognized source list and would generate an "Unassigned" channel grouping. For Instagram-placed ads, many teams use instagram as the source, which is also recognized by GA4.

What utm_medium value should I use for Meta paid social campaigns?

Use paid_social. This is in GA4's Default Channel Grouping regex for the Paid Social channel. Avoid cpc for social ads - in GA4, source=facebook&medium=cpc does not reliably map to Paid Social and may appear as Paid Search or Unassigned depending on the GA4 property configuration.