Integrations
FormsPlannedSource

Typeform

The form answer arrives with the click that asked for it.

Typeform collects answers; hidden fields carry the context. With utm parameters and click identifiers mapped to hidden fields, every form_response lands in Apointoo already attributed.

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

Form tools deliver answers, not attribution

The submission arrives without its history. By the time the lead reaches your CRM or your ad platform, nobody can say which campaign produced it.

Hidden fields in, canonical lead events out

Each form_response becomes a typed Apointoo event with identity, answers, and the original click context. From there it matches, deduplicates, and delivers like any other source.

What it sends to Google Ads

lead_capturedquote_requested

How the data flows

  1. Ad click lands on the Typeform
  2. Hidden fields carry utm / gclid / fbclid
  3. form_response webhook reaches Apointoo
  4. Answers normalized into a lead event
  5. Event matched and forwarded to destinations

How the connection works

  1. Add hidden fields for utm parameters and click identifiers.

  2. Point the Typeform webhook at your Apointoo endpoint.

  3. Map answers to identity fields once.

  4. Every submission lands normalized and matched.

What it reads

form_response webhook

Event mapping

FromApointoo
form_response submittedlead_captured / quote_requested

Frequently asked questions

The form answer arrives with the click that asked for it.

Click identifiers travel in the URL and hidden fields, so attribution survives even without third-party cookies.