# Submission metadata

Form Plume captures submission metadata like UTM campaign values, referrer, country, and request context so you can see where each form entry came from.

[Submitted fields](/docs/forms/fields) tell you what someone wrote. Metadata helps explain where the submission came from.

## UTM attribution

Form Plume stores UTM values when your form includes them in the submission. A plain HTML form does not send campaign parameters from the page URL automatically.

Add hidden fields for the values you want to keep:

```html
<input type="hidden" name="utm_source">
<input type="hidden" name="utm_medium">
<input type="hidden" name="utm_campaign">
<input type="hidden" name="utm_term">
<input type="hidden" name="utm_content">
```

Then copy the values from the page URL before the form is submitted:

```html
<script>
  const params = new URLSearchParams(window.location.search);
  const names = [
    "utm_source",
    "utm_medium",
    "utm_campaign",
    "utm_term",
    "utm_content",
  ];

  for (const name of names) {
    const value = params.get(name);
    const input = document.querySelector(`[name="${name}"]`);
    if (value && input) input.value = value;
  }
</script>
```

Keep your campaign names consistent across links so the submitted values are easy to compare.

## Referrer and page

The referrer can provide a fallback source when no UTM values exist. Browsers and privacy tools may shorten or remove it, so treat it as useful context rather than guaranteed truth.

## Country and request context

Country comes from trusted edge or proxy data. Form Plume does not ask the browser for precise location.

Metadata may also include the page, received time, request identifier, and safe technical context used for troubleshooting and [spam protection](/docs/spam-protection).