Adjust S2S Missing Device ID: 5 Causes and a Quick Fix

Short answer: an Adjust S2S missing device ID error means the request has no device identifier. Adjust’s S2S events page says each request needs an advertising ID, such as idfa for iOS or gps_adid for Android. Without an accepted identifier, the practical result is that Adjust has nothing to find the device with, so the event is not attributed. Add a filled identifier your app really collects, check the parameter name and its letter case, and resend.

This guide is for developers, marketers and agencies who send events to Adjust from a server. Below you will find which device IDs Adjust accepts, a BAD and a GOOD request, five common causes of an Adjust S2S missing device ID with a way to check each one, a quick fix, a checklist and a short FAQ.

Check this example in the Attribution Debugger

The button opens the Attribution Debugger with a sample request that has no device identifier. The check runs in your browser and nothing is uploaded. The tool reads only the request text you paste and explains likely causes. It cannot see inside your Adjust account and it cannot fix a request for you.

What an Adjust S2S missing device ID means

Adjust’s S2S events endpoint is https://s2s.adjust.com/event. A request carries the app token, the event token, s2s=1 and a device identifier. The page lists the identifier as an advertising ID, such as idfa for iOS or gps_adid for Android.

Adjust’s page also has a table of other device IDs, including android_id, idfv, imei, meid, win_naid and win_hwid, where they apply. For iOS, it recommends adid, the Adjust identifier, because it lets you match device data when the IDFA is not available.

Adjust’s page does not say what happens when no identifier is sent. The practical reading, which is not an Adjust statement, is that without one of these identifiers Adjust cannot find the device, so the event is not attributed. A request can look fine on your side while that happens. Confirm that events appear in Adjust, not only that your server got a response.

How an Adjust S2S missing device ID differs from an old timestamp

My guide to an Adjust S2S event older than 58 days is about timestamps. It covers the 58 day limit and the order of events by created_at_unix. This guide is about device matching. An event can have a perfect timestamp and still not be attributed because the request has no device identifier. Check both when an S2S event does not show up.

BAD vs GOOD request for an Adjust S2S missing device ID

Here is a request where the gps_adid parameter is there, but empty. The parameter name is right, and the value is missing, so Adjust has no identifier to match:

https://s2s.adjust.com/event?s2s=1&app_token=FAKE_APP_TOKEN&event_token=FAKE_EVENT_TOKEN&gps_adid=&created_at_unix=1700000000

And the same request with a filled placeholder value, which is the shape Adjust expects:

https://s2s.adjust.com/event?s2s=1&app_token=FAKE_APP_TOKEN&event_token=FAKE_EVENT_TOKEN&gps_adid=00000000-0000-4000-8000-000000000001&created_at_unix=1700000000

The values above are fake. Never paste a real app token, event token or device ID into a post, a chat or a screenshot, and leave your S2S security token out of anything you share.

Adjust S2S missing device ID

5 causes of an Adjust S2S missing device ID and how to fix them

The requirement for a device identifier comes from Adjust’s S2S events page. The five causes below are common causes seen in real setups, not Adjust statements. Each one ends with a check you can run.

1. The identifier field is present but empty

Support: common cause, not an Adjust statement. A template builds the URL with gps_adid= or idfa=, and the variable behind it is empty, so the parameter exists with no value.

Fix: fill the value from the source your app really collects, and do not send the parameter when you have nothing to put in it.

How to check: look at the final URL or body your server sends, not the template, and look for an equals sign followed by an ampersand or nothing.

2. A wrong parameter name or wrong letter case

Support: Adjust’s page says parameters for S2S events are case-sensitive. The device ID table also lists a format for some values, for example android_id in lowercase without hyphens and idfv in uppercase with hyphens. A name such as GPS_ADID or advertising_id is not one of the names on the page.

Fix: use the exact parameter name and format from Adjust’s page.

How to check: compare each identifier name in your request with the page, letter by letter.

3. An iOS advertising ID that is all zeros

