Basic Context Objects

Every Semantic Event is enriched with a set of standardized context objects. These objects provide a wealth of information about the environment in which the event occurred, such as the user's device, operating system, and application details. Understanding these objects is key to unlocking the full analytical power of your event stream.

Much of this context is captured automatically by the Jitsu client library, reducing the amount of manual instrumentation required. For the core event properties that work alongside these context objects, see Core Properties. Below is a breakdown of the most common context objects and their properties.

The App Object

Contains details about the application that generated the event, typically a mobile app.

Property	Description	Provided By
`name`	The name of the app (e.g., "MyShop App").	Auto-Populated
`version`	The version of the app (e.g., "1.2.0").	Auto-Populated
`build`	The build number of the app (e.g., "1024").	Auto-Populated
`namespace`	The namespace of the app (e.g., "com.myshop.app").	Auto-Populated

The Device Object

Captures information about the user's device.

Property	Description	Provided By
`id`	A unique identifier for the device instance.	Auto-Populated
`manufacturer`	The manufacturer of the device (e.g., "Apple").	Auto-Populated
`model`	The model of the device (e.g., "iPhone 14 Pro").	Auto-Populated
`name`	The user-assigned name of the device.	Auto-Populated
`type`	The type of device (e.g., "mobile", "tablet").	Auto-Populated
`ad_tracking_enabled`	A boolean indicating if ad tracking is on.	Auto-Populated
`advertising_id`	The device's advertising identifier (IDFA/GAID).	Auto-Populated

The OS Object

Details about the operating system of the device.

Property	Description	Provided By
`name`	The name of the OS (e.g., "iOS").	Auto-Populated
`version`	The version of the OS (e.g., "16.5.1").	Auto-Populated

The Page Object

For web events, this object contains information about the page being viewed.

Property	Description	Provided By
`url`	The full URL of the page.	Auto-Populated
`path`	The path portion of the URL (e.g., "/pricing").	Auto-Populated
`referrer`	The URL of the page that referred the user.	Auto-Populated
`title`	The `<title>` of the page.	Auto-Populated
`search`	The query string portion of the URL.	Auto-Populated

The Screen Object

For mobile events, this object details the screen being viewed.

Property	Description	Provided By
`name`	The name you provide for the screen.	User-Provided
`height`	The height of the screen in pixels.	Auto-Populated
`width`	The width of the screen in pixels.	Auto-Populated
`density`	The pixel density of the screen.	Auto-Populated

The Campaign Object

Captures marketing campaign information, typically from URL parameters.

Property	Description	Provided By
`name`	The name of the campaign (from `utm_campaign`).	Auto-Populated
`source`	The source of the traffic (from `utm_source`).	Auto-Populated
`medium`	The medium of the campaign (from `utm_medium`).	Auto-Populated
`term`	The keyword for the campaign (from `utm_term`).	Auto-Populated
`content`	The specific ad content (from `utm_content`).	Auto-Populated

Event Enrichment Example

The true power of the context objects comes from automatic enrichment. A simple track event sent from the client becomes a rich, detailed record on the server.

Event as Sent by the User (Client-Side)

Here is a track event for a user adding a product to their cart. Notice how little information the developer needs to provide manually.

JSON

json

1{
2"type": "track",
3"event": "Product Added",
4"userId": "user-9b8d7c",
5"properties": {
6"cart_id": "cart-a1b2c3",
7"product_id": "prod-f4g5h6",
8"sku": "SKU-BLK-LG",
9"price": 49.99,
10"quantity": 1
11}
12}

Event After Auto-Population (Server-Side)

After the event is received, it is enriched with the context objects. The final event stored is much more detailed, providing a complete picture of the interaction without extra work from the developer.