On this page
Why Meta ads need UTM tags
Meta adds its own click ID, fbclid, to ad links. GA4 does not use it to decide the channel. Without UTM tags, GA4 only sees that the visitor came from Facebook:
The source is a social network or the medium is social. The right channel would be Paid Social.
So a paid ad shows up in the same channel as your own posts, and you cannot separate the results of your advertising. Some traffic from the in-app browser does not report its source at all, and it shows up in Direct.
The right values
| Parameter | Value | Note |
|---|---|---|
utm_source |
facebook or instagram |
GA4 knows both as social platforms |
utm_medium |
paid-social |
Tells GA4 the traffic is paid |
utm_campaign |
spring_sale_2026 |
The same name as in your other channels |
utm_content |
video_a |
The ad version, if you want to compare ads |
With these values, the traffic lands in Paid Social:
The source is a social network and the medium is paid.
The medium cpc also works, because GA4 treats it as paid. Still, pick one and stick with it, so the same traffic does not split into two rows.
Why the source must not be meta
The company is called Meta, but GA4's list of social sources has the names of the platforms: facebook, instagram and their abbreviations. The source meta is not on the list, so the ad lands in Paid Other:
The medium is paid, but GA4 does not recognize the source as a search engine, social network, video site or shopping site. The right channel would be Paid Social.
In your reports, the traffic then sits among other unrecognized paid channels and does not count as social advertising.
Facebook or Instagram?
The same ad often runs on both platforms. You have two options:
- One fixed source. Use the source
facebookin all Meta ads. This is the simplest way, and the channel is always right. - Source by placement. The dynamic parameter
{{site_source_name}}sets the source tofb,ig,msgorandepending on where the ad was clicked. GA4 knowsfbandig, but traffic from Messenger (msg) and Audience Network (an) lands in Paid Other.
If you want to tell the platforms apart, you can keep facebook as the source and store the placement in the content: utm_content={{placement}}.
Dynamic parameters
You do not have to write the tags into every ad. In Ads Manager, the ad settings have a field called URL parameters (in the Tracking section). The text you write there is appended to the ad's address, and Meta replaces the placeholders in curly braces with the ad's details:
utm_source=facebook&utm_medium=paid-social&utm_campaign={{campaign.name}}&utm_content={{ad.name}}
The most used dynamic parameters:
| Parameter | What Meta writes |
|---|---|
{{campaign.name}} |
Campaign name |
{{adset.name}} |
Ad set name |
{{ad.name}} |
Ad name |
{{placement}} |
Placement, for example feed or story |
{{site_source_name}} |
Platform: fb, ig, msg or an |
A dynamic parameter copies the name as it is. If your campaign is called “Spring Sale 2026” in Meta, that exact spelling, spaces included, ends up in GA4. Name your campaigns in Meta with the same rules as your UTM values (spring_sale_2026), or write the campaign into the tag by hand.
Your own posts
Tag your own social posts too if you want to separate them from other Facebook traffic. Use the medium social, so the posts show up in Organic Social and do not get mixed up with your ads:
The source is a social network or the medium is social.
Checklist
- The source is
facebookorinstagram, notmeta. - The medium is
paid-socialin all ads andsocialin your own posts. - The campaign name follows the same pattern as in your other channels.
- If you use dynamic parameters, your campaigns and ads are named cleanly in Meta.
Try it yourself
Open the generator with this guide's example values.
Kanavoi is a Finnish UTM tool for teams. It keeps naming consistent and shows the GA4 channel before a link is shared.