📊 Tracking

propform can integrate directly with three analytics tools. All three can be enabled independently in the form settings.


Contents

---

Google Tag Manager (GTM)

Enable GTM in the form settings and enter your GTM container ID (format GTM-XXXXXXX). propform will then send the following events to dataLayer:

Event When triggered?
form_onload Form is loaded
form_onpageshow Form is displayed (including when returning from the browser cache)
form_start_input Visitor starts their first input
form_abort Visitor leaves the form after starting input, without submitting
form_submit Submit button is clicked (before server-side validation)
form_next_step / form_previous_step For multi-step forms: step forward or back (with step numbers and names)
onload_thank_you_page Thank-you page is loaded after a successful submission
onpageshow_thank_you_page Thank-you page is displayed (including from the browser cache)

Every event also contains formSlug and formCustomSlug; the step events additionally include departureStep/arrivalStep along with the step names.

Example triggers in GTM

In GTM, you can create triggers based on events — e.g. send a conversion to Google Ads or a Meta Lead event on onload_thank_you_page, or a re-engagement pixel on form_abort.

⚠️ Use onload_thank_you_page for conversions: form_submit already fires when the submit button is clicked — including when the submission fails, e.g. due to a required field. A visitor only reaches the thank-you page after a successfully saved submission.

Passing field values with the submit event

Enable the option “Pass value to tracking events” in a field's field settings — the field's current value is then attached to the form_submit event on submission (in the dataLayer and in the postMessage to the parent page), under the key trackingFields.<fieldname>:

  • Choice fields (single/multi select, radio, checkboxes) provide the option key and the visible label, e.g. trackingFields.ind_Stelle_123.value = ind_Schl_5905 and trackingFields.ind_Stelle_123.label = Sales Manager (m/f/d)
  • Text and number fields provide only value
  • Empty fields are omitted

In GTM, access them via data layer variables (e.g. trackingFields.ind_Stelle_123.value) and attach them to your tags as event parameters. Typical use case: an application form with a job selection — your tracking sees which position was applied for.

⚠️ Privacy: Do not flag fields containing personal data (name, email, phone …) unless visitor consent is in place — the values flow into your tag management and potentially to its recipients.

> 💡 Multi-step tracking: For each break field, you can assign a step name in the field editor (e.g. “Step 2: Contact details”). This is included in the form_next_step/form_previous_step events and enables detailed funnel tracking.


## Facebook Pixel

Enable Facebook Pixel in the form settings and enter your Pixel ID (the 15–16-digit number from Meta Events Manager). propform then loads the Meta base code directly within the form and fires a PageView event on every page view — both on the form itself and on the thank-you page after a successful submission.

Measuring conversions: custom conversion on the thank-you page

The thank-you page has its own URL ending in /thankyou. In Meta Events Manager, create a custom conversion:

  • Event: PageView
  • Rule: URL contains thankyou

This conversion counts exactly the successful submissions and can be selected as a conversion goal in your ad sets.

💡 Want the standard Lead event? (e.g. for lookalike audiences or campaign optimisation on “Lead”): Use Google Tag Manager for this — the Meta base code as a custom HTML tag on all pages, plus a tag with fbq('track', 'Lead'); triggered by the custom event onload_thank_you_page. In that case, do not additionally enable propform's own pixel toggle, otherwise PageView fires twice.

---

Etracker

Enable Etracker and enter your Etracker account code. This is useful if you already use Etracker for your main website and want form events to be included in the same reporting.

CSS class track-submit for multi-step conversion tracking

For multi-step forms, the final submit button also carries the CSS class track-submit — the forward/back buttons between steps do not have this.

This allows you to specifically count only the actual conversion click in your Etracker configuration (or other tracking tools), without misinterpreting the navigation clicks:

// Beispiel: Etracker-Event nur am finalen Submit
document.querySelector('.track-submit')?.addEventListener('click', function() {
  _etracker.sendEvent(new et_UserDefinedEvent('FormConversion', 'Anfrage', 'Submit', null));
});

> 💡 For single-page forms, track-submit is also present — the selector works universally.

---

⚠️ Cookie consent is your responsibility

propform forms deliberately do not include a cookie consent banner. If you enable tracking (whether via GTM, Pixel or Etracker), you, as the form operator, are responsible for ensuring that visitors have given their consent.

Practical solution:

  • If the form is embedded as an iFrame on your main page, the cookie banner on your main page typically handles consent.
  • If the form runs as a standalone URL, you must ensure this yourself — e.g. via your privacy policy, which you link to in the form settings under “Legal Notice”.

Continue to Webhooks 👉