---
title: "Set the custom parameter recording policy"
type: reference
method: POST
path: /rest-api/custom-parameter-policy.do
tag: "Custom Parameters"
---

# Set the custom parameter recording policy

`POST https://YOUR-NETWORK-DOMAIN/rest-api/custom-parameter-policy.do`

What reaches the analytics and conversion parameter logs: ANY records every custom parameter except the registered ones with recordInAnalytics false; ONLY_VERIFIED records only registered parameters with recordInAnalytics true. Targeting, macros and click/conversion forwarding never depend on it. Refused while the policy is LEGACY: move the Analytics configuration list first (custom-parameter-policy/adopt-legacy). Logs follow within a minute. Requires the CUSTOM_PARAMETERS admin permission (Admin → Targeting presets → Custom parameters).

## Form params

| Name | Type | Required | Example | Description |
|---|---|---|---|---|
| `policy` | string | yes | `ONLY_VERIFIED` | ANY or ONLY_VERIFIED |

## Responses

- `200` — {policy}
- `400` — policy is not ANY or ONLY_VERIFIED
- `401` — Authentication error
- `403` — Insufficient permissions, naming the missing one
- `409` — The Analytics configuration list still decides; adopt it first

## Example request

```bash
curl --request POST \
  --url 'https://YOUR-NETWORK-DOMAIN/rest-api/custom-parameter-policy.do' \
  --header 'X-Api-Key: YOUR_API_KEY' \
  --header 'Content-Type: application/x-www-form-urlencoded' \
  --data-urlencode 'policy=ONLY_VERIFIED'
```

Source: https://epom.com/ad-server/docs/api/custom-parameters/post-custom-parameter-policy