> For the complete documentation index, see [llms.txt](https://developer.harness.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://developer.harness.io/feature-management-experimentation/new-to-fme/get-started/send-event-data.md).

# Send Event Data

Measure the impact of your feature rollout on your customer experience by sending Split event data and calculating metrics based on those events. Events allow you to record any actions your users perform and experiences your users encounter, such as response times or errors.

Event data can be sent to Split in one of four ways:

* Install Split's [RUM Agent](/feature-management-experimentation/new-to-fme/sdks-and-customer-deployed-components/client-side-agents/android-rum-agent.md) or [Split Suite](/feature-management-experimentation/new-to-fme/sdks-and-customer-deployed-components/client-side-sdk-suites/android-suite.md) which will auto-collect performance event data when installed in a client-side application
* Call Split's SDK `track` method (example below) to explicitly add instrumentation code to your application to record events
* Post a JSON body to Split's [Events API](https://docs.split.io/reference/introduction#events-overview) to ingest events data from existing sources
* Split integrations with [Segment](/feature-management-experimentation/management-and-administration/integrations/segment.md), [mParticle](/feature-management-experimentation/management-and-administration/integrations/mparticle.md), [Sentry](/feature-management-experimentation/management-and-administration/integrations/sentry.md), [Amazon S3](/feature-management-experimentation/management-and-administration/integrations/amazon-s3.md), or [Google Analytics](/feature-management-experimentation/management-and-administration/integrations/google-analytics.md) to ingest events data from existing sources

Below is an example of calling the track method of the SDK in JavaScript. See links above for the API and integration routes.

```javascript
// parameters
var queued = client.track('TRAFFIC_TYPE', 'EVENT_TYPE'), eventValue);
// Example
var queued = client.track('user', 'page_load_time', 83.334)
```

Learn more in the track section of each SDK reference guide ([JavaScript example](/feature-management-experimentation/new-to-fme/sdks-and-customer-deployed-components/client-side-sdks/client-side-standard-sdks/javascript-sdk.md#track)).

To verify that events are being received by Harness FME, navigate to the **Event types** tab on the **Data Hub** from the FME navigation menu.

![](/files/07vhoD1iBqzDk9bpUpTA)

You can see event types and a stream of events per event type. For more information about events, see [Events](/feature-management-experimentation/use-fme/release-monitoring/events/index.md).

For an interactive onboarding experience including further use cases and features like \*\*events\*\*, \*\*metrics\*\*, and \*\*monitoring and alerting\*\*, check out the \[\*\*Harness Feature Management & Experimentation Advanced Feature Flagging for Engineers certification\*\*]\(<https://university-registration.harness.io/fme-level-2-advanced-feature-flagging-for-engineers>).