Choose the outcome before making the link
Decide what you want to learn: which social posts bring people to an article, which versions lead to newsletter signups, or whether a tutorial reaches interested readers. Keep website behavior separate from platform reach. An impression is not a click, and a click is not necessarily a measured website session.
UTM parameters label traffic; they do not install analytics. Confirm that your site has a working GA4 web data stream and that the action you care about is measured correctly. If a newsletter signup is the goal, verify that the signup event fires on a completed signup rather than just a button press.
Pick a naming convention you can keep
Google documents source, medium, campaign, and content parameters for custom campaign URLs. Values are case-sensitive, so 'Bluesky' and 'bluesky' can fragment your reporting. A lowercase convention is an easy way to keep a small publishing operation consistent.
| Parameter | Example | Purpose |
|---|---|---|
| utm_source | bluesky | The source sending the visit. |
| utm_medium | social | The marketing medium. |
| utm_campaign | desk_reset | The shared campaign or idea. |
| utm_content | checklist_a | The creative version or placement. |
Build and test one complete campaign link
Here is an illustrative URL using an example domain: https://example.com/desk-reset?utm_source=bluesky&utm_medium=social&utm_campaign=desk_reset&utm_content=checklist_a
For the LinkedIn version, change utm_source to linkedin and keep the campaign name desk_reset. If the creative is different, change utm_content too. This keeps one campaign grouped together while letting you compare its sources and versions. Use a URL builder when values contain spaces or punctuation so the query is encoded correctly.
Open the completed link on a phone and a desktop. Confirm it reaches the intended page and that any redirects preserve the campaign values. Then verify the visit in your analytics setup. Do not put personal information such as a reader's name or email address in campaign tags.
Read the session-level acquisition results
In GA4, use the Traffic acquisition report and compare Session source / medium and Session campaign. Report navigation can vary with your property configuration; the important distinction is to use session acquisition dimensions when asking where these visits came from. User acquisition answers a different question about how users were first acquired.
Use the relevant manual ad content dimension when examining utm_content variants. Google notes that campaign parameters appear in acquisition dimensions rather than in the Landing page + query string dimension. Do not conclude tagging failed just because you cannot see the tags in a landing-page report.
'Social referral traffic' here means visits arriving from social platforms in ordinary language. It does not mean every such visit belongs in GA4's Referral channel. Use your source and campaign dimensions to investigate rather than relying only on a channel label.
Keep a small weekly review sheet
Record the campaign, source, creative, sessions, sessions with the chosen outcome, and one follow-up decision. If you calculate a rate, define the numerator and denominator explicitly. For example, 'sessions with a signup divided by sessions' is not the same as 'signup events divided by users.' Use a report or exploration that can actually provide the selected metric.
Start with one question: did the checklist or the demonstration bring more relevant visits? Keep the destination page and campaign stable where practical. A small observational comparison can suggest your next experiment; it does not prove a general causal advantage for a format or platform.
When clicks and sessions do not match
First inspect your own setup. Check capitalization, missing tags, redirects, consent configuration, and whether the page actually loads with working analytics. Browser behavior and measurement limits can also affect what gets recorded. Do not assign every discrepancy to bots or to a platform without investigating.
Keep a consistent convention for the next campaign and write down any tracking changes. That gives future comparisons context. Ferryman can help with your publishing workflow; the UTM and GA4 setup described here is a separate website measurement process, not a claim that Ferryman automatically adds tags or provides GA4 attribution.
FROM GUIDE TO WORKFLOW
Explore this workflow in Ferryman
Cross-platform engagement analytics
Review supported destination engagement in Ferryman alongside your website analytics. Social views and likes are different from GA4 sessions and conversions.
Sources & further reading
Written by Ferryman. Sources checked Oct 16, 2026. Platform rules can change; consult the linked documentation for current requirements.