Pallyy With Causality Engine: Tag the Bio Link Before You Count

The short answer: Pallyy can show that people tapped. It has no way to show that they paid. Pallyy, the social scheduler priced per social set for agencies and brands, reports clicks and impressions on its link in bio page and analytics for 3 platforms, Instagram, Facebook and LinkedIn, each figure taken from the platform's own API (analytics help). Its help pages describe no setting that adds UTM tags to your links, so GA4 learns where a visitor came from only if you tag the address yourself, which Pallyy's free UTM builder does. Once the tagged visits are in GA4, Causality Engine, a causal attribution tool that reads GA4's Attribution paths export, can weigh Organic Social against your other channels, starting with 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.

What a bio link click is worth, step by step:

1. Price a click with your own numbers, and label it. For example, 1,410 button clicks at an assumed 2.2% store conversion rate is 1,410 × 0.022 = 31.02, so about 31 orders. That rate belongs to the whole site, not to people arriving from a bio.
2. Start from the page you already run. The bio link's per-link click table (link in bio help) tells you which buttons carry traffic. Tag those first.
3. Pick the GA4 row you will watch. Organic Social in the Traffic acquisition report, filtered on your bio link campaign, is the count to set beside the 31.

The pairing in one table

Pallyy's numbers stop on its own page

Pallyy's analytics covers Instagram, Facebook and LinkedIn; TikTok and X can be published to but do not appear, the analytics help explains, and the metrics come straight from each platform's API. Custom reports, on Agency and Scale, can include Instagram's website clicks and other profile actions (custom reports help).

The link in bio page is Pallyy's own, included on Pro, Agency and Scale. Its insights show clicks and impressions over time and a table of clicks per link, so you can see "which links earn their spot" (link in bio help). That is the last step Pallyy can see. A tap on a button sends the visitor to whatever address you typed, and from there the store and GA4 take over.

So the fit here is partial, and plainly so. Pallyy documents clicks. It documents no orders, no revenue and no Shopify or GA4 connection.

Tagging the links Pallyy sends

Pallyy's UTM builder takes a URL, source, medium and campaign name, with content and term optional, and assembles the tagged address in your browser at no charge. Its own guidance is sound: lowercase, hyphens for spaces, the same names forever, and tag the bio link too, "and profile clicks stop hiding inside your direct traffic". Google says the same from its side: its page on (direct) / (none) names links without UTM parameters as a cause of lost sources.

Two settings decide the channel. Google files a visit under Organic Social when the source matches its list of social sites, instagram among them, or the medium is social, social-network, social-media, sm, social network or social media (default channel group). A scheme that fits Pallyy's job:

• Bio link buttons: source instagram, medium social, content bio-link plus the button name.
• Links in captions on Facebook or LinkedIn: source facebook or linkedin, medium social, campaign named after the month or product.
• Stories with a link sticker: content story-link, so it does not merge with the bio.

One correction to carry: the builder page says analytics tools are case sensitive. The report rows are, so "Instagram" and "instagram" split. Google's channel rules are not, so both still land in Organic Social.

A worked example from the bio page to the till

For example, with figures invented to show the arithmetic and no shop behind them: in a 30-day month a jewellery brand's Pallyy bio page shows 3,260 impressions and 1,410 button clicks. GA4 records 1,020 sessions with content bio-link, all under Organic Social, and gives Organic Social 26 last-click purchases. Direct gets 140. The store booked 455 orders, while Meta's dashboard claims 251 and Google Ads 198.

The leak first: 1,410 - 1,020 = 390 taps with no recorded session, from consent refusals, closed tabs and in-app browsers. Then the claims: 251 + 198 + 26 = 475, which is 475 - 455 = 20 more orders than were booked, before search and email. And 140 orders sit under Direct, a row that names no sender, though a buyer who saw a post and typed the address later lands there too.

That last group is where the read starts. Per its how-it-works page, Causality Engine splits Direct back to the channels that sent those buyers, sets each channel's caused share beside a last-click rebuild from the same export, and adds a data-health score from 0 to 100 and a next step tested in one region first. It reads Organic Social as a whole: the bio link, caption links and untracked shares all count together. Which button did it stays in Pallyy's table.

If the read puts Organic Social well above 26, do not double the posting rota on that alone. Test the change in one region first.

The free check: swap the top button for two weeks

Pallyy lets you reorder, edit and delete bio links at will (link in bio help). Use that. For two weeks, point the top button at your best seller with a tagged link; for the next two, replace it with a link that goes nowhere near a product, such as the blog. Then compare orders of that product in the store's own export across the two fortnights. It is a by-hand test, rough, and any promotion or ad change in the window ruins it. On a steady account it shows whether the bio link sells or only gets tapped, at no cost.

When the question becomes social against everything else, export the Attribution paths CSV and drop it on the start page. The preview is free and worked out in your browser. Causality Engine, which I founded, sells the full read of that file at €99 once, excluding VAT, refundable for 30 days (pricing, checked on 11 November 2026).

Where the pairing runs out

Nothing connects the two products, and nothing has to. The integrations page describes a read of every channel a GA4 export records; Pallyy shows up in it only as tagged Organic Social visits.

The read asks for 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). A client whose bio link brings a few hundred visits a month will often land there. And the read schedules nothing, collects no approvals and builds no client report; those stay in Pallyy.

Pallyy's bio link insights end at the tap on Pallyy's own page, the one step it hosts, so the figure that says the page is working is measured before the store has any chance to disagree, and it renews with the social set either way.

See also

• Pallyy: social sets, plans and the MCP server
• How to use Pallyy: a client's month of posts signed off
• Pallyy on the marketplace: Pallyy's affiliate program terms
• Causality Engine: the read, its inputs and its price
• How to use Causality Engine: from export to budget decision
• Causality Engine on the marketplace: its affiliate program terms
• Pallyy vs Later: a client roster or one brand's Instagram
• How to export GA4 data for attribution: the file the read needs

FAQ

Is there a Pallyy integration for Causality Engine?

No. Pallyy sends nothing to it and needs to send nothing. The read takes a GA4 export, and Pallyy's links appear there once they carry UTM tags (integrations).

Why are bio link clicks higher than GA4 sessions?

The click is counted on Pallyy's page, before the store loads. GA4 records only visits whose tag fires, so refused consent, a closed in-app browser or an untagged link each lose one.

Can Pallyy show sales from Instagram?

Not from its documentation. The analytics help lists reach, impressions, engagement and profile metrics from each platform's API, and the bio link reports clicks. Orders come from the store or GA4.