CONNECTIONS / Mobile SDK
App events, direct from your code to ad platforms.
The Datahash Mobile SDK sits inside your iOS or Android app and emits events straight to Signals, no MMP required in the middle. Identifiers hash on-device before anything leaves the app, then Signals delivers server-side to Meta, Snap, and TikTok's app conversion APIs.
- ● mobile sdk :: event emitted
- > SDK event install first_open=true
- > SDK event purchase value=64.00 AED
- hash sha256(email,phone) on-device before send
- route meta · snap · tiktok
- ✓ delivered · no MMP in path
The signal Mobile SDK yields.
Every kind of signal that moves between Mobile SDK and the platforms, through one hashed, deduplicated route.
- App conversions
- Every install, session start, and custom event your app code logs reaches Signals directly, with no MMP resolving or relaying it first.
Pick your platform. Every use case for it, in one place.
Every way Mobile SDK data moves, grouped by platform and ranked by how many use cases Mobile SDK supports.
Meta 1 
Snap 1 
TikTok 1 From authorization to delivered signal.
-
Integrate the SDK
The Datahash Mobile SDK drops into the iOS or Android build, or connects through a Firebase export where that is the existing setup, with no MMP dependency to configure first.
-
Instrument events
Install, session, and purchase calls are placed at the point in your app code where they actually happen, so the event fires the moment the user does it.
-
Map to each app spec
Logged events map to Meta, Snap, and TikTok's app conversion schema in the visual mapper, the same destinations an MMP-fed setup would use.
-
Deliver, hashed and queued
Identifiers hash on-device, events queue through connectivity drops, and delivery runs server-side to every mapped destination, checked in the live debugger.
Mobile SDK questions, answered.
Do we need an MMP like Kochava or Singular to use the Mobile SDK?
No. The Mobile SDK emits install, session, and purchase events directly from your app code to Signals, so there is no MMP resolving attribution in the middle. Teams already running an MMP can keep it for multi-touch attribution and add the SDK for delivery, or use the SDK on its own if attribution modeling is not what you need.
Can the Mobile SDK still attribute an install to a campaign without an MMP?
It captures and forwards what the OS and store exposes at install, such as the Google Play install referrer, but it does not run multi-touch attribution logic across ad networks the way an MMP does. If crediting installs across several networks and channels matters, pair the SDK with an MMP; if a single-network or first-party view is enough, the SDK covers it alone.
Does the SDK add noticeable overhead to the app?
No. It is a lightweight client, batches network calls instead of firing one per event, and queues events on-device when connectivity drops rather than blocking the app. Identifiers hash before an event leaves the device, and no PII is stored on Datahash's host servers, so the performance and data-handling footprint both stay small.
NEXT STEP
See your Mobile SDK data working in every ad platform.
Ready to enable a use case, or still mapping what Mobile SDK data could do? Our team helps you find the right place to start.
