Skip to content

Commit f95a02d

Browse files
Merge pull request #7099 from segmentio/prigiattiperrut-patch-5
Update troubleshooting.md
2 parents 12e25f9 + d5a5d22 commit f95a02d

File tree

1 file changed

+4
-0
lines changed

1 file changed

+4
-0
lines changed

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

Lines changed: 4 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -129,6 +129,10 @@ 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 do I see events with timestamps in the past or future?
133+
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).
135+
132136
## Known issues:
133137

134138
[Review and contribute to these on GitHub](https://github.com/segmentio/analytics.js/issues).

0 commit comments

Comments
 (0)