Event and conference campaign tracking
Conferences scatter your links across booth QR codes, talk slides, and printed handouts. Tagging each touchpoint distinctly turns an offline event into measurable traffic. This page shows a UTM structure that keeps booth, slide, and handout links separable under one event campaign.
Tag each touchpoint distinctly
Use one utm_campaign for the event and vary utm_content per physical touchpoint, so the event aggregates while each placement is measurable:
- utm_campaign=<one event name, e.g. devconf-2026>
- utm_source=event, utm_medium=offline (kept consistent)
- utm_content=booth-qr for the booth code
- utm_content=slides or handout for talk and print links
Why distinct touchpoints matter
Events are expensive, and a single 'event' number cannot tell you whether the booth, the speaking slot, or the printed handout justified the cost. Distinct utm_content per touchpoint lets you compare them on a like-for-like basis and decide where to invest next year.
Because many of these touchpoints are QR codes, the encoded URL is visible to any scanner — so keep every value generic and never encode an attendee badge ID or personal data. Each booth code, slide link, and handout should carry its own utm_content under the shared event campaign.
How it appears in analytics and logs
A visit with one event utm_campaign and a utm_content naming the touchpoint tells you whether the booth, a talk slide, or a handout drove it. Without the split, the whole event collapses into one undifferentiated number.
Diagnostic use case
Tag every on-site touchpoint — booth QR, slide link, handout URL — with a distinct label so you can tell which one drove visits at an event.
What WebmasterID can help detect
WebmasterID reads the shared event utm_campaign and per-touchpoint utm_content at ingest, so the event rolls up as one campaign while booth, slide, and handout traffic stay separable.
Common mistakes
- Using one identical QR code for the booth, slides, and handouts, so touchpoints cannot be compared.
- Encoding attendee badge IDs or contact data into a scanned URL.
- Splitting the event across several utm_campaign strings so it cannot roll up.
Privacy and accuracy notes
Keep event UTM values generic — touchpoint and placement labels only. Never encode an attendee's badge ID or contact details in a scanned URL. The encoded link is public to any scanner.
Related pages
- QR code campaign tracking with UTM
A QR code is just an encoded URL, so encoding a UTM-tagged link turns print, packaging, and signage into measurable offline-to-online traffic. This page shows the structure, a worked example, and the rule that no personal data goes in the encoded URL.
- Webinar campaign tracking with UTM
A webinar has several link touchpoints — the registration page, reminder emails, and the join link — and tagging them separately reveals which one drives results. This page shows a UTM structure that keeps registration distinct from reminders so attendance attribution is honest.
- Campaign links (docs)
Tag booth, slide, and handout links under one event campaign.
Sources and verification notes
- MDN — URL search paramsEach touchpoint encodes a tagged URL sharing one utm_campaign.
Last reviewed 2026-06-24. Facts are checked against primary/official sources where available; uncertain specifics are marked “Data not yet verified” rather than guessed.