iOS, Android & Flutter Catch Up

Why this matters

If you ship a native app, your SDK choice shouldn't decide how much of LinkForty you get to use. Until now, the React Native and Expo SDKs led on two capabilities the native SDKs didn't have: knowing which SDK and version produced each event, and attributing what happens inside your app back to the link that brought the user in.

That gap is closed. The iOS (Swift), Android (Kotlin), and Flutter SDKs now match React Native and Expo on both fronts — same data model, same attribution behavior, same dashboards light up regardless of which SDK you integrate.

What every event now carries: SDK identity

Every install and in-app event reports the sdkName and sdkVersion that produced it, and each request to the LinkForty backend carries an X-LinkForty-SDK header.

This is what powers SDK Health in your dashboard: a clear view of which SDKs and versions are live in production, so you can spot an app stuck on an old build, confirm a rollout landed, and know exactly what's talking to your backend. With native parity, that picture is now complete across your whole install base instead of just the JavaScript apps.

What you get down-funnel: last-click attribution

The native SDKs now do last-click attribution with automatic screen-view tracking, just like React Native and Expo:

• In-app events attribute to the link that drove them — within a conversion window, on a last-click basis. A signup or purchase deep in your app traces back to the campaign link that started the journey.
• Automatic screen-view tracking — screen views are captured without you instrumenting every view by hand.
• A rotating session id ties a user's activity together for the length of a session without persisting a long-lived identifier.

The upshot: per-link mobile funnels, install attribution, and revenue attribution now work the same whether your app is Swift, Kotlin, Flutter, or JavaScript.

How to get it

Bump to the released versions:

• iOS — 1.4.0, via Swift Package Manager.
• Android — 1.3.0, on Maven Central as com.linkforty:sdk.
• Flutter — 0.2.0, on pub.dev as linkforty.

No backend changes are required — the identity header and attribution events are handled automatically once you're on a current SDK.

Getting started

Already integrated on an earlier version? Updating the dependency is enough to start reporting SDK identity and last-click attribution. New to the native SDKs? Each package ships with a short integration guide.

For installation steps and the full configuration reference for every platform, see the SDK docs.