Getting started

Getting started

This page takes you from zero to your first offline conversion inside Google Ads. Nothing here is simulated: every step uses the published SDK and the direct-confirm path already running in production.

1. Install the SDK

npm install git+https://github.com/vizuh/apointoo-sdk.git hono zod

The package ships domain types, zod schemas, adapter contracts, and the server pipeline (queue, outbox, conversion upload).

2. Mount the handler

createBookingHandler returns a Hono app. Mount it on your Next.js route handler, Worker, or Node server:

import { createBookingHandler } from '@vizuh/apointoo-sdk/server'
import { directConfirmAdapter } from '@vizuh/apointoo-sdk/adapters/booking/direct-confirm'

export const app = createBookingHandler({
  config: { /* your tenant config */ },
  booking: directConfirmAdapter(),
  state: memoryStateStore(),
})

3. Capture the click

First-touch and last-touch attribution must exist at the moment of conversion. On WordPress, the Apointoo Capture plugin keeps gclid, fbclid, and UTMs attached to the forms you already run. On custom frontends, the SDK attribution helpers normalize the click context.

4. Confirm the outcome

When the sale, booking, or closed deal actually happens, confirm it with its matching attribution:

await apointoo.confirm({
  leadId: lead.id,
  outcome: 'sale_paid',
  value: 1840.00,
  currency: 'EUR',
})

5. Watch it land in Google Ads

Confirm flows through the queue and outbox; the conversion uploads with click id, value, and time. Failures retry. Logs keep every receipt.

Next steps

• Core concepts: session, identity, and canonical events.
• Adapters: swap direct-confirm for your system's adapter.
• Deployment: environment variables and the production checklist.