Conversation
|
Hi @nhausman1 , Regards, |
|
Hi @nhausman1 While this is something that might be supported on future releases, currently it's still being discussed. I've talked with the SDK PM and we created feature request for this, which would help the product team prioritize it properly. We're truly sorry for any inconveniences this may cause. If all you need to do is to send previously captured events in batches, we can work with you on a small wrapper for our API. We'll keep your request in mind and probably reach out to you looking for feedback when we start working on the final design for this feature. Thank you very much for understanding. |
|
Hi @nhausman1, Just want to let you know that our Admin API do support posting bulk events allowing specifying the event timestamp. Thanks |
Python SDK
What did you accomplish?
Currently the timestamp for an event is hardcoded as the current time in the track function. This means that you cannot backdate events if, for example, you wanted to run a script every 24 hours that gathers/calculates relevant events and push them to Split. This backdating feature is however supported in Split's JSON Rest API so it will be great to have similar access through the simplified Python API.
Note that this change is non-breaking as I've implemented the logic such that when timestamp isn't specified the logic falls back to
time.time().How do we test the changes introduced in this PR?
Standard build script/test suite. I've added tests for both positive and negative cases.