Support: common cause, not an Adjust statement. An iOS advertising ID can arrive as a string of zeros, which is common when the app was not allowed to track. Adjust’s page does not describe how it treats such a value, so do not guess a rule.

Fix: check what your app actually collects and what your server forwards. For iOS, Adjust recommends adid, which helps when the IDFA is not available.

How to check: log the identifier on the device, and log it again on your server. If the value is already zeros on the device, the server is not the cause.

4. The ID was never passed from the app to your server

Support: common cause, not an Adjust statement. The app reads the identifier, but the call that sends the purchase or sign up to your backend does not include it, so the server has nothing to forward.

Fix: send the identifier from the app to your server with the event, or store it when the user first opens the app, and read it back when you build the request.

How to check: inspect the request from the app to your backend. If the identifier is not in it, the gap is in the app, not in the Adjust call.

5. A mix of iOS and Android identifiers in one request

Support: common cause, not an Adjust statement. A shared code path fills both idfa and gps_adid, one of them from the wrong platform, so the request describes two devices at once. Adjust’s page does not describe this case.

Fix: send identifiers for one platform per request, based on the device that produced the event.

How to check: look for requests that carry both an iOS and an Android identifier.

Quick fix for an Adjust S2S missing device ID

Use this order to clear an Adjust S2S missing device ID:

  1. Open the exact request your server sends, not the template.
  2. Check that one accepted identifier is there, with the right parameter name and letter case.
  3. Check that its value is filled, and is a real value from your app, not a placeholder or zeros.
  4. Send identifiers for one platform per request.
  5. Resend a test event and check that it appears in Adjust.

Checklist after fixing an Adjust S2S missing device ID

  • The request carries one accepted device identifier.
  • The parameter name and letter case match Adjust’s page.
  • The value is filled, and comes from what your app really collects.
  • The identifier reaches your server from the app.
  • No request mixes iOS and Android identifiers.
  • The timestamp is inside the window and in order, as in the 58 day guide.
  • A test event appears in Adjust, not only in your server log.

Check your own Adjust S2S missing device ID

Paste the request text for your Adjust S2S missing device ID into the Attribution Debugger, and it explains the likely causes. It reads only what you paste. It cannot see inside your Adjust account and it cannot fix the request, so paste it with fake or removed tokens, never a real token. The check runs in your browser and nothing is uploaded.

Check this example in the Attribution Debugger

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, read the Adjust S2S event older than 58 days guide or the AppsFlyer S2S 401 guide. Source: Adjust, Server-to-server (S2S) events API.

Frequently asked questions

Which device ID does Adjust need for an S2S event?

Adjust’s S2S events page says each request needs an advertising ID, such as idfa for iOS or gps_adid for Android. It also lists other device IDs it accepts, including android_id, idfv, imei, meid, win_naid and win_hwid where they apply, and it recommends adid for iOS.

Why is my S2S event not attributed?

A missing device ID is one reason. If the request has no accepted identifier, Adjust has nothing to find the device with. Adjust’s page does not describe the exact outcome, so treat this as the practical reading. Also check the timestamp, because an event older than 58 days is rejected.

Can I send an empty gps_adid?

Adjust’s page does not describe how it handles an empty value. An empty gps_adid gives Adjust nothing to match, so send a filled value, or another identifier from the accepted list that your app really collects.

What if I have no advertising ID?

Check which other identifier your app collects. Adjust’s page lists others it accepts where they apply, such as android_id, idfv, imei, meid, win_naid and win_hwid. For iOS, Adjust recommends adid, which helps when the IDFA is not available. Never invent a value to fill the field.

Does iOS need idfa or idfv?

Adjust’s page gives idfa as the iOS example of an advertising ID, and lists idfv among the device IDs it accepts. It recommends adid for iOS, because it lets you match device data when the IDFA is not available. Which one fits depends on what your app collects, so check the full list.

Can I test this without sending real data?

Yes. Paste a sample request into the Attribution Debugger, which checks it in your browser and uploads nothing. Or check the request on paper with fake tokens and fake device IDs, and look for an empty or missing identifier before you send anything real.

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.