Fixing links to tracking section in docs (#10326)
This commit is contained in:
parent
bfcba3f560
commit
915c4ea476
2 changed files with 2 additions and 2 deletions
|
|
@ -40,7 +40,7 @@ an `Ahoy::Visit` for the event being tracked.
|
|||
|
||||
Events can be tracked in a controller action on the backend, or with JavaScript
|
||||
on the frontend. Learn more about tracking events with JavaScript in our
|
||||
[frontend tracking guide](../frontend/tracking.md).
|
||||
[frontend tracking guide](/frontend/tracking).
|
||||
|
||||
When an event is tracked, it should include a `name` and a `properties` hash.
|
||||
When adding new events, be sure that the name is unique per-event. The
|
||||
|
|
|
|||
|
|
@ -7,7 +7,7 @@ title: Tracking
|
|||
For first-party analytics, we use the
|
||||
[`ahoy.js` library](https://github.com/ankane/ahoy.js), which tracks visits and
|
||||
events. This library works in conjunction with the `ahoy_matey` gem, which is
|
||||
documented in our [backend tracking guide](../backend/tracking.md).
|
||||
documented in our [backend tracking guide](/backend/tracking).
|
||||
|
||||
### Configuration
|
||||
|
||||
|
|
|
|||
Loading…
Add table
Reference in a new issue