apointoo.
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 Apointo 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 Apointo 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. 01Ad click lands on the Typeform
  2. 02Hidden fields carry utm / gclid / fbclid
  3. 03form_response webhook reaches Apointo
  4. 04Answers normalized into a lead event
  5. 05Event matched and forwarded to destinations
How the connection works
01

Add hidden fields for utm parameters and click identifiers.

02

Point the Typeform webhook at your Apointo endpoint.

03

Map answers to identity fields once.

04

Every submission lands normalized and matched.

What it reads
form_response webhook
Event mapping
FromApointo
form_response submittedlead_captured / quote_requested
Frequently asked questions
What if a visitor blocks cookies?

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

Do partial responses count?

No. Only completed form_response webhooks create events.

When does this connector ship?

This page is the working specification. Join the early-access list and build order follows demand.