---
title: WHO Targets in Omnichannel Experiences
slug: engine-api/who-targets
description: How to include targeting data such as IP address and user agent in a Monetate Engine API request
image:  https://archbee-image-uploads.s3.amazonaws.com/ceIfEvQHzQk1IVxoRWUh7/K9eTL4jKm7UQINb6zNziJ-20250912-181225.png
docTags: 
createdAt: 2024-05-16T11:43:50.288Z
---

Omnichannel experiences support most [WHO targets](https://docs.monetate.com/docs/types-of-who-targets) that you can use in an experience built for a [Monetate JavaScript API](docId\:ZFxS45Ymf6aIcWwKKgXcC) implementation, with the exception of a few that rely on data specific to Monetate tag–based integrations.

In an Engine API implementation, information such as IP address, used to determine the location and related information, and user agent, from which device type and operating system are derived, aren't available to Monetate and must be provided in the body of the Engine API request, as shown in this example.

:::CodeblockTabs
Example Engine API Request with Events for User Agent and IP Address

```json
{
"channel": "a-927c8120/p/example.com",
"monetateId": "5.275061469.1543777025730",
"events": [
    {
      "eventType": "monetate:decision:DecisionRequest",
      "requestId": "11111",
      "includeReporting": true
    },
    {
      "eventType": "monetate:context:UserAgent",
      "userAgent": "Mozilla/5.0 (Macintosh; Intel Mac OS X 10_13_6) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/70.0.3538.102 Safari/537.36"
    },
    {
      "eventType": "monetate:context:IpAddress",
      "ipAddress": "198.51.100.0"
    }
  ]
}
```
:::