Send conversion events
Relay one or more conversion events to the target ad platform's native Conversions API.
Platform is inferred from the provided accountId. Requires the Ads add-on.
Supported platforms:
- Meta (
metaads) via Graph API - Google Ads (
googleads) via Data Manager APIingestEvents - LinkedIn (
linkedinads) via/rest/conversionEvents - TikTok (
tiktokads) via the Offline Events API/offline/batch/— OFFLINE conversions only - OpenAI Ads (
openaiads) via its Conversions API (a separate host,bzr.openai.com)
destinationId semantics differ per platform:
- Meta: pixel (dataset) ID, e.g.
123456789012345 - Google: conversion action resource name, e.g.
customers/1234567890/conversionActions/987654321 - LinkedIn: conversion rule ID or URN, e.g.
104012orurn:lla:llaPartnerConversion:104012 - TikTok: Offline Event Set ID, e.g.
7057103914977558530 - OpenAI Ads: pixel wire id (numeric
pixel_id, distinct from the internal pixel id), as returned byGET /v1/accounts/{accountId}/conversion-destinations
TikTok notes: this path sends OFFLINE conversions (in-store / CRM / call-center), not web-pixel events. Each event must carry an email or phone (TikTok requires at least one). The connected TikTok ads account must have granted the Offline Events permission; older grants must reconnect.
OpenAI Ads notes: requires a tracking tag (pixel) to already exist on the account — returns 422
with code TRACKING_TAG_REQUIRED if POST /v1/accounts/{accountId}/tracking-tags hasn't been
called yet.
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. LinkedIn externalIds are passed through as plaintext per LinkedIn's spec;
only emails and phones are hashed.
For LinkedIn, the connected account must have been authorized after the Conversions API
rollout (i.e. the OAuth grant must include rw_conversions). Older accounts must reconnect.
Batching is handled automatically. Meta caps at 1000 events per request and rejects the entire batch if any event is malformed. Google caps at 2000. LinkedIn caps at 5000 and is also all-or-nothing per chunk. OpenAI Ads caps at 1000 per request; larger submissions are split into 1000-event chunks, each all-or-nothing (a malformed event fails every event in that chunk, not the whole request).
Dedup: pass a stable eventId on every event. Meta and LinkedIn use it to dedupe against
browser-side pixel/Insight Tag events; Google maps it to transactionId.
Per-platform eventName semantics:
- Meta: free-form. Standard names (Purchase, Lead, ...) match Meta's built-in events; custom strings are accepted.
- Google: ignored. The conversion action's category determines the event type. Send the standard name closest to your action for documentation, but the platform will not branch on it.
- LinkedIn: ignored. The conversion rule's
type(LEAD, PURCHASE, etc.) is locked to the destination at rule-creation time. Send the standard name for documentation; LinkedIn does not branch on it. - OpenAI Ads: a fixed subset of standard names (Purchase, Lead, AddToCart, ViewContent, InitiateCheckout, CompleteRegistration, Subscribe, StartTrial, Schedule) maps 1:1 onto OpenAI's own event-type enum; any other standard name or custom string is sent as
type: customwith the name preserved.
API key authentication - use your Zernio API key as a Bearer token
In: header
SocialAccount ID (metaads, googleads, linkedinads, tiktokads, or openaiads).
Platform destination identifier. For Meta, the pixel/dataset
ID. For Google, the conversion action resource name. For
LinkedIn, the conversion rule ID or full
urn:lla:llaPartnerConversion:{id} URN. For OpenAI Ads, the
pixel wire id.
1 <= itemsMeta test_event_code passthrough. Ignored by Google, LinkedIn, and OpenAI Ads.
Batch-level user consent. Required by Google for EEA/UK events under the Feb 2026 restrictions. On Meta, any DENIED flag enables Limited Data Use on every event in the batch (data_processing_options ["LDU"] with geolocation, country 0 / state 0); GRANTED or absent consent sends events with Meta's default processing. Ignored by LinkedIn.
Response Body
application/json
application/json
import Zernio from '@zernio/node';const zernio = new Zernio({ apiKey: process.env.ZERNIO_API_KEY });const { data } = await zernio.conversions.sendConversions({ body: { accountId: 'account_abc123', destinationId: 'destination_abc123', events: [ { eventName: 'Purchase', eventTime: 1744732800, eventId: 'order_abc_123', user: { email: 'user@example.com', phone: 'string', firstName: 'Example', }, }, ], },});console.log(data);{
"platform": "metaads",
"eventsReceived": 0,
"eventsFailed": 0,
"failures": [
{
"eventIndex": 0,
"eventId": "string",
"message": "string",
"code": "string"
}
],
"traceId": "string"
}{
"error": "Unauthorized"
}Remove associated campaigns DELETE
Remove one or more campaign associations from this conversion rule. Pass `adAccountId` and `campaignIds` as query parameters (`campaignIds` is comma-separated). The route also accepts a JSON body with the same fields for clients that prefer DELETE-with-body, but the documented surface is query-only because some SDK code generators (e.g. Python) collapse query + body parameters with the same name into a single kwarg.
Create Click-to-Call ad POST
Same shape and flow as POST /v1/ads/ctwa, but the CTA is CALL_NOW dialing `phoneNumber` via a tel: link. The ad set is destination_type PHONE_CALL optimizing QUALITY_CALL and the campaign objective defaults to OUTCOME_LEADS. Supports the same single-creative and multi-creative shapes as CTWA.