📊Form elements: UTMs, score, outcome, submitted date
Send the metadata Dapta Forms captures on its own to HubSpot: the five UTM parameters, the lead score, the outcome heading and the submitted date. Plus the switches for inferring the company from the
Not everything worth sending to HubSpot is an answer. Dapta Forms also captures where the respondent came from, how they scored, which outcome they landed on and when they submitted. The Map form elements section is where you decide which contact property receives each of those.
Open your form, click Connect, and scroll inside the HubSpot card to Map form elements. The section is described as Send captured metadata (UTMs, lead score, outcome, and submitted date) to HubSpot properties.
Step 1: Map the campaign parameters under UTM mappings.
The five rows are utm_source, utm_medium, utm_campaign, utm_term and utm_content. Whenever someone opens the public form with those parameters in the URL, Dapta Forms captures them automatically: you do not have to add hidden questions for them.
UTMs are sent on partial and complete submissions, so an abandoned lead still arrives with its campaign attached.
💡 Tip: The same values ride along in the webhook payload under
utm, and they are also visible on each submission. Tracking scripts are configured separately, in Tracking & pixels.
Step 2: Choose where the lead score and the submission date go.
Score property
The total score as a number. Receives the total score as a number, on completed submissions only. Pick a HubSpot number property.
Submitted-date property
The date of the submission. HubSpot date properties store midnight UTC, so the time of day is not kept. If you need the exact timestamp, take it from a webhook instead.
Scoring is set up on the Logic tab. If your form does not use points, leave Score property on (none). See Scoring.
Step 3: Send the outcome the respondent saw.
It receives the heading you wrote on the matching score range in Results: the same text the respondent reads on the ending screen, not a code. It is written on completed submissions only, and only when a score range actually matches. With scoring switched off, nothing is sent. See Outcomes.
Step 4: Decide what else the sync should do, with the three switches under the mapping sections.
Infer company from email
When the respondent uses a work email, fills the company and website properties from its domain. Free mail domains (gmail, outlook and the like) are skipped, and a value you mapped yourself is never overwritten.
Create a note on completed submissions
Attaches a note with the form name and the score to the contact. On by default.
Record a form submission in HubSpot
Creates a matching form in your portal, so each completed submission shows on the contact as a form submission activity listing the properties it set, not just a note. The form is named after yours, with (Dapta Forms) appended.
Record a form submission in HubSpot needs the forms and form-submissions-write scopes on the private app behind your connection. If your portal refuses, the card shows HubSpot could not set this up: {reason} and the rest of your settings still save.
⚠️ Note: All three only act on completed submissions. A partial submission carries the contact upsert, the mapped answers and the UTMs, and nothing else.
Reference
UTM mappings
Yes
Yes
Score property
No
Yes
Outcome property
No
Yes, when a score range matches
Submitted-date property
No
Yes, date only
Infer company from email
No
Yes
Create a note on completed submissions
No
Yes
Record a form submission in HubSpot
No
Yes
What's next
Value maps & static properties: translate answers and stamp fixed values.
Booking sync: the properties written when someone books a meeting.
How the sync works & troubleshooting: read the delivery log and fix a sync that is not running.
Last updated