What Meta adds to your Facebook ad URLs on its own
Meta's help center says that since January 1, 2024, some URL parameters may be added to your ad traffic automatically. The list covers a campaign source of Facebook or Instagram, a campaign medium of paid, and the ad, ad set and campaign IDs.
Meta also passes its own click ID. Its developer docs describe fbclid as a Meta-generated parameter that arrives in the URL of the page request. Meta uses it for its own measurement. It does not give your analytics a campaign name.
So open a live test click before you add anything and read the full URL. If Meta's values are already there, decide whether you keep them or replace them. Google's campaign help says parameter values are case sensitive, so Facebook and facebook show up as two source rows even though they are the same traffic.
Where the URL parameters field sits in Ads Manager
The field lives at the ad level. Work through the ad steps until you reach Tracking, then type into URL parameters or click Build a URL parameter. Meta appends whatever is in that field to your Website URL.
The field wins when keys clash. In Meta's own example, utm_source=1 in the Website URL and utm_source=2 in the field leaves only utm_source=2 in the final URL. Meta also asks you never to leave a value empty, so remove a key rather than send utm_content= with nothing after it.
Parameters on a boosted post only apply to clicks on the ad. Someone who sees the same post organically and taps the link brings no ad tags with them.
Dynamic parameters and the UTM slot each one fits
Meta swaps double-brace placeholders for real values when the ad is delivered. These come from its specification page:
Name-based values freeze at first publish. Rename the campaign later and the URL keeps the old name. Meta also warns that editing URL parameters after launch may put the ad set back into the learning phase. Settle on names before you publish.
| Placeholder | What Meta fills in | Good place for it |
|---|---|---|
{{campaign.name}} | Campaign name at first publish | utm_campaign |
{{adset.name}} | Ad set name at first publish | utm_term |
{{ad.name}} | Ad name at first publish | utm_content |
{{placement}} | Placement, such as facebook_feed | A custom key |
{{site_source_name}} | fb, ig, msg, an or th | A custom key, not utm_source |
Which GA4 channel your Facebook tags reach
GA4's Paid Social definition needs two things. The source must be on Google's list of social sites, and the medium must match ^(.*cp.*|ppc|retargeting|paid.*)$. facebook is on that list, so utm_medium=paid_social or paid meets Paid Social. Organic posts tagged utm_medium=social meet Organic Social.
The last row of the table matters here. Of Meta's site source names, only fb and ig are on Google's social list. Paid clicks from Messenger, Audience Network or Threads tagged as msg, an or th miss Paid Social and only meet Paid Other. Keep utm_source=facebook fixed and send the site source to its own key.
Our builder handles the static part. It accepts letters, numbers, hyphens, underscores and periods, so it flags braces. Build the fixed tags there and paste the placeholders into Meta's field by hand. Use your real landing page as the Website URL, not a short link. TrimLink's redirect sends visitors to the stored destination and does not pass on parameters added to the short link, so Meta's placeholders and fbclid would stop there. Short links suit organic posts. UTM and campaign reports in TrimLink analytics are on Pro and above.
https://example.com/spring-sale?utm_source=facebook&utm_medium=paid_social&utm_campaign={{campaign.name}}&utm_content={{ad.name}}&fb_site={{site_source_name}}Sources (checked November 2026)
- Meta Business Help: Specifications for dynamic URL parameters
- Meta Business Help: Add URL parameters to your Meta ads
- Meta for Developers: fbp and fbc parameters
- Google Analytics Help: [GA4] Default channel group
- Google: GA4 default channel group sources and categories (PDF)
- Google Analytics Help: [GA4] URL builders, collect campaign data