---
title: "Device ID"
slug: "device-id"
updated: 2026-04-21T13:49:01Z
published: 2026-04-21T13:49:01Z
canonical: "help.yahooinc.com/device-id"
---

> ## Documentation Index
> Fetch the complete documentation index at: https://help.yahooinc.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Device ID Audiences

> [!WARNING]
> Important
> 
> The Device ID Audiences endpoint is scheduled for future removal. This endpoint is being replaced by the `customsegments` [endpoint](/dsp-api/docs/custom-audiences).

Device ID audiences are audiences made up of Apple iOS Identifier for Advertising (IDFA) IDs, or Google Play Advertising IDs (GPADVIDs) that you provide. After you create a device ID audience, you can target the audience at the line level.

## Hierarchy

You define a `Device ID` audience at the advertiser level.

## Endpoint

```plaintext
/traffic/audiences/device_id
```

Use the following HTTP methods:

- Use the `GET` method to read an existing device ID audience.
- Use the `POST` method to create a new device ID audience.
- Use the `PUT` method to update an existing device ID audience.

## Resources

The `Device ID` audience object contains the following fields:

| **Field** | **Description** | **Data Type** | **Create** | **Update** |
| --- | --- | --- | --- | --- |
| `id` | Specifies the audience ID. | `integer` | N/A | Required |
| `name` | Specifies the name of the audience. | `string` | Required | Optional |
| `status` | Specifies the current status of the audience. Allowed values: - `ACTIVE`: you can target the audience. - `INACTIVE`: you cannot target the audience. Defaults to `ACTIVE` if you don’t specify a value. | `string` | Optional | Optional |
| `accountId` | Specifies the advertiser ID. An audience is tied to its advertiser and you can only use it in that advertiser’s campaigns. To learn more, refer to [Advertisers](/dsp-api/docs/advertisers). | `integer` | Required | Required |
| `retentionDays` | Specifies the number of days custom audience data is retained. Allowed values: - `30` - `60` - `90` - `180` Defaults to `180` if a value is not selected. | `integer` | Optional | Optional |
| `seedList` | Specifies an array of device IDs. Limit is 50K items per request. | `array` | Required | Optional |
| `seedListType` | Specifies the types of devices you can include. Allowed values: - `IDFA`: Apple (IDFA). - `GPADVID`: Google (GPADVID) | `array` | Required | Optional |
| `isDeviceOnly` | Enables or disables cross-device support. If you enable cross-device support, Yahoo DSP links cookie and mobile device identifiers deterministically at a person level and probabilistically at a household level. Disabling cross-device support turns off device linked cookies and restricts targeting to the seed audience that you have uploaded or collected using a pixel. If you disable cross-device targeting, you disable the deterministic and probabilistic cross-device linkages that occur both when you create the segment and when you target it. - `true`: disables cross device support. - `false`: enables cross device support. Defaults to `false` if you don’t specify a value. | `boolean` | Optional | Optional |
| `createdAt` | A read-only field that specifies when the audience was created. | `string` | N/A | N/A |

## Read Audience

Read a specific device ID audience.

```plaintext
GET /traffic/audiences/device_id/{id}?accountId={accountId}
```

### Parameters

| **Parameter** | **Parameter Type** | **Description** | **Data Type** | **Required** |
| --- | --- | --- | --- | --- |
| `id` | path | Specifies the audience ID. | `integer` | Y |
| `accountId` | query | Specifies the advertiser ID. | `integer` | Y |

### Sample Request URL

```plaintext
GET https://dspapi.admanagerplus.yahoo.com/traffic/audiences/device_id/51525777?accountId=1406321
```

### Sample Response

```plaintext
{
  "response": {
    "status": "ACTIVE",
    "id": 51525777,
    "name": "dev_id_56",
    "accountId": 1406321,
    "createdAt": "2020-02-01",
    "isDeviceOnly": false,
    "retentionDays": 180
  },
  "errors": null,
  "timeStamp": "2020-02-01T05:12:41.049Z"
}
```

## Create Audience

Create a new device ID audience.

```plaintext
POST /traffic/audiences/device_id
```

### Parameters

All fields are specified in the body of the `application/json` payload.

### Sample Request URL

```plaintext
POST https://dspapi.admanagerplus.yahoo.com/traffic/audiences/device_id
```

### Sample Request Body

```plaintext
{
  "name": "test_device_id",
  "status": "ACTIVE",
  "accountId": 1406321,
  "retentionDays": 180,
  "seedList": [
    "34A668B2-03CF-11E5-8418-1697F925EC7B",
    "34a66c5e-03cf-11e5-8418-1697f925ec7b"
  ],
  "seedListType": "GPADVID"
}
```

### Sample Response

```plaintext
{
  "response": {
    "status": "ACTIVE",
    "id": 51525777,
    "name": "test_device_id",
    "accountId": 1406321,
    "createdAt": "2020-02-01",
    "isDeviceOnly": false,
    "retentionDays": 180
  },
  "errors": null,
  "timeStamp": "2020-02-01T05:12:41.049Z"
}
```

## Update Audience

Update an existing device ID audience.

```plaintext
PUT /traffic/audiences/device_id/{id}
```

Partial updates are supported; values of supported fields that are not in the payload remain unchanged.

> [!NOTE]
> Note
> 
> Additional Device IDs may be appended to the audience using the `PUT` operation.

### Parameters

The audience `id` is specified in the endpoint path. All other fields are specified in the body of the `application/json` payload.

### Sample Request URL

```plaintext
PUT https://dspapi.admanagerplus.yahoo.com/traffic/audiences/device_id{id}
```

### Sample Request Body

```plaintext
{
  "name": "test_device_id-2",
  "accountId": 1406321
}
```

### Sample Response

```plaintext
{
  "response": {
    "status": "ACTIVE",
    "id": 51525777,
    "name": "test_device_id-2",
    "accountId": 1406321,
    "createdAt": "2020-02-01",
    "isDeviceOnly": false,
    "retentionDays": 180
  },
  "errors": null,
  "timeStamp": "2020-02-01T05:12:41.049Z"
}
```

## Delete Audience

The DSP Traffic API does not support the deletion of device ID audiences.