
Registration Pages
Part of Event partner promotion
Tracking partner registrations without inflating totals
Give each event partner a distinct registration link or code before promotion starts. Name it consistently, record who received it and test it through to the …
Give each event partner a distinct registration link or code. Record who received it and use a consistent label. In the link, use utm_source for the partner, utm_campaign for the event promotion and one consistent utm_medium value for the channel. A partner name in lowercase is a common choice for utm_source.
Include utm_source, utm_medium and utm_campaign: some systems, including Google Analytics, require all three. Google Analytics’ URL builder can add campaign data to custom URLs. Test each tagged link through to the registration page before promotion starts.
Use analytics to identify visits from each tagged link, not to count registrations. Retain the partner label or code with a registration record if you want to attribute that registration; a visit alone does not show that someone registered. If a record cannot be linked to a partner label, do not assign it to that partner.
Use the registration export as the event’s headcount base and apply one event-wide rule to count valid registration records once. Do not add partner report totals to the export. A ticket order may cover more than one attendee, so decide whether your figure counts registration records or attendees rather than treating orders as registrations.
Keep partner attribution separate from headcount: it shows the tracked route, not which invitation persuaded someone to register. If the same person sees two partner invitations, the tracked route cannot establish which one persuaded them. A registration can also be cancelled or transferred, so apply the same rule to those records before reporting valid registrations.
When useful, report three figures separately: attributed registrations are records linked to a partner label; valid registrations are the records counted under your event-wide rule after cancellations; actual attendees come from later attendance records. Date each extract and note untracked channels. Restrict access to personal information to people who need it for the event.
How to Track Partner Registrations Without Inflating Totals
- Assign a unique registration link or code to each partnerUse a distinct utm_source for each partner (e.g., utm_source=partnername)
- Use consistent campaign parametersSet utm_campaign to the event name and utm_medium to one consistent value (e.g., email, social)
- Test each tagged link before promotionVerify the link redirects correctly to the registration page with tracking data intact
- Track visits, not registrations, via analyticsAnalytics shows traffic sources but does not confirm registration; use only for route attribution
- Attribute registrations using the partner labelOnly count a registration as attributed if it is linked to a valid partner code in the record
- Use registration export as headcount baseApply one event-wide rule to count valid records once—do not sum partner reports
- Separate partner attribution from final headcountAttribution shows the referral path; headcount reflects actual valid registrations after cancellations
- Report three key figures separatelyAttributed registrations, valid registrations (post-cancellation), and actual attendees (from attendance records)
- Restrict access to personal dataOnly allow staff who need it for event operations to view or handle personal information
Key Metrics to Report Separately
- Attributed Registrations
- Registration records linked to a partner's unique tag
- Valid Registrations
- Records counted under event-wide rule after cancellations and transfers
- Actual Attendees
- Confirmed presence at the event based on check-in or attendance records



