Query parameters in the attendee profile
Who can use this
ContentHub
Free
Managed Service
Included
You can pass extra data on the event URL and store it on the attendee profile without showing a field on the form. Typical values are campaign parameters such as utm_source, utm_medium, utm_campaign, and utm_content, or a partner ID.
Attendees never see these fields. When they open the registration page or the login form with a matching query string, MEETYOO copies each matching value onto that person as a custom property.
Example:
https://www.example.com/event/...?utm_source=linkedin&utm_medium=paid&utm_campaign=q3-webinar
If a configured parameter is missing from the URL, that profile value stays empty. Extra query parameters that you did not configure are ignored.
Registration vs login
The same idea applies on two attendee paths. You configure a hidden custom field for the path you actually use.
Registration page
The hidden field's name is the query parameter. A field named utm_campaign reads utm_campaign from the registration URL and writes that value to the new user's profile when they submit.
Parameter names may use letters, numbers, _, -, and .. They cannot contain spaces.
Login with name and custom fields
When access is Login with Name and Custom Fields, hidden custom login fields do the same on the event login form. The value is stored when the attendee submits login, not when they only open the page.
The URL parameter is the field name without the custom:: prefix. In ContentHub Admin, that parameter is generated from the field Label (spaces become underscores). After you save, changing the label does not change the parameter.
What attendees and operators see
On the registration page and on login, hidden fields are not rendered. Visible custom fields (text, email, select, checkbox) are unchanged.
After registration or login, the values are custom properties on that attendee. In Analytics, they appear under Custom Properties (for example Registrations by utm_campaign) and as extra columns on the user list.
Campaign links and a post-session destination are separate settings. To send attendees somewhere after the livestream, see Post-session redirect.
Configure in ContentHub Admin
Hidden query-parameter fields are configured in two places: the registration form, and login when access is Login with Name and Custom Fields. Use the path that matches how attendees enter the event.
Registration page
- Open the event.
- Under Event Configuration, open Registration.
- Open the Custom Fields tab.
- Choose Add Field.
- Set Field Type to Query Parameter Field.
- In Query Parameter, enter the exact URL parameter, for example
utm_campaign. Letters, numbers,_,-, and.are allowed. No spaces. - Choose Save.
The field is listed under Selected Registration Fields with the parameter name as its label. Attendees never see it on the form.
The hint This field will be automatically filled with values from the URL parameters is shown while you add the field.
Login with name and custom fields
- Open the event.
- Under Event Configuration, open General.
- Open the Access tab.
- Set access to Login with Name and Custom Fields. Custom Login Fields appears.
- Choose Add Field.
- Enter a Label. The URL parameter is generated from this label (spaces become underscores). Example: label
utm_campaign→?utm_campaign=value. - Set Field Type to Query Parameter (Hidden).
- Choose Save on the field dialog, then Save on Access.
You can have at most four custom login fields, including the required user field. You cannot remove user.
After the field exists, the URL parameter is locked. Changing the label later does not change the parameter.
The dialog explains: This field is not shown to attendees. Use it to pass extra data through the event URL, for example a campaign or partner ID. Append the parameter like ?utm_campaign=value.
Check the result
Open the registration or event URL with the query string, complete registration or login as a test attendee, then open Analytics. Values show under Custom Properties and as extra columns on the user list.