Event Tracking FAQ

Yes, you can send any events to Segment using the global analytics object from Segment's Analytics.js library. See the documentation on analytics.track(). 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.

You can customize Segment events from the Chord SDK with Segment 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.

When you use the Chord SDK in your website code, it sends events to Segment with Segment's Analytics.js library. Internally, the Chord SDK uses a Typewriter client generated from Chord's Protocols Tracking Plan. The Chord OMS sends events to Segment with Segment's Ruby library.

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.