Planable With Causality Engine: Approve the Link, Then Read It

The short answer: Planable is where a post gets signed off, which makes it the cheapest place to catch an untagged link before it ships. Planable, the approval-first social planner priced per workspace, neither adds UTM tags nor shortens links: its help centre says "Planable does not support any link shorteners integrations" (link shortener article), and a search of its help centre for UTM returns nothing. Its Analytics add-on, $14 per workspace a month (pricing file, checked on 11 November 2026), reports clicks, spend and cost per click as the platforms count them, and no orders. Put the tagging rule into the approval step, let GA4 record the visits, then run the free first finding at app.causalityengine.ai/start to see what Causality Engine, which reads GA4's Attribution paths export, makes of social against your other channels.

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 the next client report:

1. Divide spend by sales, not by clicks. For example, €1,960 of Meta spend over 1,570 paid clicks is 1,960 ÷ 1,570 = €1.25 per click. Over 44 orders GA4 gives Paid Social on last click it is 1,960 ÷ 44 = €44.55 per order. Only the second number touches the store.
2. Use the reviewer you already have. On Pro, Required approval blocks scheduling until an approver signs off (approvals article). Make "link carries utm_medium=social" part of what that approver checks.
3. Watch the right GA4 row afterwards. Organic Social, in the Traffic acquisition report, is where tagged organic posts should appear.

Planable next to the read

What the Analytics add-on counts

Planable Analytics reads each platform's own numbers. The Facebook analytics article lists engagement, post reach, views, clicks ("the number of clicks your post has received"), reactions, comments and shares, page engagement rate, followers and page views. Connect a Meta ad account and an Ad spend card joins them, with CPM, CPC and CTR. Spend comes from Meta's Ads Insights, a separate source from page insights, which carry no cost at all.

The Planable Analytics article sorts results into three kinds: organic posts, boosted posts with an organic half and a paid half, and paid ads that never appeared on the page. The split shows in the single-channel view only; across channels the numbers stay blended. Custom reports add Google Business Profile's website clicks, calls, bookings and directions (reports article).

What none of these articles lists is a purchase, a conversion or revenue. Planable's result is reach and clicks, measured on the platform. That makes this a partial fit: the tool shapes the traffic that reaches a store, through the links its users approve, and reports nothing about what the store sold.

Putting the tag into the approval step

Since Planable writes no tags, every link carries exactly what the author pasted. Google files a visit under Organic Social when the source matches its list of social sites or the medium is social, social-network, social-media, sm, social network or social media (default channel group). An untagged click from a social app often brings no referrer, and Google's page on (direct) / (none) names missing UTM parameters as one reason a visit is filed as Direct.

Build the tagged address in Google's own URL builder or any other, then let the workflow enforce it:

• Choose Required, not Optional. Optional lets anyone publish without a sign-off; Required, on Pro and Enterprise, does not (approvals article).
• Write the rule where approvers read it. The campaign description field in Planable's Campaigns holds the brief; put the agreed source, medium and campaign values there.
• Expect long links. With no shortener inside Planable, a tagged URL shows in full in the caption. To keep a caption tidy, shorten the link outside Planable before pasting it, then check that the short link forwards the tags.

A worked example on one client workspace

For example, with numbers chosen to show the sums and taken from no client or shop: in one month a client's Facebook page shows, in Planable's single-channel view, 1,180 organic clicks and 1,570 paid clicks on €1,960 of spend. GA4 records 610 Organic Social sessions and 1,240 Paid Social sessions, and gives Organic Social 9 last-click orders and Paid Social 44. The client's shop booked 380 orders. Meta Ads Manager claims 97 purchases; Google Ads claims 214; the email tool's own report claims 102.

Claims first: 97 + 214 + 102 = 413, which is 413 - 380 = 33 more orders than the shop booked, before organic social has claimed any. Then the funnel: 1,180 + 1,570 = 2,750 clicks in Planable against 610 + 1,240 = 1,850 GA4 sessions, so 2,750 - 1,850 = 900 clicks never became a recorded visit.

The read puts a third view beside those. As its how-it-works page describes, it splits Direct back to the channels that sent those buyers, shows each channel's caused share next to a last-click rebuild of the same file, and gives a data-health score from 0 to 100 and a next step with a one-region test. It works on channels. Which approved post or which boosted half did the work is beyond it.

If the read and Meta's 97 sit far apart, change nothing on the strength of it. Test the budget in one region first, as the read itself recommends.

The free check: approve a month with no links

Planable's calendar and approval flow make a clean by-hand test. For one client, plan two comparable fortnights: in the first, product posts carry tagged links; in the second, the same kind of posts go out with no link, approved under the same Required workflow. Compare orders per fortnight in the shop's own export. It is rough, and a sale or an ad change inside either window spoils it. On a steady account it shows whether the linked posts sell or only collect clicks, and it costs nothing.

When the client asks how social compares with search and email, take the Attribution paths export to the start page: the first finding is free and computed in the browser. Causality Engine, which I founded, charges €99 once for the full read, refundable within 30 days (pricing, checked on 11 November 2026).

Where neither tool reaches

There is no connection between them. Causality Engine's integrations page describes a read of the channels a GA4 export records, so Planable figures in it only through visits its approved links produce.

The read needs 12 months or more of GA4 data, and a channel under 1% of credit on both methods is called too small to act on (how it works). Small client pages will often sit below that line. Published posts are kept 13 months on Basic and Pro and then deleted (pricing file), so a year-on-year comparison of Planable's own figures needs an export first. Feedback, sign-off and the calendar remain Planable's work.

Planable's help articles close on "See what your ad budget actually bought", and the add-on sells that line per workspace; what it then shows is spend and clicks in Meta's Ads Insights, which is what the budget bought from the platform, never what the client's shop sold.

See also

• Planable: workspaces, approval types and add-ons
• How to use Planable: a month of client approvals
• Planable on the marketplace: Planable's affiliate program terms
• Causality Engine: the read, what it needs and costs
• How to use Causality Engine: one export through to a regional test
• Causality Engine on the marketplace: its affiliate program terms
• Planable vs Loomly: paying per client or per approver
• How to find what Direct traffic is hiding: what the Direct row holds

FAQ

Can Planable send its analytics to Causality Engine?

No, and the read would not use them. Causality Engine takes only a GA4 export, where Planable's approved posts appear as Organic Social visits once their links are tagged (integrations).

Does Planable add UTM parameters for me?

Not according to its help centre, which documents no UTM setting and says no link shortener is integrated (link shortener article). Tag each link before it goes into the post.

Why do Planable's clicks exceed GA4's sessions?

Planable shows the platform's own count of clicks the post received. GA4 counts a session only when its tag loads on your site, so consent refusals and abandoned loads fall away.