Skip to main content

Umbraco Forms submissions aren't tracked in Engage when forms are custom-rendered or submitted headless

Why Forms submissions can be missing from Umbraco Engage for custom-rendered, JSON or custom-endpoint forms, what Engage needs from a submission, and a checklist of silent failures.

Written by Joana Knobbe

Type: Troubleshooting ​Category: Umbraco Engage > Analytics ​Tags: Umbraco Engage, Umbraco Forms, Umbraco.Engage.Forms, form tracking, form submissions not tracked, goals not triggering, visitor profile, headless forms, custom form rendering, custom endpoint, JSON

Product: Umbraco Engage with Umbraco Forms ​Version: Umbraco Engage 17


If your Umbraco Forms entries are saved in Forms but don't show up in Umbraco Engage, this article explains what Engage needs from a submission and what to check. It mostly applies to forms that are rendered with your own JavaScript or markup, posted as JSON, or saved through a custom endpoint.

Symptoms

  • Entries appear in Umbraco Forms, but the submission is not linked to a visitor in Engage.

  • The Umbraco Forms submission goal does not trigger.

  • The submission appears on the visitor profile, but without its field values.

  • No errors appear in the logs.

Cause

Tracking Forms submissions requires the Umbraco.Engage.Forms add-on. Core Engage doesn't listen for Forms submissions on its own. With the add-on installed, Engage links a submission to a visitor when Umbraco Forms creates a record. At that moment, Engage reads the incoming request. It only processes the submission when all of these are true:

  • The record is created during the visitor's own HTTP request.

  • The request body is form data. JSON posts are skipped.

  • The request carries the Engage visitor cookie.

The Forms record is always saved. Engage never blocks it. What changes is what Engage can do with it:

  • No visitor cookie: Engage skips the submission completely. It is not linked to a visitor, no goals trigger, and nothing appears on a profile. This is also what happens, by design, for visitors who haven't consented to analytics cookies.

  • Visitor cookie, but no pageview ID: the submission is linked to the visitor and they're marked as identified, but Forms goals don't trigger and the profile shows the submission without its field values.

The visitor cookie is required. The pageview ID is what makes goals and profile details work.

Standard Umbraco Forms rendering meets all of these requirements automatically. Custom-rendered forms and custom endpoints have to meet them on their own.

Solution: check your form against these requirements

None of the problems below raises an error. The data is simply missing, so go through the list one by one.

What goes wrong

What is lost

The data is saved some other way than as an Umbraco Forms record

All server-side tracking

The submission is posted as a JSON body, including through the Umbraco Forms headless API

All server-side tracking

No visitor cookie is sent, for example a cross-origin request without credentials: "include"

All server-side tracking

The record is created in a later request or a background job

All server-side tracking

The form markup has no hidden FormId and FormName inputs. The Engage script looks for these in the page to recognize the form as an Umbraco Form.

All browser tracking, and the pageview ID field

The form is inserted inside a wrapper after the page has loaded

All browser tracking, and the pageview ID field

The __umbracoEngageAnalyticsPageviewId field, which the Engage script adds to the form, is not posted with the submission

Goals, and field values on the profile

No submit event fires, for example when calling form.submit() or posting from a click handler

The submission is not listed on the profile

The visitor has not consented to analytics cookies

The link and goals go to the shared anonymous visitor (by design)

Fields are added to the form after it was tracked

Focus and error reports for those fields

If you use a custom endpoint, the simplest way to keep tracking working is to:

  1. Render a real <form> element in the page, with the hidden FormId and FormName inputs, so the Engage script can add the __umbracoEngageAnalyticsPageviewId field.

  2. Submit it with a real submit event, not form.submit() or a click handler.

  3. Post it as form data, for example new FormData(form), not JSON. Send it from the visitor's browser so the Engage visitor cookie goes with it. For cross-origin requests, use credentials: "include".

  4. In your endpoint, create the entry through Umbraco Forms, as a real Forms record, within that same request.

Prevention

Before replacing standard Umbraco Forms rendering or the Forms submission endpoint, compare your custom version against the table above. Then submit a test entry and confirm it appears on your own visitor profile in Engage, with its field values, before going live.

Still having issues?

Contact Umbraco Support with your Umbraco, Umbraco Forms and Umbraco Engage versions, a description of how the form is rendered and submitted, and an example of a request your form sends.

Recommended documentation

Related articles


AI + human generated. Last updated on November 13, 2026

Did this answer your question?