# Harness FME Cloud Mode Integration

After you have successfully instrumented Harness FME (formerly Split.io) as a destination in RudderStack, follow this guide to correctly send your events to Harness FME in [cloud mode]({{< ref "/destinations/rudderstack-connection-modes.md#cloud-mode" >}}).

Find the open source transformer code for this destination in the [GitHub repository](https://github.com/rudderlabs/rudder-transformer/tree/main/src/v0/destinations/splitio).

## Identify

The [`identify`]({{< ref "event-spec/standard-events/identify.md" >}}) method lets you identify a user and associate them to their actions. It also lets you record any traits about them like their name, email, etc.

A sample `identify` call is shown below:

```javascript
rudderanalytics.identify("1hKOmRA4GRlm", {
  name: "Alex Keener",
  email: "alex@example.com",
  plan: "GOLD",
  age: 40,
})
```

## Track

You can use the [`track`]({{< ref "event-spec/standard-events/track.md" >}}) call to capture user events and the associated properties.

A sample `track` call is shown below:

```javascript
rudderanalytics.track("Clicked button", {
  color: "red",
  buttonText: "Get started",
})
```

RudderStack sends the above `track` call as a `Clicked_button` event to Harness FME along with the event properties.

Note that the event name (`Clicked button` in the above example) in the `track` event should:

- Start with a letter or number.
- Contain 80 characters or less.
- Contain only letters, numbers, hyphen, underscore, or period.

## Page

The [`page`]({{< ref "event-spec/standard-events/page.md" >}}) event lets you record your website's page views with any additional information about the viewed page.

A sample `page` call is shown below:

```javascript
rudderanalytics.page("homepage", "home", {
  url: "https://abc.com",
  title: "Test",
  referrer: "https://google.com",
})
```

RudderStack sends the above `page` call as a `Viewed_home_page` event to Harness FME, along with the associated properties.

## Screen

The [`screen`]({{< ref "event-spec/standard-events/screen.md" >}}) call lets you record whenever your user views their mobile screen, with any additional relevant information about the screen.

A sample `screen` call is shown below:

```javascript
[[RSClient sharedInstance] screen:@"Main" properties:@{@"prop_key" : @"prop_value"}];
```

The above snippet captures information related to the viewed screen such as its name and category. RudderStack sends this call as a `Viewed_Main_screen` event with the associated properties.

## Group

The [`group`]({{< ref "event-spec/standard-events/group.md" >}}) call lets you link an identified user with a group like a company, organization, or an account. You can also record any custom traits associated with that group like the company name, number of employees, etc.

A sample `group` call is shown below:

```javascript
rudderanalytics.group("group123", {
  company: 'Sample Company',
});
```

## Specify traffic type in events

You can specify the Harness FME traffic type in your events as follows:

```javascript
rudderanalytics.identify("1hKOmRA4GRlm", {
  name: "Alex Keener",
  email: "alex@example.com",
  plan: "GOLD",
  age: 40,
  trafficTypeName: "account"
})
```

{{< info >}}
Note that:
- RudderStack automatically maps the `trafficTypeName` field present in your `traits`/`context.traits`/`properties` object to Harness FME's `trafficTypeName` field.
- The traffic type name specified at the event level takes precedence over the [Traffic Type]({{< ref "destinations/streaming-destinations/split/setup-guide.md#connection-settings" >}}) dashboard setting.
{{< /info >}}

<br />