Skip to main content

Use UTM parameters with your HeySummit event

Track which campaigns and links bring attendees to your event registration.

Written by Benjamin Dell

UTM parameters are labels added to a link so you can identify which campaign, channel, or source brought someone to your event.


​

Add UTM parameters to an event link

Attendee attribution records utm_source, utm_medium, and utm_campaign. Add the first parameter after a ?, then join additional parameters with &.


​

Example: https://your-event-domain.com/?utm_source=linkedin&utm_medium=social&utm_campaign=launch


​

Use those exact parameter names. Replace the example values with short labels that make sense in your reporting.


​

When attribution is saved

HeySummit carries the UTM values into registration and saves them against the attendee when attribution is first recorded. Each field keeps its first saved non-blank value for that attendee in the event. A later registration step can fill a field that was previously blank, but it does not replace an already recorded value.


​

View or export UTM data

  • Go to Registration & Attendees > Attendees and export the attendee list to see utm_source, utm_medium, and utm_campaign for individual attendees.

  • Select Full breakdown on the attendee report's Top Traffic Source card to open Referral Sources. Use its source selector to compare saved UTM sources, media and campaigns with other attendee attribution sources.


​

ref is also supported for custom referral labels, but it is separate from the three UTM parameters.


​

Compare campaign traffic

Go to Registration & Attendees > Attendee Insights to compare visits by UTM source, medium, campaign, term or content. Switch between Visitors and Page views. These traffic reports start from when tracking became available and do not change an attendee's saved attribution. The attendee export still contains the three fields described above. See Understand referral and campaign traffic in Attendee Insights for setup, count definitions and limits.

Did this answer your question?