Entegy Suite Glossary

Core

Project: Each event is set up as a Project in the Core and can include some or all Suite products and Elements. Projects are created and edited by Core Users.

Standalone App: A custom app with branded app icon, loading screens and dedicated store listing page.

Embedded App: An app embedded in a Portal.

Portal: A container app housing multiple apps.

Enter Code portal: Users will require a unique code to access the app through the Portal.

Tile entry portal: Users select from a list of active app tiles to access the app through the Portal.

Container Page: A group of content pages that is automatically created by some page types and additional sub-pages will need to be created within in (e.g. an exhibitor page type will house a list of exhibitor subpages).

Page Type: Content is stored in the App using page types; each page type is used for a specific type of content (e.g. a schedule page type will be used to build a schedule, and an exhibitors page type lists exhibitor information and allows for them to be mapped onto a floor plan).

Target Page: The page that will link to that item (e.g. icon on the Main Menu linking to related content, where the content would be the target page. Or a Page Banner linking to a Submission Form, where the submission form is the target page etc.)

Click through: Click on an object and be taken to another page (e.g clicking through on a Page Banner takes you to the App Sponsor’s page).

Import: Upload/populate data into the Core.

Export: Extract data or reports from the App or Core.

Project/Core User: Core Projects can be accessed as a Core Users. Different permission levels can be granted depending on a user’s job requirements (e.g. user permissions may be granted to access an entire project or just specific tasks within a project).

Event Code: The custom code that indicates your project/app. Event codes are used when accessing an app in a portal, and using the Capture or Track apps.

QR Code: A code that, when scanned, provides access to information in the app. Can be used in conjunction with Attendee Connect, Lead Capture, Attendance Tracking and Kiosk Manager.

 

Design

Generic Header: A header image that appears on every supporting content and features page.

Feature Header: A header image that can be uploaded for an individual page. This might be used to highlight a sponsor or special event etc.

Phone Menu Background: An image that will appear under your menu icons and phone menu header.

Phone Main Menu Header: A header image that sits on top of the phone menu background. If transparent, this will be placed over the top to blend into the background image.

Tablet menu header: A header image that sits on top of the main menu icon list on a tablet.

Custom Menu Icons: Main menu icons that are uploaded and not part of the default icon set.

Email Header: A header image that appears on all system-generated emails (e.g. forgot login details etc.).

Page Banner: Appear at the bottom of the app and can be used to draw attention to something in the App (e.g. feedback form or special event) or be used as a sponsorship opportunity.

Push Notification Image: An image sent as part of a push notification.

Phone splash/loading screen: A full-screen graphic that appears briefly as the App loads when it is first opened on a phone.

Tablet splash/loading screen: A full-screen graphic that appears briefly as the App loads when it is first opened on a tablet.

iOS App icon: The icon that will appear when the App is downloaded on an iOS device.

Android App icon: The icon that will appear when the App is downloaded on an Android device.

Google Play Store feature image: The header image used as part of the App Store Listing on the Google Play Store.

Interactive Sessions Display Screen Background / Holding Image: A full-screen graphic used between asking live polling questions or displaying a question/comment.

Registration header graphic: A header image for the registration form.

Kiosk background: 5:4: The background image for a Sprintr kiosk.

Kiosk background: 16:9: The background image for other widescreen devices.

Kiosk background: Portrait: The background image or a Sprintr Mini, Portrait.

Kiosk background: 16:10: The background image for other widescreen devices.

Kiosk button: Tap to start: Kiosk button on the main screen before clicking to display the 3 options.

Kiosk button: Register: A check-in option to register through the kiosk.

Kiosk button: Enter Code: A check-in option to enter Attendee Code to print badge.

Kiosk button: Scan QR: A check-in option to scan an Attendee QR Code to print badge.

 

Store Listing

Store Listing: A standalone app or portal that can be downloaded from both the Apple App and Google Play stores. The App is listed with screenshots and related app details (e.g about the app, icon title etc.). This is a requirement for standalone and portal Apps.

Store Listing Details: App or portal details that are submitted with the App. These details can include App Store Title, Icon Title, App Description, Android and iOS App Icons etc.

Store Submission: The process of sending an App to the Apple App or Google Play stores to be listed and downloadable.

