Hootsuite With Causality Engine: Test the Revenue per Post

The short answer: Hootsuite's revenue per post is Google Analytics data wearing Hootsuite's labels. Hootsuite, the per-seat social suite, promises on its ROI page that you can "see how much revenue each post generated", and its help centre explains how: connect Google Analytics to Advanced Analytics, tag every link, and include "a unique post ID for proper traffic attribution" (Connect a Google Analytics account). Each post's revenue is therefore the revenue GA4 tied to a session carrying that post's tag. That figure answers which post got the last tagged click. It cannot say which post caused a sale. Causality Engine, which reads the store's GA4 export and estimates what each channel caused, gives a free first finding at app.causalityengine.ai/start.

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

Before a top post becomes next quarter's template:

1. Add up the posts. For example, if Impact content credits 30 posts with €475 each on average, that is 30 x 475 = €14,250 for the quarter. Set it against the store's quarterly revenue before reading any single post as a winner.
2. Check the preset everyone already uses. An organization can hold a default preset that applies tracking and shortening to every post automatically (Shorten and track links). Its values decide which GA4 channel the visits join.
3. Look for the post ID. Without a unique ID per post, GA4 cannot split the traffic per post, and Advanced Analytics has nothing post-level to show.

The facts, sourced

How Hootsuite credits a post

Hootsuite does not run its own attribution model, on the pages read today. The Google Analytics article, updated 5 November 2026, says Google Analytics tracks the journey from a click on a post or ad to a visit and a conversion, and that Hootsuite shows the results in five places: Advertising performance, Impact content, ROI analysis, Content comparison and Reports. It asks you to set up ecommerce tracking if you sell online. On connection it backfills GA4 data for one month up to one year, depending on volume.

So the rule is GA4's, filtered by Hootsuite's tags. Two things follow. A sale after someone saw a post and later typed the shop's address is in GA4's Direct row, not in any post's revenue. And the same sale cannot be in two posts, since only one tagged session carried it.

The ROI page also offers to track "total ad spend" and revenue by network. Ad results shown beside organic ones come from a separate source, so keep them in a separate column before adding anything up.

Tags, presets and the channel they produce

In Perch, paste a link, select Add tracking, then a preset or Customize (Shorten and track links). Under Tracking, Custom, each parameter gets a name and a value, up to 100 per link. Paid plans can pick a dynamic type: Social Network fills in X or Facebook, Social Profile fills in the profile's name, and Post ID fills in a unique ID per post per network. The article's own example link carries utm_source=facebook and a campaign, no medium.

Google's default channel group handles that well. Organic Social needs either a source on Google's social list or a medium such as social or sm. Google's downloadable source list includes facebook, instagram and hootsuite itself. The risk is a preset with a medium of cpc or paid on organic posts: Paid Social is checked first, so organic visits would join the ads. A source outside the list with an unlisted medium falls to Unassigned.

One more caution from Google: its (direct) / (none) page says redirects and shorteners such as bit.ly can strip referral details. Open a live Ow.ly link once and confirm the tags arrive.

Worked example: a quarter of posts beside two ad dashboards

For example, using figures invented to illustrate the arithmetic, not any store's: a fashion label's quarter brings €176,900 of net revenue. Impact content credits its organic posts with €14,250. Meta claims €96,400, Google Ads €88,700. GA4's Organic Social row, which includes untagged traffic from social sites, shows €17,830; Direct holds €31,060.

Add what the tools credit: 14,250 + 96,400 + 88,700 = €199,350, which is 199,350 - 176,900 = €22,450 above what the store booked. Hootsuite's share of that is not the inflated part: it is a last-click slice, smaller than GA4's own Organic Social row by 17,830 - 14,250 = €3,580. The overshoot comes from the ad platforms. The part nobody claims is Direct's €31,060.

A causal read works on that file. Its how-it-works page describes splitting Direct back to the channels that sent those buyers, separating what each channel caused from what it only touched, and printing a data-health score and a next step to test in one region first. Organic Social is one line in it. Which post did the work stays a Hootsuite question; whether organic social as a whole deserves more of the team's week is the read's. If the two disagree, move effort on one market for 14 days before the content calendar changes.

A free check, post ID by post ID

Hootsuite's dynamic Post ID makes a by-hand check possible. Set the default preset to put Post ID in utm_content, which Google's URL builder page describes as the parameter for telling creatives apart. After a month, build a GA4 exploration of Organic Social purchases by that content value and set it beside Impact content. Matching totals confirm the plumbing. A gap means some posts went out without the preset.

Then the causal question, still free and by hand: choose one social profile, and for two of four weeks post with no store links at all. Compare store orders in link weeks and link-free weeks. A small test, noisy, and enough to tell whether links on that profile sell anything.

For the whole channel mix, export GA4's Attribution paths report (export guide) and load it on the start page. The first finding is free and computed in the browser.

What the pairing leaves out

The two products share nothing: no app, no token, no feed. Causality Engine's integrations page says it measures every channel visible in GA4 data, including organic, and Hootsuite appears there only as the visits its tags labelled.

The read asks for 12 months or more of GA4 data (how it works), and the key events GA4 keeps, purchase first (one-off read). It calls a channel under 1% of credit on both methods too small to act on, and the homepage says it declines when spend is too small for a signal. It does nothing Perch, Nest or Lumen do.

Revenue per post appears only for customers with Advanced Analytics, and the page that advertises it sells that same upgrade, so the figure offered as proof that the upgrade pays is produced by the upgrade. Check the plumbing above before that figure decides a renewal.

Causality Engine, which I founded, sells one full read for €99, excluding VAT, refundable within 30 days, and Pro at €299 a month (pricing, checked on 11 November 2026). The start page takes the export.

See also

• Hootsuite: Perch, Nest, Lumen and the seat price
• How to use Hootsuite: the job the suite is built for
• Hootsuite on the marketplace: Hootsuite's affiliate program terms
• Causality Engine: what a causal read returns
• How to use Causality Engine: export, read, test one region
• Causality Engine on the marketplace: the read's affiliate terms
• Hootsuite vs Sprout Social: two enterprise social suites side by side
• Blended ROAS calculator: revenue over all spend, your inputs

FAQ

Can Hootsuite Advanced Analytics feed Causality Engine?

No. There is no connection between them. The read works from a GA4 export alone, and the Organic Social visits Hootsuite tagged are already in that file (integrations).

Why does a post show no revenue when sales came in that day?

Revenue reaches a post only through a tagged session with its post ID. A buyer who saw the post and came back by typing the address lands under Direct, per Google's (direct) / (none) page.

Which utm_source should a Hootsuite preset use?

The network's name works with GA4's rules: facebook, instagram and others are on Google's social list, as is hootsuite. Keep the medium social or leave it out for organic posts (default channel group).