Integrations
FormsPlannedSource

Jotform

Every submission shows up with its source attached.

Jotform posts each submission to your webhook endpoint. Apointoo receives it, attaches the captured click context, and turns it into the same canonical lead event every other source produces.

Pages marked Planned are complete specifications written before the connector ships. They validate demand. Connectors with real delivery logs are marked Production or Beta.

Submissions arrive anonymous to your ads

The form knows the answers. The ad account knows the clicks. Nothing joins them, so optimization runs on incomplete data.

One webhook, attributed from the start

Capture records the click context when the visitor opens the form page. When Jotform posts the submission, Apointoo joins the two and delivers the outcome wherever it counts.

What it sends to Google Ads

lead_capturedquote_requested

How the data flows

  1. Ad click lands on the Jotform page
  2. URL parameters captured alongside the submission
  3. Submission webhook reaches Apointoo
  4. Answers normalized into a lead event
  5. Event matched and forwarded to destinations

How the connection works

  1. Point the Jotform submission webhook at your Apointoo endpoint.

  2. Keep capture running on the pages that host your forms.

  3. Map form fields to identity fields once.

  4. Deliveries show up in the same logs as every other source.

What it reads

submission webhook (POST to your endpoint)

Event mapping

FromApointoo
New submissionlead_captured / quote_requested

Frequently asked questions

Every submission shows up with its source attached.

Webhook availability depends on your Jotform plan tier. The connection states its requirement during setup.