Native mobile tracking that ships to your infrastructure

Why most mobile SDKs make measurement worse

The standard mobile measurement stack is a stack of vendor SDKs: Firebase for analytics, Adjust or AppsFlyer for attribution, Meta SDK for CAPI, the platform SDK for Pinterest / TikTok / LinkedIn / Snapchat, and a CMP SDK on top to coordinate consent. Each adds binary size, third-party network calls, and an independent privacy review.

SDK in practice

Configure once at app start. Track events with the same property shape as the web SDK so your blueprints work for both. Identify after sign-in, update consent when the CMP returns.

// AppDelegate.swift or App.swift
import DataflySignal

@main
struct MyApp: App {
    init() {
        Datafly.shared.configure(
            endpoint: URL(string: "https://collect.yourbrand.com")!,
            pipelineKey: "ios_app_production",
            options: .init(
                consentDefault: .denied,
                attBehaviour: .respect,
                identityKeychain: true
            )
        )
    }

    var body: some Scene {
        WindowGroup { ContentView() }
    }
}

// Track an event
Datafly.shared.track("purchase", properties: [
    "value": 29.99,
    "currency": "USD",
    "items": ["sku_123"]
])

// Identify a user (after sign-in)
Datafly.shared.identify(userId: "u_4f9a", traits: [
    "email": "user@example.com",
    "plan": "premium"
])

// Update consent when CMP returns
Datafly.shared.setConsent([
    "marketing": true,
    "personalisation": false,
    "analytics": true
])

// MyApplication.kt
import com.datafly.signal.Datafly
import com.datafly.signal.Options

class MyApplication : Application() {
    override fun onCreate() {
        super.onCreate()
        Datafly.configure(
            context = this,
            endpoint = "https://collect.yourbrand.com",
            pipelineKey = "android_app_production",
            options = Options(
                consentDefault = Options.Consent.DENIED,
                identityEncryptedPrefs = true
            )
        )
    }
}

// Track an event
Datafly.track("purchase", mapOf(
    "value" to 29.99,
    "currency" to "USD",
    "items" to listOf("sku_123")
))

// Identify
Datafly.identify("u_4f9a", mapOf(
    "email" to "user@example.com",
    "plan" to "premium"
))

Mobile SDK approaches compared

How a typical multi-vendor SDK stack compares to a single first-party SDK.

Frequently asked questions

How does the SDK handle ATT denial on iOS?

When App Tracking Transparency is denied, the SDK does not attach the IDFA to events and falls back to its own first-party anonymous_id stored in the iOS Keychain. Server-side, the Signal Core handles the rest of the vendor-specific behaviour (SKAdNetwork postbacks for ad networks that need them, Meta CAPI app event format) without the SDK needing per-vendor logic. The user's privacy choice is honoured end to end.

Does the SDK send to vendor SDKs at all?

No. The Datafly Signal SDK has only one network destination: your own first-party Ingestion Gateway, e.g. collect.yourbrand.com. There are no Firebase calls, no Adjust pings, no Meta SDK requests, no TikTok SDK traffic. Vendor delivery happens server-side once the event reaches the Signal Core. This dramatically simplifies app store privacy declarations and shrinks the third-party network surface.

How does identity stitch between web and app?

The same anonymous_id format is generated server-side for both web and app pipelines. When a user signs in on either surface, the identify call links the anonymous_id to a user_id. Subsequent web visits and app launches resolve to the same identity record. Cross-device and cross-surface attribution is deterministic, with no probabilistic stitching.

What about SKAdNetwork postbacks?

SKAdNetwork postbacks are received server-side by the Signal Core when ad networks send them. They're joined to the matching app install or conversion event using the SKAdNetwork conversion value, then delivered to your warehouse and to vendors that use them for attribution. The SDK doesn't handle SKAdNetwork directly — that complexity stays server-side where it can be updated without an app release.

How big is the SDK in MB?

The iOS SDK is under 200KB and the Android SDK is under 250KB. Compared to a typical multi-vendor stack (Firebase ~3MB, Adjust ~2MB, Meta SDK ~5MB, TikTok SDK ~2MB), removing those vendor SDKs in favour of one first-party SDK reduces app binary size by 5-10MB depending on the prior setup.

Can I use it alongside my existing Firebase or Adjust setup?

Yes, during migration. The Datafly Signal SDK runs in parallel with vendor SDKs without conflict. Most teams run both for a transition period while validating that server-side delivery matches client-side reporting, then remove the vendor SDKs once confidence is established. Migration is incremental, not big-bang.