Conversions
Send events to every destination
Changed onSends conversion events once and forwards them to every ad platform destination saved for the profile (see POST /v1/events/destinations), or to the destinations given in the request. Requires the Ads add-on.
Forwarding
- Each destination receives the events exactly as POST /v1/ads/conversions would send them, so the per-platform notes there (hashing, batching, eventName semantics, dedup on eventId) apply here too.
- A destination saved with eventNames only receives events with those names.
- One destination failing never blocks the others: each one reports its own result.
Storage
Zernio also stores each event for the profile's reporting.
- Email, phone and externalId are stored only as SHA-256 hashes.
- sourceUrl keeps only its origin, path and attribution parameters (utm_*, gclid, fbclid, ttclid, li_fat_id, epik, rdt_cid, gbraid, wbraid).
- Events sent with testCode are forwarded but not stored.
post/v1/events
Request
- Base URLhttps://zernio.com/api
- URLhttps://zernio.com/api/v1/events
- AuthHTTP bearer
Request body
Example request
{
"events": [
{
"eventName": "Purchase",
"eventTime": 1744732800,
"eventId": "order_abc_123",
"value": 99.5,
"currency": "USD"
}
]
}Response
Events processed. Check each destination for partial failure.
Changes
- info
added the optional property
to the response with the status
- info
- info
endpoint added
- info