---
title: "Get delivery accuracy per destination"
method: GET
path: "/v1/events/accuracy"
tags: ["Conversions"]
---

# Get delivery accuracy per destination

`GET /v1/events/accuracy`

## Request

- Base URL: `https://zernio.com/api`
- URL: `https://zernio.com/api/v1/events/accuracy`
- Auth: HTTP bearer

For each forwarding rule of a profile: what its destination received over a period, and how many of the profile's real sales reached it.

`deliveries` counts every event sent to the destination in the period, whatever its source, by the latest outcome of each. `accuracy` compares only sales: Shopify and WooCommerce orders and Stripe payments, as Elevar's Channel Accuracy does. Sales a rule leaves out by choice do not count against it.

Without `profileId` it covers every profile you can access. Requires the Ads add-on.

## Query parameters

- `profileId` string
- `period` 'today' | '7d' | '30d' | '90d'

## Response `200`

One entry per forwarding rule.

- object
  - `period` 'today' | '7d' | '30d' | '90d'
  - `destinations` object[]
    - `ruleId` string: The forwarding rule.
    - `profileId` string
    - `accountId` string
    - `platform` string: Ad platform, such as `metaads` or `googleads`.
    - `accountName` string
    - `destinationId` string
    - `sales` integer: Real sales in the period from the sources the rule takes.
    - `sent` integer: Sales a send was tried for.
    - `accepted` integer: Sales the platform accepted, by the latest attempt.
    - `failed` integer
    - `retrying` integer
    - `notSent` integer: Sales never sent: no ad consent, no identifier the platform matches on, or left out by the rule's event names.
    - `accuracy` number, nullable: `accepted / sent`, from 0 to 1. `null` with no sale sent.
    - `deliveries` object: Every event of any source the rule takes that had a send in the period, by the latest outcome of each.
      - `events` integer
      - `accepted` integer
      - `failed` integer
      - `retrying` integer
    - `match` object: The same events, and how many carried each identifier the platform matches people on.
      - `events` integer
      - `identified` integer: Events with at least one of the identifiers below.
      - `email` integer
      - `phone` integer
      - `externalId` integer
      - `clickId` integer
    - `matchRate` number, nullable: `match.identified / match.events`. `null` with nothing sent.

## Other responses

- `400`: Invalid request
- `401`: Missing or invalid API key. `code` is `missing_credentials` when no Authorization header was sent and `invalid_credentials` when the key is unknown, revoked or expired.
- `403`: No ads access on the account (`ads_addon_required`).

## Changes

- **2026-11-19** `6a265f2beba5`: 1 info
  - endpoint added

[Operation history](https://skmtc.dev/zernio/apis/zernio-api/changes/v1/events/accuracy/get.md)

---

[API](https://skmtc.dev/zernio/apis/zernio-api.md) - [All operations](https://skmtc.dev/zernio/apis/zernio-api/llms.txt) - [OpenAPI document](https://skmtc.dev/zernio/apis/zernio-api/revisions/988c032ae545?raw)
