Conversions API

Conversions API (specification)

Status: planned. This page is the working specification. The product is built after click validation proves demand for the page. Join the early-access list on the product page.

What it solves

Booking systems without a native adapter never deliver the outcome to Google Ads. The Conversions API receives that outcome from any system that knows when the sale or appointment happened.

Contract (v0, simulated)

POST /v1/conversions
Authorization: Bearer <ingest-token>
Content-Type: application/json

{
  "type": "appointment_booked",        // lead | appointment_booked | appointment_attended | sale | refund
  "idempotency_key": "system-x-12345",
  "contact": { "phone": "+15551230000", "email": "maria@example.com" },
  "attribution": { "gclid": "...", "utm_source": "google", "utm_campaign": "summer" },
  "value": 180.00,
  "currency": "EUR",
  "occurred_at": "2026-08-24T14:30:00Z"
}

• Re-sending the same idempotency_key returns the same result; nothing duplicates.
• Without consent, click identifiers are stripped before ad delivery.
• refund becomes a retraction on the same record.

Privacy rules

Identity is limited to matching fields (phone, email). Clinical detail does not belong in the payload.