Build against explicit beta contracts.

Send outcomes from a trusted server. Use a workspace-scoped token with events:write and a stable deduplication key. Outcome means an event received from CRM, API, or Zapier; attribution happens separately.

POST /api/v1/events
Authorization: Bearer <workspace token>
Idempotency-Key: <stable source key>

Use the Sissel Zapier integration with a workspace token. Trigger and action payloads preserve the source and deduplication identity; reconnect the account if its token is revoked.

SISSEL_API_BASE_URL=https://app.sissel.app
Authentication: workspace token

Sissel verifies a read-only API key, reads entity types, fields and stages, then asks you to map identity fields and outcome meanings. Sync is cursor-based and starts with new changes.

Required: base URL + read-only API key
Then: verify → map fields/stages → receive a test outcome

OAuth reads account hierarchy and spend. Conversion delivery is configured per outcome as Not sent, Test, or Live. Live requires a fresh named reconciliation baseline, at least 98% parity, and no unexplained differences.

Required: owner/admin + ad account + dataset
Path: connect → map → test → reconcile → review → Live

OAuth reads accessible accounts, hierarchy and spend. Each active outcome requires its conversion action ID. Tests use validation before Live; the same reconciliation gate applies.

Required: owner/admin + operating account + conversion action IDs
Test: validateOnly before production delivery