Skip to content
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

Jump to bottom

Fix typo #8982

Merged
merged 1 commit into from
Jul 17, 2024
Merged

Fix typo #8982

Changes from all commits
Commits
Show all changes
1 commit
Select commit
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: 2 additions & 2 deletions contents/docs/getting-started/send-events.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -88,7 +88,7 @@ A second reason why Custom events become important is for keeping tracking consi
When elements of your frontend change, this can affect how autocapture events show up in PostHog.
Continuing with the example above, if we changed the text for our add to cart button to just 'Add', our autocapure events would begin showing up as `Clicked button with text 'Add'` instead of what they had previously been.

While combining these two events using [Actions](/manual/actions) to fix this drift is possible, manually track these high-value actions with custom events is far more reliable.
While combining these two events using [Actions](/manual/actions) to fix this drift is possible, manually tracking these high-value actions with custom events is far more reliable.

## 3. Capture backend events

Expand Down Expand Up @@ -125,4 +125,4 @@ That said, we strongly recommend tracking the following events from the server-s

It's a priority for us that events are fully processed and saved as soon as possible. Typically, events will be usable in queries within a few minutes.

> **Further reading**: [How event ingestion works](/docs/how-posthog-works/ingestion-pipeline)
> **Further reading**: [How event ingestion works](/docs/how-posthog-works/ingestion-pipeline)