Publer With Causality Engine: Check Where the UTM Tags Land

The short answer: Publer will tag every link you post with one switch, but the values it starts with decide which GA4 row the visits fall into. Publer, the scheduler priced per social account, fills in 5 UTM keys by default once Google Analytics is turned on under URL Settings (UTM article), and its own reports stop at link clicks counted by each network. Check that the tags land under Organic Social, then export GA4's Attribution paths report and open the free first finding on Causality Engine's start page. Causality Engine is a causal attribution tool that reads that one file.

Disclosure: I founded Causality Engine and own it, and this page recommends it. Every claim about it links to Causality Engine's own pages.

Three checks, cheapest first:

1. Clicks minus sessions. For example, 1,840 link clicks in Post Insights against 1,190 tagged sessions in GA4 means 1,840 - 1,190 = 650 clicks that never became a recorded visit. A gap is normal; its size tells you how much the click column flatters.
2. The toggle you may already have. Open Social Accounts, pick an account, then URL Settings. If Google Analytics is on, the keys and values sit right there.
3. The row they land in. In GA4's Traffic acquisition report, filter on the campaign value Publer writes and see which channel it shows.

Publer and the read: the facts with their pages

The URL Settings tab, and its starting values

The UTM article gives the steps: Social Accounts, choose an account, URL Settings, switch Google Analytics on. Five keys appear: utm_source, utm_medium, utm_campaign, utm_term and utm_content, and both keys and values can be edited. The setting lives on each account, so a brand with six connected profiles has six tabs to check.

The screenshot in that article shows what a Facebook page starts with: utm_source fb_page, utm_medium "Facebook Page", utm_campaign publer. Set those against Google's default channel group. Organic Social needs the source to match Google's list of social sites, or the medium to be social, social-network, social-media, sm, social network or social media. "Facebook Page" is not one of those mediums. The source list Google links from that page includes facebook and fb, and fb_page does not appear in it. Whether GA4 still files these visits as Organic Social is something to see on a test click, not to assume. Google's rules end in Unassigned when nothing matches, and Causality Engine's pricing page for agents says it flags Unassigned traffic with advice to fix tagging first.

The quickest fix is in the same tab: set utm_medium to social on every account, and give the source a plain network name such as facebook or instagram. Lowercase keeps the rows from splitting in reports, even though Google's channel rules are not case sensitive.

Two notes on the shorteners. The Bitly setup article offers "shorten any link" or "shorten only link posts", and under the second a link in a video caption stays long. Shortening happens after the post is scheduled, so the preview never shows it. A short link hides the tags from the reader, not from GA4, provided the shortener forwards the full tagged address.

What Publer counts as a result

Publer has no purchase or revenue figure. The analytics overview says the metrics come from each network's official API, pulled twice a day, with Sync Insights to refresh by hand. Post Insights lists reach, reactions, comments, shares, video views and link clicks per post (account analytics). The automatic refresh covers posts from the last 7 days, and a manual sync reaches back three years (refresh article).

Link clicks, then, are the network's count of taps on the link. With Linkie, Publer's link-in-bio page, two figures appear, Linkie clicks and link clicks, and the Linkie insights article warns they are not the same metric. Neither one reaches the checkout.

A worked example from tagged clicks to booked orders

For example, with figures made up for illustration and not drawn from any store: in October a homeware shop posts 64 link posts through Publer. Post Insights shows 1,840 link clicks. GA4 records 1,190 sessions carrying utm_campaign=publer, which after a medium fix sit under Organic Social, and gives that channel 23 last-click purchases. The shop booked 512 orders. Meta's dashboard claims 268 purchases and Google Ads 241.

The paid claims plus social's last click: 268 + 241 + 23 = 532, which is 532 - 512 = 20 more than the shop sold, with email, search and Direct still to come. A conversion rate from Publer's clicks would be 23 ÷ 1,840 = 1.25%, from GA4's sessions 23 ÷ 1,190 = 1.93%. Neither says whether those 23 buyers needed the posts.

The read answers that per channel. Its how-it-works page describes Direct being split back to the channels that sent those buyers, each channel's caused share shown next to last-click from the same file, a data-health score from 0 to 100 and a next step tested in one region first. It sees Organic Social as one channel: Publer posts, posts made in the native apps and anyone else's shares of your link all sit together. Which post did best stays a Post Insights question.

Free first: a by-hand on and off test

Publer's posting schedules make an alternating test simple to run. For four weeks, post your product links in weeks one and three, and only link-free posts in weeks two and four, keeping volume the same. Then compare orders per week in the store's own export. It is by hand, and it has limits: a sale, a payday or an ad push in one week will swamp the difference. For a shop with steady weeks it gives a rough answer to whether link posts move orders at all, and it costs nothing.

For the wider question, social against ads, search and email, take the Attribution paths export to the start page, where the first finding is free and computed in the browser. Causality Engine, which I founded, charges €99 once for the full read, with a refund inside 30 days (pricing, checked on 11 November 2026).

Limits on both sides

The two products do not connect: no app, no API, no shared login. Causality Engine reads whatever channels a GA4 export holds (integrations), so Publer appears only through the tags its toggle writes.

The read asks for 12 months or more of GA4 history, and a channel under 1% of credit on both methods is called too small to act on (how it works). Organic social on a small account often sits there. Publer keeps the parts the read never touches: scheduling, CSV uploads, recycling and the per-post numbers.

Publer's starting value for utm_campaign is publer, so every visit the toggle tags carries the vendor's name into your analytics, the report a renewal is judged by; whether the medium beside it matches Google's social rules is left to you.

See also

• Publer: accounts, plans and the MCP server
• How to use Publer: a month of posts from one CSV file
• Publer on the marketplace: Publer's affiliate program terms
• Causality Engine: what the read does and costs
• How to use Causality Engine: export, read, test in one region
• Causality Engine on the marketplace: its affiliate program terms
• Publer vs Metricool: per-account pricing against ads reporting
• How to find what Direct traffic is hiding: the Direct row explained

FAQ

Do Publer and Causality Engine share data?

They do not. Causality Engine works from a GA4 file you download, and Publer's part in it is the UTM tags on your links, nothing more (integrations).

Should utm_campaign stay as publer?

My recommendation: replace it with the campaign or product name, since the medium and source already say where the visit came from. The value is editable in URL Settings (UTM article).

Do shortened links break the tags?

Not by design. Publer shortens after scheduling through the shortener you connect (Bitly setup article). Click one live link and read the address bar to confirm the tags arrive.