Skip to content

Update troubleshooting.md #7099

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 2 commits into from
Oct 1, 2024
Merged

Update troubleshooting.md #7099

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
81a4ea9
Update troubleshooting.md
prigiattiperrut Oct 1, 2024
d5a5d22
Apply suggestions from code review
forstisabella Oct 1, 2024
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
4 changes: 4 additions & 0 deletions src/connections/sources/catalog/libraries/website/javascript/troubleshooting.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -129,6 +129,10 @@ If you're having issues with your destinations loading with Prototype.js, there

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.

## Why do I see events with timestamps in the past or future?

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).

## Known issues:

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