Sending a user_id of a number will 200 but event won't show in Dashboard about amplitude-node HOT 6 OPEN

Hey @Galkon ,

Sorry to hear that. We'll pass this on to our data ingestion team for the response being returned by the HTTP v2 API, and also include some better tooling in this SDK to validate the events better.

from amplitude-node.

Hello, user_id should be a string type.

from amplitude-node.

Yeah I understand that, therefore the fact that you can send an integer and not get an error response, and have the event silently disappear, is a bug.

from amplitude-node.

@tom-james-watson in your 200 response, do you have logs of the other metadata? e.g. how many events were ingested. in 1.0.x and onwards there is an issue where we silently throw away events with neither user nor device id.

when I hit the http api with 123 I get a different response - it errors because it is too short. I've found that creating numeric user ids of length > 5 do get accepted though.

from amplitude-node.

from amplitude-node.

+1 here, we ran into this and were stuck on it for over a day. It's easy to overlook, the request should definitely not 200 when it fails to log the event or track anything. We were trying to track "user_id": 15479253 and that would give us a 200, with eventsIngested = 0 in the callback. We finally spotted that it needed to be a string, and we got a 200 with eventsIngested = 1.

Amplitude should handle invalid data in a better way.

from amplitude-node.