Wendung.step(): Record and queue a named user event

Call Wendung.step() anywhere in your application to record a named event. The event is queued and flushed automatically: on the next timer tick, when the queue reaches the effective batch size, or when the page hides or unloads. Each event gets a unique id (crypto.randomUUID()), an ISO 8601 timestamp taken at call time, and a snapshot of the current session ID, identity, and page context. Throws if called before init().

Wendung.step(name: string, properties?: Record<string, unknown>): void

Parameters

string

required

The event name, 1–100 characters. Use a consistent convention, for example snake_case pairs like page_view or checkout_completed. If the name is empty or too long, the call is ignored and a [Wendung - Warning] is logged; nothing is thrown.

Record<string, unknown>

Optional metadata, sent as events[].properties. Must be a plain object with JSON-serializable values; it is deep-cloned at call time. If a non-plain value is passed (array, class instance, Map), the call is ignored and a warning is logged. To include array data, nest it under a key.

Returns

void

Examples

Simple event

Wendung.step('page_view')

Event with properties

Wendung.step('export_clicked', {
  format: 'csv',
  rowCount: selectedRows.length,
})

You do not need to call flush() after step(). The SDK batches and sends automatically; manual flushing is only useful when you want a send attempt to settle before something like an external redirect.

SDK Methods

Types

Wendung.step(): Record and queue a named user event

Parameters

Returns

Examples

Simple event

Event with properties

​Parameters

​Returns

​Examples

​Simple event

​Event with properties

Parameters

Returns

Examples

Simple event

Event with properties