Do you need InGo to pass on additional data from users of your event and therefore utilize in a fashion you desire? If so, a good example of this use would be if a registration company (or anybody who actually collects the registration data) wishes to somehow know the source of where people are coming from, or if they wish to parse the information and dump certain people in buckets, say for example, anybody with the TITLE=DIRECTOR, then this is the exact purpose of the query string.
Insert these directly into the event's URL Parameter Mask (Conference -> Edit). The following parameters are supported:
| Parameter | Description |
|---|---|
%first_name% |
First Name |
%last_name% |
Last Name |
%email% |
Email Address |
%company% |
Company Name |
%company_position% |
Title / Position |
%social_channel% |
What Social Network the User Utilized |
%is_social_user% |
If they are a Social Network User |
%external_registration_id% |
If you provided an external_registration_id for the Authorizer widget, this will contain that ID on any subsequent visit your registrant makes to the page with the Activator Widget installed. |
Individual key=value pairs are joined with an ampersand (&).
Examples
All using John Smith (jsmith@smiths.com) Blacksmith for Smiths Metalworks who logged in using Facebook:
| Description | URL Parameter Mask | Query String |
|---|---|---|
| Forward first and last name | fn=%first_name%&ln=%last_name% | ?fn=John&ln=Smith |
| Forward last name and email | lastName=%last_name%&e=%email% |
?lastName=Smith&e=jsmith@smiths.com |
| Signal social channel | channel=%social_channel% |
?channel=facebook |
Example template (forwards all the values)
firstName=%first_name%&lastName=%last_name%&emailAddress=%email%&companyName=%company%&position=%company_position%&channel=%social_channel%&isSocial=%is_social_user%