| Edition:Growth, Corporate, Enterprise | Audience: Timezone Admin |
How Timezones Work with Bullhorn Analytics
This article explains how both Bullhorn ATS and Bullhorn Analytics calculate timezones in order to show your data on the correct date.
Timezone Calculation/Logic
- When you first log in to Bullhorn ATS, it identifies the local timezone from your computer and stores it against your user record.
- When a record is created or edited in Bullhorn ATS, it takes the local time that action was taken, converts that into EST, and stores it on the database.
- When Bullhorn Analytics loads the record, it converts that date into UTC, and then applies the relevant owner's timezone against that record. It is this conversion that can cause confusion, because unless you have set a timezone in Bullhorn Analytics, the UTC date might be on a different date to when the action was actually taken.
- In short, as long as users' local computer timezone and Bullhorn Analytics timezone match, you should never have an issue.
Activity Showing for the Incorrect Day
If you notice that data does not display on the day it was inserted by the relevant user in Bullhorn Analytics, it is likely your timezones for that user/group have either not been set, or have been misconfigured.
You can manage users' timezones via Admin > Timezones. For a guide to managing timezones, see Set a Timezone.
Was this helpful?