📈Tracking & pixels
Add Google Tag Manager, Meta Pixel, PostHog or the HubSpot tracking code to a form's public page, understand when each tag fires, and see how UTM parameters are captured with every submission.
Tracking & pixels lets you measure the traffic that reaches a form with the tools you already use. You paste an ID, publish, and the matching tag loads on the form's public page. Nothing loads in the editor, and nothing loads for a tool whose ID you left empty.
This is optional. Dapta Forms already counts views, starts, submissions and drop-off on its own under Analytics; tracking IDs are for stitching form traffic into your own campaign reporting.
Step 1: Open the form in the editor and click the Connect tab. Scroll past Integrations to the Tracking & pixels section.
Step 2: Fill in only the fields for the tools you use. Every field is optional and independent.
Google Tag Manager ID
GTM-XXXXXXX
Loads your GTM container on the form page so your tags fire.
Meta Pixel ID
123456789012345
Fires a PageView on your Meta pixel to measure campaigns.
PostHog project key
phc_...
Captures a pageview in PostHog for product analytics.
PostHog host (optional)
https://us.i.posthog.com
Defaults to PostHog US cloud; set your EU or self-hosted ingestion URL.
HubSpot tracking ID
12345678
Loads the HubSpot tracking code for your portal on the form page.
💡 Tip: The PostHog host field only matters if your project is not on PostHog US cloud. It must be a full address, for example
https://eu.i.posthog.com. Anything else is refused with Enter a full http(s) URL, e.g. https://eu.i.posthog.com.
Step 3: Click Publish. Tracking IDs are part of your draft, so they only reach visitors once the form is published.
The banner above the fields reads: "These IDs are staged with the rest of your draft: click Publish to put them on the live form. Integrations above save to the live form immediately."
That difference is worth remembering:
Tracking & pixels: saved into the draft, live after Publish.
Integrations (webhook, HubSpot): saved to the live form the moment you change them, no publish needed.
See Autosave, drafts & publishing for the rest of the draft lifecycle.
When each tag fires
The rules are the same for every tool, so what you measure stays predictable:
Tags load only on the public form page. The editor, the preview and the admin never load them.
Each visit produces exactly one pageview: one GTM container load, one Meta
PageView, one PostHog$pageview, one HubSpot tracking script.Moving from one question to the next fires nothing. A slides form is a single page for your analytics, however many steps it has.
Submitting fires no conversion event. If you need one, build the trigger yourself in GTM (for example on a URL or an element on your thank-you page, or on the redirect destination you set in the ending screen).
⚠️ Note: Dapta Forms does not show a cookie or consent banner on the public form. If your visitors need one, handle consent in your own GTM container and gate your tags there.
LinkedIn, TikTok, Google Ads and everything else
There are only five fields, and there is no separate field for LinkedIn Insight, TikTok Pixel, Google Ads or any other tool. Load those through Google Tag Manager: set the Google Tag Manager ID here, then add each tag inside your container. One ID on the form, as many tags as you like in GTM.
UTM parameters are captured for you
You do not need a pixel to know where a lead came from. When someone opens a form with campaign parameters on the link, for example:
utm_source, utm_medium, utm_campaign, utm_term and utm_content are stored with the submission. From there they travel with the answer:
to HubSpot, through the five UTM mappings in Form elements;
to your endpoint, in the
utmobject of the webhook payload.
The footnote under the fields says the same: "UTM parameters are captured automatically and can be mapped to HubSpot properties in Integrations."
⚠️ Note:
utm_keys are reserved for campaign capture. A question whose field key starts withutm_is never prefilled from the URL. See Hidden fields & URL prefill.
What is not collected
A form with no tracking IDs makes zero third-party requests. Dapta Forms itself stores the answers, the score, the timestamps and the UTMs of a submission, and does not store IP addresses, user agents, devices, countries or referrers. Read Security & Privacy for the full picture.
What's next
Analytics: views, starts, completion rate and drop-off, measured by Dapta Forms.
Form elements: UTMs, score, outcome, submitted date: send the captured UTMs to HubSpot properties.
Payload & headers reference: where the UTMs sit in the webhook body.
Autosave, drafts & publishing: why the IDs wait for Publish.
Last updated