Who can use this?
- Event Organisers that use the Grip Default Login structure
- Event Organisers with a custom SSO Protocol (scroll down to the dedicated section)
What is a Deeplink?
A deeplink is purely a link to a specific place within a Grip event. This could be any kind of Profile, Session or Navigation Item list. Following a deeplink means that after you've logged into Grip, you're taken straight to that specific page instead of just going to the normal Homefeed.
Example: Organisers will sometimes want to use this link in their own systems, in order to direct participants straight from their website to a specific Company Profile within the Grip event.
Deeplinks all contain the event url, along with the specific ID of the Profile/Session/Navigation Item that they're pointing to.
Profile: To link to a specific profile of an Event Participant or Company, add app/home/profile/<thing_id> to the end of the URL. The Thing_ID can be retrieved from the Grip Organiser dashboard and from the API.
Sessions: Add app/session/<session_id> to the URL. The Session_ID can be retrieved from the Grip Organiser dashboard and from the API.
Navigation Items: To link to, for example, the 'Exhibitor List' or 'Speaker list' in an event, add /home/network/list/<List_id> to the base URL. The List_id can be retrieved from the Grip Organiser dashboard and from signing into the Grip web platform. It can not be retrieved from the API at this moment in time.
You can view and copy a profile's deeplink in the dashboard by clicking on the 'Web Networking Deep Link' button (shown below) - or right-clicking and selecting 'Copy Link Address'. You can also simply copy the URL shown in your browser while you're viewing the Profile, Session or Navigation Item itself.
You can also see deeplinks detailed in the csv file downloads that are generated from the Dashboard - use this when you want to send a list of deeplinks to your client for all the profiles in their event.
What is Link Pre-population?
Link Pre-population is where we add user information to the url link that they follow when navigating to a Grip event.
Doing this means that we can 'pre-populate' (autofill) login details for this user, making it a lot easier for them to log in.
Example: We use link pre-population in our Welcome emails, which means that when the user follows the "Open Platform" link, it will automatically pre-populate the user's email in the email field, and Registration ID in the Reg ID field. This basically means the user doesn't have to copy and paste their details in order to sign up/login to the event.
Grip Login Experience
The login experience with email and badge ID pre-population will depend on whether it's a first-time login or a subsequent login.
1st Login: Badge / Registration ID Confirmation Page
If an Event Participant is signing in to Grip for the first time, the user will land on the Email Input page, then the Badge / Registration ID confirmation page. On these pages, the Email and Badge / Registration ID are both pre-populated:
1st Login: Create a Password
Once the Event Participant has pressed "Claim Account" they will be asked to create a password.
Subsequent Login: Enter password
On any subsequent login (if the user is not still signed in due to cookies) the Event Participant will be asked to only enter the password they create the first time they logged in.
How do we create these pre-populated URLs?
We use a specific format to add these details to the end of a URL, as follows:
For each user, the url will be different, as of course they have a different email address and badge id (sections in bold above).
Let's take a standard networking link as an example. This might usually be:
With the additional section for pre-populated details, it would become:
(this would take you to the login page for Grip Virtual, and fill in your email with 'email@example.com' and your Badge ID with 'ABC123')
Note: If you were to only include one part of the pre-population, you could prefill only the email address for example:
Using deeplinks with pre-populated login details:
This is just a combination of using a deeplink to take the user to a specific place within an event, and also pre-population to autofill login details. Some examples:
Deep linking to Profiles with link population for Single Sign-On Clients:
Deeplinks for Single Sign-On providers are slightly custom. The part of the link specific in all examples as " ssopass?id=XXX" might be multiple values in reality, depending on the SSO system that Grip is integrated with.
- Home: The below link will direct the user to the home page, this will be the Home Feed if configured, or the Recommended for You if it's not configured.
- Thing Profile:The below structure can be used for deep linking to a specific Thing Profile such as an Exhibitor profile or a Speaker profile.
- Event Agenda: The below structure can be used for deep linking to the event agenda in the platform.
- My Schedule: The below structure can be used for deep linking to the My Schedule of the user to straight away see their meetings for example.
- Individual Sessions: The below structure can be for deep linking to a specific session on the platform such as a roundtable or sponsored session.
- My Profile The below structure can be used for deep linking to the users own profile for example for easy editing.
- Lists URL: The below structure can be used for deep linking to a specific list, such as the attendee list, or the exhibitor list
Can I use deep linking if I use a custom SSO Protocol?
Yes, but specific structures apply to the URL that might be different than what is outlined in this article.Can I pre populate URLs even if Event Participants are not yet registered in Grip?
No, even if you are using pre-population of URLs its important that Event Participants are already registered in the Grip platform.