Facebook UTM builder that lets Meta fill in the campaign, ad set and ad

Ads Manager substitutes eight placeholders in a destination URL at the moment of the click: {{campaign.name}}, {{campaign.id}}, {{adset.name}}, {{adset.id}}, {{ad.name}}, {{ad.id}}, {{placement}} and {{site_source_name}}. The last one resolves to fb, ig, msg or an, which is how you tell Facebook from Instagram from Messenger from Audience Network in a report. Names give readable reports; ids survive renames. Most teams use the names in the UTMs and, if they run LeadJourney or another attribution tool, add the ids through a separate template.

The recommended set is utm_source={{site_source_name}}, utm_medium=paid-social, utm_campaign={{campaign.name}}, utm_term={{adset.name}} and utm_content={{ad.name}}. Set once, it tags every ad with its own values and needs no per-ad work. The builder loads it by default.

There are two places to put tracking on a Meta ad. The Website URL field holds the full destination, and appending parameters there works but has to be done per ad. The URL parameters field, under Tracking at the ad level, holds only the query string and is appended to whatever destination the ad uses, so one string serves every ad in the campaign, and campaign-level defaults apply it to new ads automatically. Use the second. The builder outputs either: switch to parameters only and it drops the destination and the leading question mark.

One thing the macros cannot fix: utm_medium. There is no macro for it, and the value decides where GA4 files the session. Use paid-social, hyphenated, for every Meta campaign, and never "Facebook Ads" or "social", which land in Unassigned and Organic Social respectively.

The URL tells your analytics where the visitor came from. It does not tell Meta that the visitor converted. That message goes back through the pixel, and since iOS 14 the pixel fails to deliver it for 30 to 50 percent of real conversions: Safari cookie limits, the App Tracking Transparency prompt, declined consent banners and cross-device journeys all break the connection. Ads Manager under-reports, the cost per lead reads too high, and Advantage+ learns from the visible half.

The fix is server side. Capture the fbclid Meta appends to every click, store it first-party, match the lead to it when the form arrives (on any device), and send the conversion back through the Conversions API with the CRM stage attached. The UTMs you build here are the readable half of that record; the click-ID template the builder can append is the machine-readable half, and LeadJourney does the rest.