Sending custom events

The Track method lets you record custom events end users take in your application using an event key.

Here’s how:

1
client.Track("event-key-123abc");

You can also attach custom data to your event by passing an extra parameter to Track, using the LdValue class to represent any value that can be encoded in JSON. To learn how, read LdClient.Track.

The track method lets you record custom events end users take in your application using an event key. You can also attach custom JSON data to your event by passing an extra JsonElement parameter to track.

Here’s how:

1
client.track("event-key-123abc", data);

To learn more, read track.

You can also attach custom data to your event by calling TrackData or TrackMetric.

The Track method lets you record custom events end users take in your application using an event key.

Here’s how:

1
client.Track("event-key-123abc");

To learn more, read Track.

The track function lets you record custom events in your application with LaunchDarkly using an event key.

Here’s how:

1
client.track('event-key-123abc', { customProperty: someValue });

The track method lets you record custom events end users take in your application using an event key. You can also attach custom data to your event by passing an extra LDValue parameter or num parameter to track.

Here’s how:

1
client.track('event-key-123abc', data: LDValue.objectBuilder().addBool("clicked-button", true).build());

To learn more, read track.

The track method lets you record custom events end users take in your application using an event key.

In the iOS SDK, track is a custom event added to the LDClient event store. A client app can set a tracking event to allow client customized data analysis. After an app has called track, the app cannot remove the event from the event store. LDClient periodically transmits events to LaunchDarkly based on the frequency set in LDConfig.eventFlushInterval. The LDClient must be started and online.

After the SDK’s event store is full, the SDK discards new events until the event store is cleared when it reports events to LaunchDarkly. Configure the size of the event store using LDConfig.eventCapacity. The first parameter, key, is the key for the event. The SDK does nothing with the key, which can be any string the client app sends. The second parameter, data, is the data for the event. The data parameter is optional. The SDK does nothing with the data, which can be any valid JSON item as an LDValue instance.

Optionally, you can add a metricValue parameter of type Double to track in Swift or as a required parameter to the overloaded track method in Objective-C.

1
let data: LDValue = ["some-custom-key": "some-custom-value", "another-custom-key": 7]
2
try LDClient.get()!.track(key: "event-key-123abc", data: data)

To learn more, read the generated API documentation for Swift or Objective-C.

The track method lets you record custom events end users take in your application using an event key.

To call track:

1
client.track('event-key-123abc', { customProperty: someValue });

The second argument is optional. It assists with observational analytics for metrics or for Data Export destinations:

• If you define clicked or tapped conversion or page viewed conversion metrics in LaunchDarkly, the SDK sends them automatically after you have initialized the client. You do not have to do anything else with the client to send click or page view events. The SDK will generate page view events correctly regardless of how the URL is changed, such as by the HTML5 history API or by changing the URL hash fragment. To learn more about metrics, read Metrics.
• With Data Export, the second argument gives additional information without saving the data to the LaunchDarkly context. To learn more about Data export, read Data Export.

To learn how to attach custom data to your event with optional parameters, read track.

The track method lets you record custom events end users take in your application using an event key.

Here’s an example:

1
client.track('event-key-123abc');
2
3
client.track('event-key-456def', { someData: 2 });

To learn how to attach custom data to your event with optional parameters, read track.

The track method lets you record custom events end users take in your application using an event key. You can also attach custom JSON data to your event by passing an extra parameter to track.

Optionally, you can add a metricValue parameter to the track method if you are using the latest version of Experimentation.

Here’s how:

1
client.track('event-key-123abc', false);
2
client.track('event-key-456def', { someData: 'value' });

To learn how to attach custom data to your event with optional parameters, read track.

The track method lets you record custom events end users take in your application using an event key.

Here’s how:

1
' without optional data
2
launchDarkly.track("event-key-123abc")
3
4
' with optional data
5
launchDarkly.track("event-key-123abc", {"customField": 123})
6
7
' with optional numeric metric
8
launchDarkly.track("event-key-123abc", invalid, 52.3)

The Track method lets you record custom events end users take in your application using an event key.

Here’s an example:

1
client.Track("event-key-123abc", context);

You can also attach custom data to your event by passing an extra parameter to Track. To do this, use the LdValue type, which can contain any kind of data supported by JSON. You can also pass another parameter for a custom metric value.

The track method lets you record actions your users take in your you do application. You can also attach custom JSON data to your event by passing an LDValue parameter to track, or a custom metric value by passing a Double parameter.

Here’s how:

1
client.track(user, 'event-key-123abc', 52.3, LDValue.of('my value'));

To learn how to attach custom data to your event with extra parameters, read Other methods.

