CONNECTIONS / App Events
In-app events, delivered to ad platforms without an MMP
Some apps skip an MMP entirely and log events straight from the SDK or the backend. Signals accepts either path, hashes what it receives, and routes each in-app event to Meta, Snap, and TikTok as a server-side app conversion.
- ● app events :: signals live
- > in-app event purchase value=31.00 AED
- > in-app event level_complete level=12
- hash sha256(email,phone) pii=cleared
- route meta · snap · tiktok
- ✓ 3 destinations synced · match 88%
The signal App Events yields.
Every kind of signal that moves between App Events and the platforms, through one hashed, deduplicated route.
- App conversions
- SDK events keep working offline and catch up the moment the device reconnects, so nothing logged mid-flight is lost.
Pick your platform. Every use case for it, in one place.
Every way App Events data moves, grouped by platform and ranked by how many use cases App Events supports.
Meta 1 
Snap 1 
TikTok 1 From authorization to delivered signal.
-
Add the SDK or point the backend at Signals
The lightweight iOS or Android SDK dropped into the app, or a server-to-server event call sent straight from the backend, no MMP in between.
-
Initialize and log an event
Signals key configured and a first in-app event logged, install, purchase, or any custom event the app tracks.
-
Map events
In-app events mapped to each destination's app-conversion schema for Meta, Snap, and TikTok in the visual mapper.
-
Verify and go live
Delivery and match results confirmed in the live debugger before the mapping goes live across every connected destination.
App Events questions, answered.
Do we need to run an MMP alongside this?
No. This path exists for apps that never installed one, whether that is a young app, an internal tool, or a team that decided not to pay for attribution. The SDK or a direct server-to-server call is the source of truth for the event, and Signals maps it straight to each destination's app event schema without an MMP's install or postback layer in between.
Does the SDK affect app performance?
The SDK is small, batches network calls instead of firing one per event, and queues events on the device when connectivity drops so nothing blocks the UI thread waiting on a response. A backend sending events by server-to-server call skips the SDK footprint question altogether, since the events never touch the client at all.
Is customer PII stored by Datahash?
Identifiers are SHA-256 hashed on the device before the SDK sends anything, or at ingestion if a backend is posting events by server-to-server call instead. No PII is stored on host servers in Datahash Cloud, and a self-hosted Core deployment is available for a team that cannot let data leave its own perimeter at all.
Can one event reach multiple ad platforms at once?
Yes. One event, an install, a purchase, a level-complete, whatever the app logs, can fan out to every connected destination in the same run, each with its own field mapping and delivery status in the live debugger. Nothing about sending to five destinations instead of one changes how the event is captured or hashed.
NEXT STEP
See your App Events data working in every ad platform.
Ready to enable a use case, or still mapping what App Events data could do? Our team helps you find the right place to start.