# Conversions

Send your conversions to Campaign Manager 360 Floodlight activities through Google's Data Manager API, credited by gclid or dclid.

`POST /v1/events` sends your conversions to a Floodlight activity through Google's Data Manager API. Campaign Manager 360 is coming soon: see [Connect](/platforms/campaign-manager-360/connect).

## Send a conversion event

List the account's Floodlight activities with `GET /v1/ads/conversions/destinations`, then name one as the destination. Every event needs the ad click behind it:

```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": "8765432:12345678" }],
    "events": [{
      "eventName": "Purchase",
      "eventTime": 1798804800,
      "eventId": "order_12345",
      "value": 25.99,
      "currency": "USD",
      "user": {
        "email": "customer@example.com",
        "clickIds": { "dclid": "DCLID_FROM_THE_CLICK" }
      },
      "consent": { "adUserData": "GRANTED", "adPersonalization": "GRANTED" }
    }]
  }'
```

The destination is `<floodlightConfigurationId>:<floodlightActivityId>`. To send every event without naming it each time, create a [forwarding rule](/conversions/create-forwarding-rule).

## Event names

`eventName` is ignored: the Floodlight activity sets what is counted. Send each kind of conversion to its own activity.

## Match keys

| Field | Sent as |
|-------|---------|
| `user.clickIds.gclid`, `user.clickIds.dclid` | As is. One of them is required |
| `user.email` | Hashed, Gmail addresses normalized first |
| `user.phone` | Hashed |
| `firstName`, `lastName`, `country`, `zip` | One hashed address, only when all four are present |
| `ipAddress`, `userAgent` | As is |

An email or phone only enhances the click: it never replaces it. Hashed email or phone need the advertiser to accept the enhanced conversions terms.

The Zernio site tag captures `dclid` from the landing URL. Send the Zernio visitor id as `user.visitorId` and Zernio adds it to your backend events.

## How it behaves

- **Value.** `value` and `currency` are sent as the conversion value. `items`, `externalId` and the other click ids are ignored.
- **Dedup.** `eventId` is sent as `transactionId`. Floodlight keeps one conversion per `eventId` and activity.
- **Test mode.** `testCode` makes Google validate the events without recording them.
- **Consent.** `adUserData` and `adPersonalization` are passed to Google. On a profile with consent first, an event from the EEA, the UK or Switzerland is sent only when `adUserData` is granted and no ad signal is denied. See [Consent](/products/server-side-tracking/consent).
- **Batches.** Events go out in batches of up to 2,000.

## If it fails

| Error | Cause | Fix |
|-------|-------|-----|
| `Campaign Manager 360 needs the ad click behind the conversion` | The event has no `gclid` or `dclid` | Send one of them. |
| `destinationId must be "<floodlightConfigurationId>:<floodlightActivityId>"` | The destination is not in that form | Copy it from `GET /v1/ads/conversions/destinations`. |
| `This Google user cannot send conversions to Floodlight configuration …` | The connected user has no access to that configuration | Give it access in Campaign Manager 360, or reconnect with a user who has it. |
| `401` with `reconnect_required` | Google no longer accepts the connection | [Connect again](/platforms/campaign-manager-360/connect). |

## Related

- [Send events](/conversions/send-events)
- [List conversion destinations](/conversions/list-ad-conversion-destinations)
- [Create a forwarding rule](/conversions/create-forwarding-rule)
- [What each platform gets](/products/conversions-api/platforms)