Build: The version of an App that will be submitted to the Apple App and Google Play stores. This version of the App has been optimised for the Store Submission process.

Store Account: An Apple App and/or Google Play Developer program account that will be used to submit an App/build.

Apple ID: An Apple account which is used to register for the Apple Developer Program.

Apple Developer Program: The recurring subscription-based service which allows for Apps and Store Listing details to be submitted to the Apple App Store.

Google Account: A Google account which is used to register for the Google Developer Program.

Google Play Developer Program: The service which allows for Apps and Store Listing details to be submitted to the Google Play Store.

 

Profiles

Attendee: Someone attending the event and using the event App (e.g. speaker, sponsor, attendee etc.).

Profile Type: Used to segment profiles into distinct groups such as attendee, speaker etc.

Profile Field: Refers to all profile information in the Core. There are three types of profile fields: Fixed Fields, Identification Fields and Customisable Fields.

Fixed Field: Profile fields already set up by default in the Core (e.g. First Name, Last Name, Organisation etc.)

Identification Field: Used for profile identification in the Core. Attendees can also use these when logging into the event App.

Customisable Field: Created for additional information or to enhance element functionality (e.g. gala dinner ticket, postcode, years of service or alternate contact number).

Custom Multiple Choice Field: Created for additional profile information that has more than one possible answer. Multiple choice fields are the most versatile when working with elements in the system, and increase flexibility with personalisation and data collection.

Custom Text Field: Store the text that has been input that can then be placed throughout the app (e.g. on an attendee’s profile in the profile list). Each project is limited to 10 text fields.

Organiser permissions: Profile types with organiser permissions allow for extra functionality in the app, such as deleting comments from the Activity Feed.

Snapshot: Creates a backup of profile data to be saved and later restored if required. Snapshots can be used to reverse undesired changes made to profiles and/or profile types.

External Reference: A unique string of characters (not limited to numbers) that are populated by an event organiser when profiles are imported (e.g. membership ID, registration number, ticket number etc). This can be used to log into the event App.

Internal Reference: A unique string of numbers that are generated by the Core for each attendee. These are automatically determined when a profile is created and cannot be changed.

Authentication: How attendees will be verified when accessing the app (e.g. login methods, download details etc.).

Access Code: Codes randomly generated by the Core and used for logging into mobile Apps.

Visible in list: An attendee’s name and visible profile information will appear in the profile list.

Allow Messaging: An attendee can be messaged by another attendee.

 

Schedule Builder

Schedule: The collective term for all sessions, session groups, session segments and schedule features that make up an event’s agenda or schedule in the event App.

Abstract: A page type used to manage abstracts or posters by allowing for dynamic links to speakers, sessions and sessions segments.

Stream: Used to differentiate session types in the schedule list view in the event App by utilising colours and visual pills on the session list and on the session page.

Category: Used to help with filtering search results. When linked, a pill displaying the name of the category will appear on the session page in the event App.

Room: The location of your session or social function. Rooms can be created to link to sessions in your schedule.

Speaker: A list of who is speaking/presenting at the event. When linked to a session, speaker names and a link to their speaker page will appear on the session page.

Session: Used to build the structure of a schedule. They can include copy about the session, links to feedback forms and speaker information, as well as the ability to bookmark and take notes.

Session Segment: Used to show segments inside a parent session. These might be used to display an abstract listing, or to add an additional layer of detail to your schedule.

Session Group: Used to group sessions together to show different breakouts or concurrents.

Session Types: Can be linked to a session to allow for additional filtering capabilities. Session types can also be configured to make minor changes to session display in the schedule list view in the event App.

Featured Speaker: A keynote or important international speaker. Linking a featured speaker allows for their headshot and name to display in the schedule.

Session Thumbnail: An icon or image used to represent a session in the schedule. This might include a speaker’s headshot or a custom icon to represent a meal break etc.

 

App Element

Content: The collective term for all page information in the App.

Refresh Content: Update the App to view the latest updates and content changes.

Change event: Switch between event Apps in a portal.

Main Menu: The collection of menu items for Content pages and other features displayed on your App home screen.

Icon: The menu item on your App main menu that links to Content pages and other features.

Coming Soon Message: A message linked to an icon that does not yet have content behind it.

