CONNECTIONS / Adjust
Adjust callbacks, turned into app conversions everywhere
Adjust already attributes the install and fires a callback for it. Signals reads that callback, checks ATT and SKAdNetwork status, and turns it into a Meta, Snap, or TikTok app conversion without asking anyone to touch the SDK.
- ● adjust :: signals live
- > postback install network=organic
- > postback event purchase value=42.00 AED
- hash sha256(email,phone) att=opted_in
- route meta · snap · tiktok
- ✓ 3 destinations synced · match 76%
The signal Adjust yields.
Every kind of signal that moves between Adjust and the platforms, through one hashed, deduplicated route.
- App conversions
- Every install Adjust attributes reaches Meta, Snap, and TikTok server-side, without waiting on the ad network's own postback integration.
Pick your platform. Every use case for it, in one place.
Every way Adjust data moves, grouped by platform and ranked by how many use cases Adjust supports.
Meta 1 
Snap 1 
TikTok 1 From authorization to delivered signal.
-
Point a callback at Signals
Adjust's global callback URL, or a per-event callback, added alongside whatever Adjust already sends to app stores or a data warehouse.
-
Map callback fields
Install and event callback parameters mapped to each destination's app-conversion schema for Meta, Snap, and TikTok in the visual mapper.
-
Check ATT and reconcile
Identifiers hashed, ATT and SKAdNetwork status checked, and the event deduped against SDK traffic on Adjust's event ID before anything leaves.
-
Deliver with match feedback
Server-side delivery to Meta, Snap, and TikTok, with per-destination match results visible in the live debugger.
Adjust questions, answered.
Does this replace the ad network callbacks we already configured in Adjust?
No. Adjust can already fire a callback straight to an ad network's own postback URL, and those can stay in place. Signals reads the same callback stream in parallel and adds hashed, server-side app conversions with dedupe on Adjust's event ID, so a network that already has a matching callback does not receive the event twice.
What happens to a callback when a user opts out of ATT?
An ATT opt-out removes IDFA from the callback, but Adjust still sends the install and event with GPS ADID on Android or a SKAdNetwork conversion value on iOS. Signals forwards whichever identifier survives, plus any hashed email or phone collected at login, so the app conversion still reaches Meta, Snap, and TikTok with something to match against.
Does Signals treat an install postback differently from an in-app event postback?
Yes. Adjust fires a separate callback for the install and for each in-app event it tracks, and Signals maps them to the matching event type on each destination, an install to Meta's app-install event and a purchase callback to its purchase event, rather than collapsing everything into one generic conversion.
Do we need to change how Adjust is configured?
Only one callback URL changes. Adjust's global callback or a per-event callback can point at Signals alongside whatever it already sends to an app store or a data warehouse, with no change to the SDK integration mobile engineering already shipped, and no gap in the events Adjust was already recording.
NEXT STEP
See your Adjust data working in every ad platform.
Ready to enable a use case, or still mapping what Adjust data could do? Our team helps you find the right place to start.
