Automation Health Is UTC While Classic Tracking Often Is CST
Automation timestamps and email/mobile tracking appear offset in a combined operational report.
Trust & provenanceSTUDY
Evidence tierSTUDYOfficial sources2Other sources0Last verifiedNot recorded
Evidence tier describes my hands-on relationship with the content. Official sources describe platform contracts/documentation. Production observations should not automatically be treated as official limits.
_AutomationInstance/_AutomationActivityInstance are documented in UTC, while many classic tracking/mobile Data Views store times in Central Standard Time without DST.
What to check
- Identify the documented timezone for every source before joining by time window.
- Avoid assuming GETDATE() and GETUTCDATE() mean the same thing for all views.
Make it cheaper next time
- Normalize timestamps into one reporting timezone explicitly.
- Put timezone metadata in the Atlas/report schema.
timezoneutccstdata views