AppsFlyer S2S 400 Error: 5 Causes and a Quick Fix
A 400 from the AppsFlyer S2S API always comes with a message that names the problem. Here is what each message means and how to fix...
Read the guideDebug
Table of Contents
ToggleFree tools and step-by-step guides to find where your tracking breaks.

A 400 from the AppsFlyer S2S API always comes with a message that names the problem. Here is what each message means and how to fix...
Read the guide
A 200 OK from the AppsFlyer S2S API only means the request arrived. Here are five reasons the event never shows up, and how to confirm...
Read the guide
A Measurement Protocol app event sent with measurement_id is aimed at a web stream, so it does not show under the app. Use firebase_app_id in the...
Read the guide
Adjust needs a device identifier on every S2S event, and without one it has nothing to match the device with. Check that the field is filled,...
Read the guide
Adjust rejects server-to-server events with a timestamp older than 58 days, and events that arrive earlier than one already received for the same device and event...
Read the guide
AppsFlyer returns 401 when the key in the authentication header is not the S2S key for the app. See five common causes, a safe cURL example...
Read the guideIf your error is not covered by a guide above, send me the error message or a short description of what is going wrong, and tell me which tool it comes from. I will reply in writing.