The Track method lets you record custom events end users take in your application using an event key. Optionally, you can include additional data associated with the event.

Here’s how:

1
/* track the event */
2
client.Track(context, "event-key-123abc");
3
4
/* track the event and associate data with it */
5
client.Track(context, "event-key-123abc", 42)

To learn more, read Track() in Client.

The track method lets you record custom events end users take in your application using an event key.

Here’s how:

ldclient:track(<<"event-key-123abc">>, #{key => <<"context-key-123abc">>}, #{data => <<"example">>})

To learn more, read track.

You can also attach a JSON object containing arbitrary data to your event, or a custom metric value. To learn how, read track_metric.

The Track method lets you record custom events end users take in your application using an event key.

In this example, we use TrackEvent to send an event with the key event-key-123abc.

Here’s how:

1
client.TrackEvent("event-key-123abc", context)

You can also attach custom data to your event by calling TrackData, which takes an extra parameter. Or, if you are using experimentation, you can specify a numeric metric with TrackMetric.

The track method lets you record custom events end users take in your application using an event key.

Here’s how:

1
track client context "event-key-123abc" Nothing Nothing

You can also attach a JSON object containing arbitrary data to your event, or a custom metric value. To learn how, read track.

The track method lets you record custom events end users take in your application using an event key.

Here’s how:

1
client.track("event-key-123abc", context);

You can also attach custom JSON data to your event with an alternate version of track, trackData. You can set the data to any value that can be represented in JSON. To learn more, read LDValue.

If you are using Experimentation, you can specify a numeric metric with trackMetric.

The track method lets you record custom events end users take in your application using an event key. Optionally, you can include additional data associated with the event.

Here’s how:

1
client:track("event-key-123abc", context);

You can also attach an object containing arbitrary data to your event. To learn how, read track.

The track method lets you record custom events end users take in your application using an event key.

Here’s how:

1
client.track('event-key-123abc', context);

You can also attach custom data to your event with optional parameters. To learn how, read track.

The track method lets you record custom events end users take in your application using an event key.

Here’s how:

1
$client->track("event-key-123abc", $context);

You can also attach custom data, including anything that can be marshaled to JSON, to your event by passing an extra parameter to track. To learn how, read track().

The track method lets you record actions end users take on your site. This lets you record events that take place on your server.

Here’s how:

1
ldclient.get().track("event-key-123abc", context)

You can also attach custom data to your event with optional parameters. To learn how, read track.

The track method lets you record custom events end users take in your application using an event key.

Here’s how:

1
client.track("event-key-123abc", context)

You can also attach an extra hash containing arbitrary data to your event. To learn how, read track.

The track method lets you record custom events end users take in your application using an event key.

In this example, we use track_event to send an event with the key event-key-123abc.

Here’s how:

1
client.track_event(context, "event-key-123abc");

You can also attach custom data to your event by calling track_data, which takes an extra parameter. Or, if you are using experimentation, you can specify a numeric metric with track_metric.

Sending events is available in Cloudflare SDK version 2.3.0 and later. You must explicitly enable sending events in your configuration.

The track method lets you record custom events end users take in your application using an event key.

Here’s how:

1
client.track('event-key-123abc', context);

You can also attach custom data to your event with optional parameters.

Here’s how:

1
const exampleData = { customProperty: 'someValue' };
2
const metricValue = 10;
3
4
client.track('event-key-123abc', context, exampleData, metricValue);

When you are working with an edge SDK, you must also call flush after sending any events:

1
executionContext.waitUntil(
2
  client.flush((err, res) => {
3
    console.log(`flushed events result: ${res}, error: ${err}`);
4
  }),
5
);

To learn more, read Flushing events.

Sending events is available in Vercel SDK version 1.2.0 and later. You must explicitly enable sending events in your configuration.

The track method lets you record custom events end users take in your application using an event key.

Here’s how:

1
client.track('event-key-123abc', context);

You can also attach custom data to your event with optional parameters.

Here’s how:

1
const exampleData = { customProperty: 'someValue' };
2
const metricValue = 10;
3
4
client.track('event-key-123abc', context, exampleData, metricValue);

When you are working with an edge SDK, you must also flush the events before your worker exits to ensure that they are sent back to LaunchDarkly. If you call flush inside the waitUntil method, then flushing events will not impact the handler’s response time. To learn more, read the Vercel documentation on waitUntil.

Here’s how:

1
context.waitUntil(
2
  client.flush((err, res) => {
3
    console.log(`flushed events result: ${res}, error: ${err}`);
4
  }),
5
);

To learn more, read Flushing events.