Integrations
DataProductionData import

Conversions API

Any system that knows the outcome can now tell Apointoo.

Native adapters cover the big booking platforms. The Conversions API covers everything else: your custom CRM, your internal sheet workflow, your client's homegrown system. One authenticated endpoint receives identity, attribution ids, and value. What comes back to your ad accounts is the same verified outcome every Apointoo adapter produces.

If the outcome lives outside an adapter, it never reaches the ad

Clinics run bookings in systems no connector covers. The appointment happens, the ad platform never hears about it, and the campaign keeps optimizing on clicks.

One POST per outcome, one ledger for all of them

Send the outcome when it happens, with your own idempotency key. Apointoo matches it to the original visit, applies consent rules, and delivers it to Google Ads exactly like a native integration would. Retractions work the same way in reverse.

What any system can send

lead_capturedappointment_bookedappointment_attendedsale_paidrefund_retraction

How the data flows

  1. Your system confirms the outcome (booking, sale, stage change)
  2. One authenticated POST carries identity + attribution ids + value
  3. Apointoo matches the visit, dedupes on your idempotency key
  4. The outcome enters the same ledger as native adapters
  5. Ad platforms receive it under the same consent rules

How the connection works

  1. Request a scoped ingest token for your workspace.

  2. POST each outcome with identity, attribution ids, value, and your idempotency key.

  3. Re-sending the same key returns the same result; nothing duplicates.

  4. Refunds and cancellations post as retraction events on the same record.

Attribution identifiers

gclidgbraidwbraidfbclidutm_sourceutm_campaign

Event mapping

FromApointoo
POST /v1/conversions { type: lead }lead_captured
POST /v1/conversions { type: appointment_booked }appointment_booked
POST /v1/conversions { type: appointment_attended }appointment_attended
POST /v1/conversions { type: sale, value, currency }sale_paid
POST /v1/conversions { type: refund }refund_retraction

Frequently asked questions

Any system that knows the outcome can now tell Apointoo.

No. Adapters stay the zero-code path for covered platforms. The API is for systems that will never get an adapter.