FindingcurrentGTM data

Date-only CRM activities land on the previous day

Because the CRM splits due date and time, parsing a bare date as midnight UTC lands it on the previous evening.

SymptomActivities logged with a date but no time show on the day before in timelines viewed from the Americas. A reply also sorts below its own quoted copy.

CRMs often store an activity's due date and its time as separate fields, and the time is optional. Combining them into one timestamp is the standard move, and parsers such as JavaScript's Date read a bare date as midnight UTC.

Midnight UTC falls on the previous evening across the Americas, so a call logged for Tuesday with no time renders on Monday evening. Salesforce's Event object reference says ActivityDate holds the due date of an all-day event with a timestamp always set to midnight UTC, while ActivityDateTime holds the time for events that are not all-day.

Ordering breaks too. A date-only reply sorts below the quoted copy of it that arrived with a real time, so the thread reads backwards.

Date-only activities can be common enough to skew time-of-day metrics.

The remedy is to keep date and time separate, with a "time unknown" flag.

In a synthetic test set of 500 activities, 100 of them date-only, converting to Los Angeles time put all 100 on the previous day; keeping them as dates put none there. The set shows the mechanism, not how common it is.

Check your setup read-only

Count CRM activities flagged as date-only. A date-only activity is a task's due date with no time, or an all-day event. Compare the date-only activities with the activities that carry an explicit time. Take the 10 most recent date-only activities. Find each one in your timeline and metric output. Any date-only activity shown with a time of day, or on the previous day, is a gap.

Passes ifActivities flagged as date-only show as date-only in your timelines and metrics. No date-only activity shows with a time of day or on the previous day.

Access needed:crm-read

If it fails: changes to make later (not part of the check)
  1. 01Store an activity's date and time separately, with a flag when the time is unknown.
  2. 02Display a date-only activity as a date with no time zone shift, never as midnight UTC.
  3. 03Rank an activity's own recorded time above any fallback time when sorting.
  4. 04Count date-only activities per source before trusting any time-of-day metric.
Applies ifYou back-fill email activity as CRM tasks, or build timelines and response-time metrics from tasks and events across time zones.

← Back to the stream

For your agent

Each post has a read-only check your agent can run against your own setup. Paste this into a read-only session:

Never asks your agent to change anything · send anything anywhere · fetch other pages · run code · read something you can't.

What each rule means, and how it's enforced
  • Change anything. Every check is a question answered by reading. Each one names what it reads. The steps under “If it fails” are for you to weigh later, never part of a check.
  • Send anything anywhere. No post asks an agent to email, post, submit, upload or report back. Your results stay with you; sharing them is your call.
  • Fetch other pages. Post text carries no links, and no post tells an agent to visit one. The only URLs in the feed point to this site's own post pages.
  • Run code. Snippets are illustrations, not commands.
  • Read something you can't. posts.json is generated from this page, field for field. Nothing is hidden from a human reader.

A gate enforces these rules before every publish: it refuses links, instructions aimed at an agent, write verbs inside a check, hidden Unicode characters and any check without an "access needed" line. Each published version carries a version number and a sha256 fingerprint, so you can pin the version you reviewed. Every post is reviewed by a person before it goes out.

Feed version 1.0 · 2026-11-16 · sha256 88d19978389827b7…

Found something that breaks these rules? Tell me on LinkedIn.