Table of Contents
ToggleShort answer: An AppsFlyer S2S event not recorded after a 200 OK means AppsFlyer received your request, but the event did not end up where you are looking. A 200 only confirms receipt. AppsFlyer’s reference says that on receipt of a message, minimum data validation is performed. The documented trap is an iOS app ID sent without the id prefix, which AppsFlyer says returns a valid 200 OK without recording the event. Add the prefix, check the AppsFlyer ID and the eventTime, then confirm the event in raw data.
This guide is for developers, marketers and agencies who send in-app events to AppsFlyer from a server and get a 200 OK, but the event is not showing. Below you will find what a 200 really means, a wrong and a fixed request, five causes of an AppsFlyer S2S event not recorded with a way to check each one, how to confirm the event really landed, a checklist and a short FAQ.
The button opens the Attribution Debugger with a sample request that gets a 200 OK and records nothing. The check runs in your browser and nothing is uploaded.
The server-to-server events API takes a POST request to https://api3.appsflyer.com/inappevent/{app_id}, with the app ID in the URL path and the event in the body. Because only minimum validation happens on receipt, a 200 tells you the message arrived and passed a basic check. It does not tell you the event was recorded, tied to an install or shown in a report.
That is why an AppsFlyer S2S event not recorded is hard to spot. Nothing fails loudly. The request looks fine in your server logs, and the event is simply missing in AppsFlyer. A 401 is the opposite case: AppsFlyer rejects the key and says so, as explained in the AppsFlyer S2S 401 Unauthorized guide.
Here is a request for an iOS app that sends the App Store ID as a bare number in the path. AppsFlyer answers 200 OK, and the event is never recorded:
curl --request POST \
--url https://api3.appsflyer.com/inappevent/123456789 \
--header 'authentication: YOUR_S2S_KEY' \
--header 'content-type: application/json' \
--data '{
"appsflyer_id": "1700000000000-1234567890123456789",
"eventName": "af_login",
"eventValue": "",
"eventTime": "2026-11-07 10:15:30.000"
}'And the fixed request, with the id prefix on the iOS app ID:
curl --request POST \
--url https://api3.appsflyer.com/inappevent/id123456789 \
--header 'authentication: YOUR_S2S_KEY' \
--header 'content-type: application/json' \
--data '{
"appsflyer_id": "1700000000000-1234567890123456789",
"eventName": "af_login",
"eventValue": "",
"eventTime": "2026-11-07 10:15:30.000"
}'The app ID, AppsFlyer ID and key above are placeholders. Never paste a real key into a post, a chat or a screenshot. For an Android app, the app ID is the package name, such as com.example.myapp, with no prefix.

The first cause of an AppsFlyer S2S event not recorded below is the one AppsFlyer documents with a 200 OK. Causes 2, 3 and 5 follow from AppsFlyer’s own documentation, and cause 4 is a common cause seen in practice. Where AppsFlyer documents the point, the text says so.
Support: AppsFlyer’s S2S overview says to prefix the iOS app ID with id, and that failure to do so results in a valid 200 OK return code without recording the event.
Fix: send id123456789 in the URL path, not 123456789.
How to check: look at the URL your server calls, not the body. If the part after /inappevent/ is only digits, this is the cause. The same mistake can sit in a config file, an environment variable or a no-code tool, so check where the app ID comes from.
Support: AppsFlyer’s overview describes appsflyer_id as a unique identifier generated by AppsFlyer when the app launches for the first time. AppsFlyer’s S2S article asks you to make sure it is a real AppsFlyer ID related to an actual app install. The same article says that S2S events arriving before AppsFlyer finishes processing the install, which generally takes 20 to 30 seconds or more, may be marked as unattributed organic events, and recommends a short delay before reporting S2S in-app events that happen right after the install. Those events are recorded, but they show as organic instead of under the right media source.
Fix: read the AppsFlyer ID from the AppsFlyer SDK on the device, store it with the user on your server, and send that value. Do not reuse an ID from another app, another environment or a test you made up.
How to check: find the AppsFlyer ID you sent in your install data for the same app. If it is not there, AppsFlyer has no install to tie the event to.
Support: AppsFlyer’s overview says eventTime is the time the event occurred in UTC, in the format yyyy-mm-dd hh:mm:ss.sss, and that without it the time is set to the HTTP message arrival time. AppsFlyer’s S2S article says events that arrive on the day of the event, or the following day until 02:00 UTC, are stamped with the eventTime. Older events arriving after 02:00 UTC, and events with an invalid eventTime, are stamped with the arrival time.
Fix: send the eventTime in UTC and in that exact format, or leave it out.
How to check: an event sent shortly after midnight UTC with yesterday’s eventTime, or with a local time that is behind UTC, can be stamped on the previous date. Widen your date range to include the day before, and compare the eventTime you sent with the date you are filtering.
Support: common cause, not an AppsFlyer statement. Your iOS and Android apps have different app IDs in AppsFlyer, and a staging app is not your production app.
Fix: send the event to the app ID of the app you report on.
How to check: compare the app ID in your request URL with the app ID of the app you have open in AppsFlyer. A server that serves both platforms often sends every event to one of them.
Support: AppsFlyer’s S2S article says recorded S2S events are available across the platform, including dashboards, raw data and analytics, and that in event raw data reports the date range relates to the event date, not the install date.
Fix: look for the single event in raw data, not only in dashboard totals, and filter by the event date.
How to check: follow the steps in the next section.
Most guides about an AppsFlyer S2S event not recorded stop at the request format. A 200 is not proof, so check the event itself:
id prefix. An Android app uses its package name.yyyy-mm-dd hh:mm:ss.sss, or left out.If you still have an AppsFlyer S2S event not recorded after these fixes, paste the request, or the cURL command, into the Attribution Debugger. It flags a missing id prefix, an AppsFlyer ID in the wrong format and an eventTime in the wrong format. It reads only what you paste and cannot see inside your AppsFlyer account, so remove the key before you paste. The check runs in your browser and nothing is uploaded.
If the findings are more than you want to fix yourself, use the buttons under the report to request a written fix plan. For more guides like this one, go back to the debug hub, or open the Mobile App Attribution Debugger. Sources: AppsFlyer, Server-to-server events API overview, AppsFlyer, Server-to-server events API: Send Event and AppsFlyer, Server-to-server events API for mobile.
No. AppsFlyer’s reference says that on receipt only minimum data validation is performed, so a 200 means the request arrived. An AppsFlyer S2S event not recorded can still return 200, for example when the iOS app ID has no id prefix.
AppsFlyer’s S2S overview says that failure to prefix the iOS app ID with id results in a valid 200 OK return code without recording the event. Use id123456789, not 123456789.
No. AppsFlyer asks you to use a real AppsFlyer ID related to an actual app install. A made-up ID, or one from another app, has no install to tie the event to, so an AppsFlyer S2S event not recorded is the expected result.
UTC, in the format yyyy-mm-dd hh:mm:ss.sss. If you leave eventTime out, AppsFlyer uses the time the request arrived.
In the in-app events raw data for the same app, filtered by the event date, the AppsFlyer ID and the event name. AppsFlyer’s S2S article says the event raw data date range relates to the event date, not the install date.
Built by Al-Fahad Hridoy, an Attribution & Tracking Consultant who fixes Meta Conversions API, WhatsApp click-to-chat, AppsFlyer and Firebase tracking for apps and websites.