Solved

Batch uploaded data not queryable

  • 14 June 2021
  • 4 replies
  • 195 views

Badge

Hey there, I uploaded some events data from batch api couple of hours back. I received a 200 in response as well. There were 140 events to be precise but they don’t seem to be queryable in my charts. I can see the data got uploaded successfully from web portal as well by going into sources & destinations → identify & event counts but there is nothing in user look up or charts. PLEASE HELP!

icon

Best answer by MikkoKarvonen 15 June 2021, 12:13

View original

4 replies

Userlevel 5
Badge +3

Hey there, I uploaded some events data from batch api couple of hours back. I received a 200 in response as well. There were 140 events to be precise but they don’t seem to be queryable in my charts. I can see the data got uploaded successfully from web portal as well by going into sources & destinations → identify & event counts but there is nothing in user look up or charts. PLEASE HELP!


It’s difficult to say much here without knowing more details and what the payload looked like. Is there anything more you could share?

Badge

 


​​​​​​From above screenshot you can see that I uploaded 140 events (using batch api) on 14 June but apparently they are not being shown in user look up table or in any charts which I have created upon these events. While when I log an event using logEvent method from React native SDK, the event gets shown in look up table realtime. Now my only question is do I have to do something different to make my events queryable uploaded using batch api as compared to using logEvent method?

​​​​​​
My payload for batch api looks like this:

 

Userlevel 5
Badge +3

I think the problem might be the “time” field in your payload.

If you check the Batch API documentation (https://developers.amplitude.com/docs/batch-event-upload-api), it says:

The timestamp of the event in milliseconds since epoch. If time is not sent with the event, it will be set to the request upload time.

That would put your events a few hundred milliseconds after the epoch, i.e. 1.1.1970 00:00:00UTC.

I have no idea if Amplitude has something in place to catch things like this.

As a side note, if you plan to track European users, including actual names in your dataset like means you have to be very careful about staying GDPR compliant.

Userlevel 5
Badge +8

Hi!

 

The above responses could be a reason you are not seeing your events in the right place! The value you input for time is important on any Amplitude event. We group the events in an event stream based on the time value. https://help.amplitude.com/hc/en-us/articles/229313067#Individual-Event-Stream

 

Were you able to find your events after learning about this fact?

 

Best,

Sydney

Reply