Send conversion events to an ad platform

Relay one or more conversion events to the target ad platform's native Conversions API. Supported platforms: Meta (metaads) via Graph API, Google Ads (googleads) via Data Manager API `ingestEvents`. Platform is inferred from the provided `accountId`. `destinationId` semantics differ per platform: - Meta: pixel (dataset) ID, e.g. "123456789012345" - Google: conversion action resource name, e.g. "customers/1234567890/conversionActions/987654321" Callers can list valid destinations via `GET /v1/accounts/{accountId}/conversion-destinations`. All PII (email, phone, names, external IDs) is hashed with SHA-256 server-side per each platform's normalization spec (including Google's Gmail-specific dot/plus-suffix stripping). Send plaintext. Requires the Ads add-on. Batching: Meta caps at 1000 events per request and rejects the entire batch if any event is malformed. Google caps at 2000. Both are handled automatically by chunking. Dedup: pass a stable `eventId` on every event. Meta uses it to dedupe against pixel events; Google maps it to transactionId.

curl -X POST "https://zernio.com/api/v1/ads/conversions" \  -H "Content-Type: application/json" \  -d '{    "accountId": "string",    "destinationId": "string",    "events": [      {        "eventName": "Purchase",        "eventTime": 1744732800,        "eventId": "order_abc_123",        "user": {}      }    ]  }'

{
  "platform": "metaads",
  "eventsReceived": 0,
  "eventsFailed": 0,
  "failures": [
    {
      "eventIndex": 0,
      "eventId": "string",
      "message": "string",
      "code": "string"
    }
  ],
  "traceId": "string"
}

{
  "error": "Unauthorized"
}