Webinar: Transform Your Videos into Valuable Lead Gen Assets

Webinar: Transform Your Videos into Valuable Lead Gen Assets

Book a Demo

Exporting Analytics Data

This article will show you how to export analytics data after your Glisser event.

After your presentation or event has finished you can export detailed audience data from the analytics tab. Click on Export within the appropriate presentation or event and you can choose to export the audience data in the following ways:

Export as CSV

When you download your analytics, you will be emailed a zip file containing multiple CSVs. These CSVs may vary depending on the features you have used, but will generally consist of: 

  • Summary
  • Attendee
  • Poll
  • Question
  • GDPR

All you need to do is click on ‘Export As CSV’ on the right hand column of your Analytics tab and a downloadable CSV link will be sent to your registered email address or an email of your choice.

The email your receive will look like this:


The summary csv contains the high level data from the exported event/session. Note that duplicate attendees are removed based on their identifier, and the identifier is not case sensitive. 

The data in the summary tab would consist of:

  • Event Title: The event/session title
  • Glisser Code:  The event/session GLSR code
  • Attendees: The attendee count for the event/session 
  • Comments*: The total number of Q&A comments posted for the event/session.
  • Rejected Comments*: As above, but only counts Q&A comments rejected by moderators.
  • Votes*: The number of successful poll votes received for the event/session. This removes duplicate responses.
  • Likes*: The total number of liked slides across the event/session.
  • Downloads: The total number of attendees that have downloaded some slides during an event/session. 
  • Polls: The total number of polls asked by presenters during the event/session.
  • Skipped*: The total number of poll skips by all attendees during the event/session.
  • Polls Closed: The number of polls that were closed by presenters during the event/session.
  • Average Engagement Score: The average engagement score for all attendees during the event/session.

* for an event, this is the total across all sessions within the event.

The attendee CSV contains the information for each attendee within the event/session. The data would contain these fields: 
  • Identifier: This is the identifier that the attendee signed in with during the onboarding process.
  • Attended On (UTC): This is the time at which the attendee first joined the event/session, and is always presented in the UTC timezone.
  • Comments*: The number of comments (Q&A) left by the attendee across the event/session.
  • Rejected Comments*: As above, but only includes comments rejected by moderators.
  • Up Votes*: The number of Q&A comments upvoted by the attendee.
  • Slide Likes*: The number of likes given to slides by the attendee.
  • Downloaded?: This is a 1 (yes) if the attendee downloaded any slides across the event/session or 0 (no) if not.
  • Notes*: A count of the number of notes left against slides by the attendee.
  • Skipped*: The number of polls skipped by the attendee. 
  • Closed*: The number of polls missed due to closure by the attendee. 

* for an event, this is the total across all sessions within an event.


The poll CSV includes all poll responses for an event/session. This is not deduplicated, so if an attendee responds to a poll more than once, we will show all of those responses. The data would contain these fields:

  • Poll Id: This is a unique identifier for the poll. Useful if importing into other systems.
  • Poll Name: The title of the poll when presented to the audience.
  • Poll Type: The poll type, will be one of the below.
    • text – free text poll
    • singleChoice – opinion poll or quiz – choose one
    • multiChoice – opinion poll or quiz – choose many
    • starRating – star rating poll 
    • date – date picker poll
    • form – survey
    • lottery – lottery
  • Respondent Identifier: The identifier of the attendee responding to the poll.
  • Response: The answer submitted by the attendee.
  • Responded At (UTC): The time at which the poll was responded to.
  • Poll Vote*: 1 (yes) if the attendee successfully answered the poll, or 0 (no) if not.
  • Poll Skipped*: 1 (yes) if the attendee skipped the poll, or 0 (no) if not.

* Note that Poll Vote, Poll Skipped, and Poll Closed are mutually exclusive, there can only be a 1 in one of the three columns for each poll response.


This shows all questions (Q&A) asked by attendees across the event/session. For an event this is across all sessions within the event. The data would contain these fields:

  • Identifier: The identifier of the attendee asking the question.
  • Question: The question itself.
  • Moderation State: Was the question approved or rejected by moderators.
  • Likes: This shows how many upvotes the question received.
  • Asked At (UTC): The time (in UTC timezone) at which the question was asked.
  • Reply: Shows the reply from moderators, if one exists.

This CSV shows all attendee responses to GDPR during onboarding into a session or event. Duplicates are removed based on their identifier and the latest response is kept. Each attendee will have their own row, and the columns will signify which GDPR criteria they answered in order with a “Yes” or  “No” indicator. 

Export to Salesforce
Salesforce Export Process

To export your Glisser analytics data to your Salesforce account:

  • Select ‘Analytics’ from the left-hand menu bar.
  • Select a presentation session that you’ve presented, and click on the right-hand tool bar to ‘View Analytics’.
  • Click on the ‘Export’ button and select ‘Salesforce’.
  • The first time you do this you will be taken to Salesforce to log into your Salesforce account.
  • Once your Salesforce integration has been authenticated, a modal (pop-up box) will come up. You have the option of adding a Campaign ID which will add each record to the Campaign you have specified as a Campaign Member.
  • You can now begin to pair any fields in Glisser with your Salesforce leads fields (please note that Salesforce labels are case sensitive so copying and pasting is recommended).
  • Once you have paired all the fields click on ‘Export Data’ to export to your Salesforce account under ‘Leads’.

Please bear in mind that if your Salesforce account has any required fields, you must select a Glisser field with data for each user for their data to be successfully exported. Also consider any validation you’ve set on your Salesforce fields (maximum field length, character type etc.).

Salesforce Field Update

When you export an object which already exists in your Salesforce account, any data in those fields will be overwritten. However, if you’d like to keep track of overwritten data it is important to activate the field history tracking setting within Salesforce.

Exporting Glisser Polls to Salesforce for analytics:

For any polls you’d like to export to Salesforce, to ensure their data is exported successfully please make sure that:

  • All polls are set to mandatory to allow for you to capture consistent information from your delegates
  • The types of poll you choose for each question are consistent with the same type of form field in Salesforce:
    • Salesforce Text Field <> Glisser Free Text Poll
    • Salesforce Date Field <> Glisser Date Picker Poll
    • Salesforce Picklist Field <> Glisser Opinion Poll (ensure multi-select answer is unchecked)
Export to HubSpot

IMPORTANT! Before running your first export to a HubSpot account, you must add a Contact Notes property to your HubSport Contacts. To do this:

  • Sign into your HubSpot account and select Contacts from the menu https://app.hubspot.com/contacts
  • Click the Actions button and select Edit properties
  • Click the Create a property button
  • Enter Contact Notes in the Label field (the Internal Name field will populate with contact_notes, it is important that this isn’t changed)
  • Click the Create button

Exporting to HubSpot will need you to authenticate your HubSpot account via Glisser. It will then export all participants of a presentation as a HubSpot Contact in your account, with any additional engagement information in the Contact Notes field. Note that if the participant already exists as a contact in HubSpot then any engagement information will be added to the Contact Notes field of the existing HubSpot contact.

If there are any issues with the export, it could be because of the following:

  • The HubSpot account you authenticated with does not have the Contact Notes field setup as above.
  • The Glisser presentation or event you tried to export does not have ID Capture set to email. Only participants with email addresses will successfully export to HubSpot.
  • One or more of your participants did not enter a valid email address, which have been declined by HubSpot’s validation process.

How increase attendance and reduce cost per attendee?

For more information on how you can use Glisser to increase attendance and reduce cost per attendee, please

How increase attendance and reduce cost per attendee?