---
title: "Enable campaign piggybacks"
type: reference
method: POST
path: /rest-api/piggyback/campaign/enable.do
tag: "Piggybacks"
---

# Enable campaign piggybacks

`POST https://YOUR-NETWORK-DOMAIN/rest-api/piggyback/campaign/enable.do`

Enables all piggyback tracking pixels associated with the specified campaign so they begin firing during ad serving. This is a bulk operation that sets the piggyback status to ENABLED for every piggyback attached to the campaign. The caller must have update permissions on the campaign and the Piggyback Pixel Tracking permission. Returns a JSON object with a 'success' boolean. If the campaign does not exist, a 404 Not Found error is returned.

## Form params

| Name | Type | Required | Example | Description |
|---|---|---|---|---|
| `id` | integer | yes | `2001` | The unique numeric identifier of the campaign whose piggyback pixels should be enabled |

## Responses

- `200` — Campaign piggybacks enabled successfully
- `400` — Bad request — invalid or missing parameters
- `401` — Unauthorized - authentication error
- `403` — Forbidden - no rights on the campaign, or the Piggyback Pixel Tracking permission is not enabled
- `404` — Campaign not found
- `500` — Internal server error

## Example request

```bash
curl --request POST \
  --url 'https://YOUR-NETWORK-DOMAIN/rest-api/piggyback/campaign/enable.do' \
  --header 'X-Api-Key: YOUR_API_KEY' \
  --header 'Content-Type: application/x-www-form-urlencoded' \
  --data-urlencode 'id=2001'
```

Source: https://epom.com/ad-server/docs/api/piggybacks/post-piggyback-campaign-enable