Skip to main content

View context in a form response

Log in to add to favourites

Page last updated 17 August 2026

When a form has context capture switched on, each response carries a record of how the person arrived. You read it on the response itself.

Open the context for a response

  1. Open the form response.
  2. Select the Context tab, next to Response.

Response holds what the person filled in. Context holds everything about how they got there.

Any value can be copied with the copy control beside it, which confirms with Copied.

What the tab shows

UTM parameters

Where the visit was tagged as coming from. These are the values a campaign matches on.

FieldWhat it tells you
UTM sourceThe platform or place the visit came from
UTM mediumThe kind of channel it arrived through
UTM campaignWhich campaign brought them, matched on the campaign's UTM Campaign ID
UTM contentWhich specific link or creative, where your links distinguish them
UTM termThe search term, where one was passed

Click and ad tracking IDs

Identifiers added by advertising platforms when someone arrives from a paid placement. Contensis records whichever is present:

  • Google click ID (gclid)
  • Microsoft click ID (msclkid)
  • Facebook click ID (fbclid)
  • X click ID (twclid)
  • TikTok click ID (ttclid)
  • LinkedIn ad tracking ID (li_fat_id)
  • Campaign Manager 360 click ID (dclid)

These are useful when reconciling responses against the reporting in the ad platform itself.

Visit

FieldWhat it tells you
Submitted fromThe page the form was submitted from
ReferrerThe page they were on immediately before
Form startedWhen they began filling the form in, which read against the submission time tells you how long it took

Visitor

FieldWhat it tells you
CountryThe country the visit came from
AudiencesWhich personalisation audiences they matched

Empty fields are normal

The tab shows what was available when the form was submitted, and most responses will not have all of it.

Somebody who typed your address straight into their browser arrives with no UTM parameters, no referrer, and no click IDs, so those fields are empty. That is a complete and correct record of an untagged visit, not a fault.

Responses submitted before context capture was switched on for the form have no context at all.

Getting context out of Contensis

Context is not only readable one response at a time. It can be added to the responses listing as columns, through the manage columns control, which means you can see attribution across every response at once rather than opening them individually.

That also determines what reaches an export. The CSV export includes only the columns shown in the listing, so context appears in an export if, and only if, you have added those columns first.

Worth doing before you export rather than after. Filtering a listing to one campaign, exporting it, and then finding the file has no campaign column in it is an easy mistake to make, and the export gives no hint that anything is missing.

Still need help?

If you still need help after reading this article, don't hesitate to reach out to the Contensis community on Slack or raise a support ticket to get help from our team.
New support request