Server to Server

Jitsu supports event ingestion in server-to-server (S2S) mode.

The ingestion mode is determined by the type of Write Key used to configure the Jitsu client.

Unlike browser events, s2s events are processed differently:

• context.ip and context.userAgent are not extracted from the request headers, but should be passed explicitly in the event payload
• If context.ip is not present, the ip field will be empty to avoid confusion; same applies for context.userAgent

Strict mode

tip

Strict mode for S2S stream ensures that no third-party actor can inject events into your stream using publicly accessible information.

Jitsu Stream can be configured with Strict Mode enabled.

In Strict Mode, Jitsu requires a valid writeKey to ingest events into the current stream.

Without Strict Mode, if a correct writeKey is not provided, Jitsu may attempt to identify the stream based on the domain or, if there is only one stream in the workspace, it will automatically select that stream.