Check out the new Glisser On-Demand Content Hub
Marketo can now be integrated with Glisser to automate functions such as Entry List and Analytics reporting.
For this example, we will create a web form that sits in a landing page. When this form is submitted the smart campaign attached to this form will run and add the email address, input by an attendee in the form, to the entry list of the given Glisser resource (event or presentation). Please note that all values in this are case-sensitive.
In order to communicate with the Glisser API, you need a verified Presenter account on Glisser with the API flag enabled.
Please check with your Customer Success Manager to see if this is enabled for your account.
This needs to be done by someone with admin access to their Marketo instance. Navigate to the Admin tab > Database Management > Field Management.
Create 4 custom fields on the Person object, all of which are of string type
2. Glisser API Token
3. Glisser Resource Type
4. Glisser Resource ID
For fields 1 & 2 (the relevant authentication tokens we require) please make sure that Mark Field as Sensitive is checked:
Next, we need to create 3 webhooks to communicate with the Glisser API. Navigate to the Admin tab > Integration > Webhooks.
In the template section, replace your.email@glisser.com and YOURpassword123! with your relevant Glisser account credentials.
URL: https://api.glisser.com/user/login
Payload Template: email=your.email@glisser.com&password=YOURpassword123!
Request Token Encoding: None
Request Type: POST
Response Format: JSON
For this webhook we need to set a response mapping, select EDIT next to the Response Mappings section, like so:
Response Attribute: token
Marketo Field: glisserAccessToken
2. Glisser API Token
URL: https://api.glisser.com/user/api-token
Request Token Encoding: None
Request Type: POST
Response Format: JSON
For this webhook we need to set a response mapping, select EDIT next to the Response Mappings section, like so:
Response Attribute: apiToken
Marketo Field: glisserAPIToken
For this webhook we need to set a custom header, select the Webhooks Action dropdown > Set Custom Header, like so:
Header: Token
Value: {{lead.glisserAccessToken}}
3. Glisser Add to Entry List
URL: https://api.glisser.com/{{lead.Glisser Resource Type:default=event}}/{{lead.Glisser Resource ID:default=''}}/whitelist/add
Payload Template: identifier={{lead.Email Address:default=''}}
Request Token Encoding: None
Request Type: POST
Response Format: JSON
For this webhook we need to set a custom header, select the Webhooks Action dropdown > Set Custom Header, like so:
Header: Token
Value: {{lead.glisserAPIToken}}
When setting up the mapping between a Glisser resource (event or presentation) and a form, we use a smart campaign in Marketo to run the webhooks above and send the email address in the form to the Glisser resource’s entry list. For each Glisser resource we map them to a given resource type and ID in the flow.
From the Marketing Activities tab, create a landing page and a new form, or use an existing one. As a minimum, the form must have Email Address set as an input for the user to complete. All other inputs will be fed into your Marketo instance but only the email address will be sent via API to Glisser.
Navigate back to the Marketing Activities tab, and create a new Smart Campaign. Here we are mapping the form submission to the Smart Campaign that will then call the chain of webhooks. I’m storing this new Smart Campaign in the Web Forms folder.
Navigate to the Smart List tab of your newly created Smart Campaign. Locate and drag Triggers > Fills Out Form. Find the form you’ve created or an existing one that you want to use and select it from the dropdown, like so:
Next, navigate to the Flow tab. We need to ask Marketo to map 2 dynamic variables (Marketo refers to these as tokens), 2 static variables (to point at the given Glisser resource) and call our 3 webhooks that we created earlier. From the right hand sidebar, select & drag 4 Marketing > Change Data Value actions, and fill them out with these mappings:
Attribute: Glisser Access Token
New Value: {{lead.Glisser Access Token}}
2. List
Attribute: Glisser API Token
New Value: {{lead.Glisser API Token}}
For 3 & 4, you need to retrieve this from your Glisser account. If it’s a standalone session you are running, then the the resource type = presentation while if it’s an event you are running, then resource type = event. The ID is retrievable from the URL after selected e.g:
https://present.glisser.com/events?selected=823601https://present.glisser.com/presentations?selected=71814013. List
Attribute: Glisser Resource Type
New Value: Your resource type. For this example we have used event.
4. List
Attribute: Glisser Resource ID
New Value: Your resource ID. For this example we have used 363.
We now need to create 3 Call Webhook actions, so from the right hand side bar locate & drag Integration > Call Webhook below your previously created actions and select the webhooks in this order below:
Your Flow should look something like this:
One last important step is required. Navigate to the Schedule tab. The Glisser entry list prevents duplicates from being added. Therefore, it makes the most sense to setup your Smart Campaign to do the same so that you can maintain consistent data across both platforms.
Therefore, it is recommended that you set If person has been in this Smart Campaign before to Each person can run through the flow once. Then, ACTIVATE your Smart Campaign to ensure it runs when your form submits.
Please note: If you do not activate the Smart Campaign, the Flow will not run and the registrants will not be added to the relevant Glisser entry list.
You are now all set up! Navigate to your landing page, fill in the form and submit to test. The flow is called immediately but may take a few minutes to appear in your Glisser entry list given there are a few legs to this back-and-forth via API.
If you run into issues, this will normally come from the chaining of the webhook calls as this is the most complex part of the process. Logging for these is available from the Results tab of your Smart Campaign. All error codes from the Glisser API are web-standard HTTP status codes so will convey information on what is going wrong in the process.
For more information on how you can use Glisser to increase attendance and reduce cost per attendee, please
