> For the complete documentation index, see [llms.txt](https://docs.chord.co/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.chord.co/chord-oms/chord-storefront-event-tracking/event-tracking-faq.md). # Event Tracking FAQ ### Can I send custom events from my website front-end? Yes, you can send any events to Segment using the global `analytics` object from Segment's [Analytics.js library](https://segment.com/docs/connections/sources/catalog/libraries/website/javascript/). See the documentation on [`analytics.track()`](https://segment.com/docs/connections/sources/catalog/libraries/website/javascript/quickstart/). You can't currently use Chord's JavaScript SDKs to send custom events. If you would like to take advantage of Protocols Tracking Plan features, such as validation, you can add your custom events to your Protocols Tracking Plan. It won't impact Chord's tracking as long as you don't alter existing events. ### Can I customize events sent by the Chord SDK? You can customize Segment events from the Chord SDK with [Segment middleware](https://segment.com/docs/connections/sources/catalog/libraries/website/javascript/middleware/). This strategy allows you to intercept events after they're sent by the SDK and add properties. We don't support changing existing properties, because Chord models the data received in events, but this is a good strategy for adding additional properties to existing events. ### How does Chord send events to Segment? When you use the Chord SDK in your website code, it sends events to Segment with Segment's [Analytics.js library](https://segment.com/docs/connections/sources/catalog/libraries/website/javascript/). Internally, the Chord SDK uses a [Typewriter client](https://segment.com/docs/protocols/apis-and-extensions/typewriter/) generated from Chord's Protocols Tracking Plan. The Chord OMS sends events to Segment with Segment's [Ruby library](https://segment.com/docs/connections/sources/catalog/libraries/server/ruby/). ### How does Chord use cookies? Chord uses cookies that are essential for the site to function and cannot be disabled via Segment’s Consent Manager. A user can always disable all cookies in their browser settings, but the site may not work as intended. For example, we use cookies to remember your shopping cart when you return to our site. When you log into your user account, we use cookies to authenticate you and secure your subsequent interactions. Other cookies may be used by third party integrations, typically configured via Segment. --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://docs.chord.co/chord-oms/chord-storefront-event-tracking/event-tracking-faq.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.