Skip to content

Commit d5a5d22

Browse files
Apply suggestions from code review
1 parent 81a4ea9 commit d5a5d22

File tree

1 file changed

+2
-2
lines changed

1 file changed

+2
-2
lines changed

src/connections/sources/catalog/libraries/website/javascript/troubleshooting.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -129,9 +129,9 @@ If you're having issues with your destinations loading with Prototype.js, there
129129

130130
Analytics.js generates a campaign object inside the context object whenever the URL contains search parameters. Without any UTM parameters, the campaign object remains empty.
131131

132-
## Why Are Events Received with Timestamps Set in the Past or Future?
132+
## Why do I see events with timestamps in the past or future?
133133

134-
Please see full details [here](https://segment.com/docs/connections/spec/common/#why-are-events-received-with-timestamps-set-in-the-past-or-future).
134+
You may see events with timestamp discrepancies due to manual overriding of the timestamp value, mobile apps closed or set in the background, traffic from bots, or inaccurate device or browser time. For more information, see Segment's [Common Fields Spec](/docs/connections/spec/common/#why-are-events-received-with-timestamps-set-in-the-past-or-future).
135135

136136
## Known issues:
137137

0 commit comments

Comments
 (0)