Updates with Event Signals
We’ve recently made some improvements to Event Signals in our API. These improvements will make things easier for you to use Event Signals and to get insights on what events impact your business the most.
Get a quick refresher on what Event Signals is all about then read on to find out what improvements we’ve made.
1. Way more common date formats accepted
One of the main issues users encountered when using Event Signals was that our required date format was very strict. The date had to be specifically formatted as: yyyy-mm-dd hh:mm:ss in order for the output to process properly. For example, 2015-12-25 08:30:00.
We’ve now been able to remove the need for that strict format. We also have a date format validation check in place too. This way, if there still is an issue with your date formatting, you’ll be advised on the spot, not left wondering what went wrong.
2. Algorithm updated
There’s a lot of science and event intelligence that goes on behind the scenes. Our algorithm has been updated so that when you want to get an explanation of what happened for your business on a specific date, events are now not just correlated with your spikes and troughs but instead based on an estimated impact. That means the results you see when you do your analysis are more accurate than ever. Also check out our updated developer docs on Signals API.
3. XLSX files now accepted
Previously, we were only able to accept and process CSV files. Now, you can upload XLSX files too.
Alternatively, use our PredictHQ API to continuously feed in data rather than doing ad hoc uploads of a CSV or XLSX file with new data each time. That way, our algorithm can keep learning and provide you with more accurate results as new data comes in.
4. Index page
We’ve made it easier for you to now not only find all your Event Signals in an index page, but you can also edit, delete or expand to see high level details about each, all from this one location. Furthermore, if you have multiple Event Signals, you’ll be able to sort by created date, title or last edited dates.
5. Creating new Event Signals
You can now do this from several places. Create a new Event Signal from your:
Left hand navigation menu
Signals index page
6. Processing placeholder
Previously, when uploading a large file which takes a longer time to process, users would have been taken straight to the output page, but were told via a system message that there wasn’t enough data to display anything. This was because the processing was still taking place in the background so the output would have eventually shown after waiting a bit longer or after refreshing the page, but the error message was unhelpful and misleading. We recognized that this was a poor user experience. So, now we advise you over the duration of the time we’re processing your data that the processing is going on.
The popup modal will automatically close once your data has fully finished processing. Leaving nothing up for question and making it a much better user experience all around.
7. Errors highlighted
One super handy added feature is that if you’ve got any errors within your data that you upload, we now inform and highlight for you what they are. You can then either choose to fix your file and re-upload the data, or accept the known errors and proceed anyway to your output with the data that did get imported without any issues. You may wish to ‘proceed anyway’ if there are simply a small handful of errors that you’re happy to accept. These errors can range from rows with missing values, incorrect value formats or incorrect mappings