QR Scanner: An in-app feature that enables attendees to scan various types of QR codes.

Page Banner:  Appear at the bottom of the app and can be used to draw attention to something in the App (e.g. feedback form or special event) or be used as a sponsorship opportunity.

Popup message: Messages that appear in the app when a specific page is visited. Popups can either be set to be visible on the first view of the page, or every view of the page.

Push Notification: A message that is sent to attendees at a certain point in time. When enabled, attendees can be notified through their device notifications when a push has been received.

Push notification category: Used to send a push notification to a group of attendees (e.g. Exhibitor-specific information vs general attendee information).

Submission Form: A form used to collect information from attendees through the App.

In-app badge: An attendee’s personal QR code and basic information, which can be used instead of a physical badge or ticket.

Smart Redirect: Used to create content that is specific to a group of attendees (e.g. Main Schedule for all attendees and a Bump In/Out Schedule for exhibitors).

Back to Portal: An icon added to the app Main Menu to direct attendees back to the main portal menu.

Heading Style: Content formatting tool that creates text display variations (e.g. colour, size etc.).

Cell Style: Used to change the layout or design on some container content page types (e.g. change the blank group cell style to create a sub-menu with icons).

 

Attendee Connect Element

Gamification: Create a game out of the app. Attendees can earn points by interacting in and through the App.

Leaderboard: Points and achievements appear in the in-app leaderboard where attendees can view each others’ progress, achievement tally and overall ranking.

Points: Awarded for performing single actions in the app, such as posting to the Activity Feed or viewing a Push Notification. Each action is allocated its own number of points.

Achievements: Awarded for performing specific actions multiple times in the App. Working with the point system, achievements are awarded on top of any points for completing the action

Default Achievements: System-created achievements and point allocations that can be enabled for easy setup.

Activity Feed: A feature that allows attendees to comment on session, speaker, exhibitor and sponsor content pages. These comments will appear on the content page and in the Activity Feed.

Post: When an attendee uploads a message or image to the Activity Feed or comments on a content page.

Messaging: a feature that allows attendees to send private in-app messages to one another.

Profile List: A list of all attendees who are set to visible. This list allows app users to view and search other attendees, send private messages and view other attendees leaderboard rank.

 

Interactive Sessions Element

Live Polling: Enables attendees to be surveyed on a number of questions. Questions can either be pre-loaded, created on-the-fly, or pulled from Live Discussion and Submitted Questions.

Ask a Question/Submitted Questions: Enables attendees to submit questions directly to the speaker. These questions then can be pushed to the display screen to be addressed by the speaker or turned into a live polling question for the audience.

Live Discussion: Can be used to create a social feed specific to a session. Comments from this discussion feed can be pushed to display screens or turned into Live Polling questions for the audience.

Facilitator Dashboard: Used to enable, manage and utilise all Interactive Sessions features.

Session Status: Controls how the audience can view and interact with the session from their mobile device. There are several statuses to choose from.

Session Status: Opening Soon: The session will appear as opening soon. Audience members will be unable to view the interactive session.

Session Status: Accepting Questions: The session will appear as accepting questions. Audience members will be able to ask questions and participate in the Live Discussion.

Session Status: Live: The main state of Interactive Sessions. Used when ready to ask questions. This option enables all three features and allows audience members to vote on questions.

Session Status: Results: The session will appear as results only. Audience members will be able to view the results of any questions that were asked through Live Polling, but will be unable to comment on the Live Discussion or ask questions.

Session Status: Finished: The session will appear as finished. Audience members will be unable to view the interactive session.

Interactive Sessions Display Screen Background / Holding Image: A holding screen used between asking live polling questions or displaying a question/comment. This is essential if you are running Interactive Sessions.

 

Kiosk Manager Element

Kiosk Companion: The Kiosk Companion can be used by event staff to accommodate last-minute changes and attendee preferences onsite from a portable device.

Find a Profile: Use the Kiosk Companion to search for a profile in the list and print directly to a kiosk.

Scan a Code: Scan an attendee’s QR code to view their profile in the Kiosk Companion app. Either update and reprint or print the badge directly to a kiosk.

Add a Profile: Use the Kiosk Companion to add a new profile and print the attendee’s badge directly to a kiosk.

