# Conversions

Send orders to Awin through its Conversion API from your backend, credited to the publisher by the awc click id or a voucher code.

`POST /v1/events` sends your orders to Awin's Conversion API. The destination is the connection's advertiser id.

## Send a conversion event

Name the Awin account and its advertiser id. Send the `awc` from the publisher's click, the order's value and its currency:

```bash
curl -X POST "https://zernio.com/api/v1/events" \
  -H "Authorization: Bearer $ZERNIO_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
    "profileId": "PROFILE_ID",
    "destinations": [{ "accountId": "ACCOUNT_ID", "destinationId": "123456" }],
    "events": [{
      "eventName": "Purchase",
      "eventTime": 1798804800,
      "eventId": "order_12345",
      "value": 25.99,
      "currency": "EUR",
      "user": { "clickIds": { "awc": "AWC_FROM_THE_CLICK" } }
    }]
  }'
```

To send every purchase to Awin without naming it each time, create a [forwarding rule](/conversions/create-forwarding-rule) for the account instead.

## Event names

`eventName` is not sent: every order goes to Awin's `DEFAULT` commission group with its full `value`. Send `platformData.commission_group` to use another group.

Awin pays publishers for every order, so these are never sent: `PageView`, `ViewContent`, `Search`, `AddToCart`, `AddToWishlist`, `InitiateCheckout`, `AddPaymentInfo`. A rule turned on in the dashboard sends `Purchase` only.

## Match keys

Each order needs at least one of these:

| Field | Sent as |
|-------|---------|
| `user.clickIds.awc` | `awc`. The best match |
| `platformData.voucher` | `voucher`, for voucher code attribution |

No email, phone or other personal data is sent.

The [Zernio tag](/products/server-side-tracking/script) keeps `awc` from the landing URL. Send the visitor id, or the customer's email, phone or external id, and your backend events get it too.

## What else is sent

- `value` as the order amount (after discounts, before tax) and `currency`. Both are required: send a value of 0 for a lead.
- `platformData.order_id`, or else `eventId`, is the `orderReference`, up to 50 characters. Awin dedups on it.

## Consent

- On profiles created since 22 November 2026, an order from the EEA, UK or Switzerland is sent only with `adUserData` granted and no ad signal denied.
- In the EEA, UK and Switzerland the tag keeps `awc` only after the visitor accepts ad cookies. See [Consent](/products/server-side-tracking/consent).

## Test mode

`testCode` sends the order with Awin's `isTest`: it reaches Awin and is not tracked or paid.

## How it behaves

- One order per request, three at a time, so a refused order never fails the others.

## If it fails

| Error | Cause | Fix |
|-------|-------|-----|
| `Awin needs the awc click id (or a voucher code) to credit a publisher.` | No way to credit a publisher | Send `awc` or `platformData.voucher`. |
| `Awin needs the value and currency of every order (a value of 0 for a lead).` | `value` or `currency` is missing | Send both. |
| `Awin order references are at most 50 characters.` | `order_id` or `eventId` is too long | Shorten it. |
| `Awin pays partners for every conversion it gets, so "…" (a browsing or funnel step) is not sent.` | A funnel event reached Awin | Forward only orders to Awin. |
| `destinationId must be this connection's Awin advertiser id` | Another id was sent | Use the id from `GET /v1/ads/conversions/destinations`. |
| `401` with `reconnect_required` | Awin refused the saved key | [Connect again](/platforms/awin/connect) with a key from API credentials. |

## Related

- [Send events](/conversions/send-events)
- [Create a forwarding rule](/conversions/create-forwarding-rule)
- [Consent](/products/server-side-tracking/consent)
- [Limits and errors](/platforms/awin/reference)