View All:  Use the Kiosk Companion to view a list of all profiles, sortable by printed/unprinted.

Kiosk Status:  Use the Kiosk Companion to see which kiosks need attention such as low ink or paper.

Check-in option: Determine how your attendees will print their badge. There are several check-in options available including Enter Code, Scan QR, Register, Insert your printed/e-ticket and Scan this code via the event App.

Kiosk Check-in Option: Enter Code: An attendee inputs a unique reference code to print their badge.  

Kiosk Check-in Option: Scan QR: An attendee provides their unique QR code to scan to print their badge.

Kiosk Check-in Option: Register: Links to a registration form from the Registration Element to enable attendees to register directly on the kiosk to print their badge.

Kiosk Check-in Option: Insert your printed/e-ticket: An attendee provides their unique QR code to scan at the kiosk to print their badge.

Kiosk Check-in Option: Scan this code via event app: An attendee uses the QR Scanner on the event App. Requires an attendee to be logged into the event App to print their badge.

Kiosk background: 5:4: The background image for a Sprintr kiosk.

Kiosk background: 16:9: The background image for other widescreen devices.

Kiosk background: Portrait: The background image or a Sprintr Mini, Portrait.

Kiosk background: 16:10: The background image for other widescreen devices.

Kiosk button: Tap to start: Kiosk button on the main screen before clicking to display the 3 options.

Kiosk button: Register: A check-in option to register through the kiosk.

Kiosk button: Enter Code: A check-in option to enter Attendee Code to print badge.

Kiosk button: Scan QR: A check-in option to scan an Attendee QR Code to print badge.

  

Lead Capture Element

Lead: The generation of a new potential business client.

Capture App: A downloadable app for mobile devices that exhibitors use to capture leads, take notes and export captured data.

Lead Capture Scan: When an exhibitor team member scans an attendee’s badge/ticket using the Capture app.

Exhibitor Team: All exhibitor booth staff logged into the Capture app under their exhibitor (e.g. Sally, Steve and Alice are all onsite for the event and are exhibiting for Entegy. When they are using the Capture app, they are part of the Entegy exhibitor team).

Team Members: Exhibitor booth staff who make up an exhibitor team.

Event Code: The custom code that indicates your project/app and is used when logging into the Capture app. Can also be used to access the event App in a portal, or log into the Track app.

Exhibitor Access Code: An exhibitor-specific code used when logging into the Capture app. This code can be used by all exhibitor team members when logging in.

Exhibitor Signup Form: Allows exhibitor booth staff to register themselves as part of an exhibitor team. This is used when distributing an exhibitor access code.

Qualifying Question: Questions exhibitor team members can ask captured leads. This can be set, either by the organiser, or the exhibitor team.

Generate Blank Code: The action where exhibitor access codes are generated. Blank codes must be generated to enable exhibitor team members to login using the exhibitor access code.

Exhibitor Code Login Message: An instructional message and event organiser contact details that appear when an exhibitor logs into the Capture app using the exhibitor access code.

Exhibitor Registration Complete Email: A system email that can be sent once an attendee has completed the exhibitor signup form.

Export Fields: The profile fields and information that exhibitors can export in their post-event lead report.

View Leads: View a full list of all attendees that have been scanned through the Capture app.

 

Attendance Tracking Element

Track App: A downloadable app for mobile devices that allows attendees to be scanned into a session or social event.

Attendance Tracking Scan: When an attendee’s badge QR code or ticket is scanned into a session or social event.

Event Code: The custom code that indicates your project/app and is used when logging into the Track app. Can also be used to access the event App in a portal, or log into the Capture app.

Session Access Code: A code generated by the Core to represent a session. Used when logging into the Track app.

Generate Blank Code: The action where session access codes are generated. Blank codes must be generated to access the Track app and scan attendee badges/tickets.

Scanning Point: A session or social event QR code that can be scanned by attendees to track themselves into sessions.

Current Scans: A tally of all scans that have taken place for that session.

Tracking Session Group: A group of sessions that are being held in the same room.

Session Access Rule: Used to restrict attendee access to particular sessions based on profile information (e.g. only attendees who have paid for the gala dinner can attend. Session Access Rule is created to ensure only those paid attendees can enter).

Was this article helpful?
0 out of 0 found this helpful