Ingage Product Glossary

Trying to understand something that's not defined here? Ask us in a message — and we can add it to the list!

The key to interactivity in an Ingage presentation are Actions. Actions can be added to Components to create touchable/clickable elements on a page that will either disclose more information on a page or perform a discrete action like navigating to a different page or presentation.

There are 8 distinct actions supported by the Ingage suite:

In the Component menu are three pre-styled ways to add Actions to a presentation

Every time a user presents a presentation from either our Desktop or iOS app, we capture and store all the usage data from presentation views to button views. Company administrators and analysts have access to this data which can be presented and queried from our Teams Console. The following events are captured and stored:

When we capture the events above, we record extra data about the event that include data points like the name of the presentation, the team that the presentation was presented from, the time, the duration of event (ie. how long was the user looking at a particular page), and much more data.

From the Teams Console, administrators or analysts can view, filter and drill down on specific data points to answer questions like “who is the most active user”, “who is the least active user”, or “what is the average duration spent viewing a particular presentation”.

Analytics tags are special codes that can be added to the end of a web or deep link that will identify a specific user in Ingage’s Analytics. When a users sends a web link to a customer they can append this special code, then when the administrator views the analytics in the Teams Console, they will be able to identify if the user opened that web link. Here is what a weblink looks like with an Analytics Tag:

https://web.ingage.io/xDefHz?c=vincent_vega

Notice the ?c=vincent_vega – this is the analytics tag. When this link is opened, our analytics backend will capture all events for the presentation view and record the analytics tag so that an administrator can filter to see if the weblink with this tag was accessed.

On the iPad users can enable a special mode that allows them to draw (annotate) on their screen. They can use either their finger or an Apple Pencil to draw annotations. They can use these annotations to highlight certain parts of the presentation for visual effect. The annotated screens can be shared to the user via Text Message or Email. Annotations mode needs to be enabled on the iPad. It can be turned on by clicking on the Gear icon at the top right hand corner of the library. This opens the Settings screen where Annotations Mode can be enabled. Once enabled, a new annotations button will be visible on the Navigation Bar when presenting a presentation.

Ingage has two client applications:

The Desktop application is a cross platform application that runs on either MacOS or Windows. Most users tend to use our Desktop application for editing presentations as designers find it more efficient to design in a desktop environment with the fine control of a mouse.

The iOS application runs on either an iPad or an iPhone. The iPhone app is not as capable as the iPad app and has no editing capabilities. Most users use the iOS app for viewing presentations.

A company is the primary organizational unit in Ingage. Most of our customers will be a member of one company, though it is not uncommon for some customers to be a member of other companies that support guest teams. Each company can have an unlimited number of teams where common users can be grouped.

Deep links are special URL’s that instruct a user’s Operating System – like Windows or Mac OS – to open an application to a specific location. You actually use deep links every day when you use your web browser. When you open the URL https://google.com, you are telling your operating system to open the web page at google.com in your web browser. The operating system knows to open the web browser because the url begins with https:// – this is called an URL Scheme and is the instruction the operating system uses to know to open a web browser.

An Ingage Deep link looks very similar to a website URL except instead of beginning with https:// it begins with ingage:// – when the operating system sees an URL that begins with ingage:// it scans the computer for an installed app that is capable of opening our link – in our case this would be our Desktop app on MacOS/Windows or our iPad app on iPadOS/iOS.

Deep links can be generated in the Teams Console, our Desktop Apps and our iOS app. These links can be copied and shared via email or text message. Some of our partners like Leap allow customers to enter Ingage Deep Links directly into their platforms to enable a seamless integration between our two apps.

An example Ingage Deep Link is a combination of the URL Scheme, and action (can be present or edit and ends with a presentation share alias. Generally they look like this:

ingage://present/sY74cv

Design components are the basic building blocks of a presentation. Components are added to a page using the Ingage Page Editor. Ingage offers both static and interactive components.

Static components are components that cannot be interacted with. They are static page elements.

Interactive components are components that the user can interact with to perform actions or change the behavior of the component.

Dynamic Content is a platform feature of Ingage that enables you to update their presentation content at runtime based on data that:

Every company gets basic Ingage User, Team and Company profiles and do not have the ability to create additional custom profile fields. Companies on our Enterprise tiers can create additional custom profile fields.

Importing documents into Ingage provides a quick way to allow you to transfer your existing presentations or documents into an Ingage presentation. Ingage supports 4 document types for importing on both the iPad and Desktop apps:

When importing any of these files, an Ingage page will be created for each page in the imported document. The page will contain an image that represents each page in the imported document. It’s important to remember this – because the page is imported as an image, any text on the page WILL NOT be editable.

Ingage ships with a basic set of fonts. These fonts have been chosen by our design team and work particularly well in the context of a presentation. Admin and Creator level users can upload their own fonts into Ingage to maintain brand consistency across all of their marketing channels. Fonts can be uploaded through our Teams Console Website or in both of our client applications.

HTML Pages are a special type of page in Ingage where creators can use custom web content to provide additional interactivity or even small web applications in your Ingage presentations. An example of a small web application is Ingage's PriceKit.

HTML pages require knowledge of, and the ability to create or outsource your own HTML content. Once you have developed HTML content, all you need to do is compress the HTML page(s) into a .zip file and upload into the Ingage HTML page, or ideally an Embed Component.

NOTE: HTML Pages have been deprecated and we encourage the use of our more flexible Embed Component.

Guest Teams are used to provide access to presentations owned by a Manufacturer. Guest Administrators can add Guest Viewers to their teams providing access to the content that has been shared by the Manufacturer.

The inspector is a common space on the right hand side of the Page Editor and Presentation Storyboard. Inspectors have widgets that can be adjusted to change the behavior or look and feel of the currently selected item. Inspector widgets are designed to serve a range of functions yet never let the user get into a situation where they can break something.

Integrations are ways that Ingage can work somewhat seamlessly with other applications or web services. Ingage supports the following integrations:

Further descriptions of these items can be found below.

Deep links are by far the simplest way of integrating with Ingage. A few partners like Leap, Paradigm Vendo, and One Click Contractor can already work with our deep links and offer a seamless way to navigate back and forth between Ingage and their applications.

Two call coaching services (RillaVoice, Siro) use our Analytics Public API to enrich their call coaching data with analytics events from Ingage. This provides a richer coaching experience for the customer.

Public API’s are much more complicated and generally require the customer to have their own engineering team to integrate. Customers who are interested in our Public API integrations should speak to the engineering team to request documentation and coordinate any integration efforts.

A linked presentation is a presentation that has been opened using an Open Presentation button. It is a simple plain old presentation – there is nothing at all different about it except in the manner in which it’s been opened. You will see this term used in Session Analytics to differentiate between the session user’s main presentation and any presentation that was opened with an Open Presentation button.

When presenting a presentation the navigation bar is visible across the bottom of the screen. The navigation bar has a number of buttons that allow you to easily navigate through your presentation:

The navigation bar can be styled by a creator or administrator in order to have the navigation bar reflect the brand colors used by the company.

A key feature of Ingage Presentations is that they can be easily presented in a non-linear manner. This means a user can present pages in almost any order they wish. This non-linear navigation is exposed by clicking on the section buttons in the presentation’s navigation bar, tapping on the “All Pages” button in the presentation’s navigation bar, and/or using the Go To Page button within a presentation. Note: a company administrator can turn off the “All Pages” button if they prefer to prevent their users from skipping around a presentation.

Pages are where users place static design components (Images, Text, etc.) and interactive design components (Buttons, Compares, Scrollmotions). Pages can be organized into sections.

The page editor is where users add content to the pages in their presentation. The page editor supports many of the features of other editing tools like copy/cut/paste, undo/redo, multi-selection. The page editor supports many of the same editing conventions that are provided by default on the host operating system. The page editor has two main areas:

Items can be added to the Page Canvas by tapping or clicking on the new component button (a plus sign) on the main application’s toolbar. Once components are added, they can be selected, resized, reorganized, or have their behavior and look and feel changed through the Inspector.

Premium Content is enhanced interactive content that can be added to a customer’s presentation. This content is typically created using web technologies (HTML, CSS & JavaScript) and embedded into an Ingage Embed Component. Premium Content is offered as Page Templates via the Ingage Content Marketplace. Once installed, these page templates can be added to any Ingage presentation and customized to fit the user’s use case. Examples in the page templates are common configurations that can be used as is, or can be tweaked by the customer to match their requirements.

Current Premium Content offerings:

A presentation contains a selection of pages that help the presenter tell their story. These pages can be organized into sections allowing for non-linear navigation.

The Presentation Library is the first view seen when opening our client applications. It contains two window panes:

When a user begins editing a presentation they are taken to the Presentation Storyboard screen. This screen shows the user a list of all pages within the presentation, organized by section. Users can click on a page to begin editing it, or they can create a new page by clicking on a button that has a large green plus icon on it.

Users can also manage the pages from the Presentation Storyboard by selecting pages and choosing options by right clicking (Desktop) or long-pressing (iOS). Some management options include deleting, duplicating, copy/pasting and reordering.

The Presentation has a sidebar inspector that lets the user choose some advanced options for the viewing experience like applying a new theme or showing/hiding the All Presentations button.

All Ingage Presentations are downloaded and saved locally to a user’s device. This allows the user to present their presentations even while not connected to the internet. When an update is made to an Ingage presentation, all users who have access to that presentation will receive updates the next time their device is connected to the internet and they open the app. This ensures that every Ingage user in the field will almost always have the most up to date presentation in their library.

Each time a user edits an Ingage presentation a new version is created in our database. The viewers of the presentation always see the most current version, but it’s worth noting that Ingage Support can help you roll back a presentation to a previous version on request. If you're in need of a previous version of your content, please file a support ticket.

Ingage Presentations can be easily shared to the web. When a presentation is shared to the web, it becomes available on Presentations Web – aka PWEB. Presentations that are shared to the web are given a public url that begins with https://web.ingage.io followed by a path that contains a short-code. A full web shared presentation url will look something like this:

**https://web.ingage.io/xDefHz**

Presentations can be shared from within our Teams Console, our Desktop App and/or our iOS app. It is important to note that any presentation shared to the web can be viewed by ANY person in the world who has a link to the presentation’s web URL.

Take your presentation to the next level with the new PriceKit, Ingage’s answer to solving the most common issue sales reps face: presenting the value of a project. To close more deals, homeowners need to understand the value of the investment they’re making with you, but scribbling numbers on a sheet of paper or putting them in a spreadsheet is confusing and wastes time.

With the PriceKit pages, you can go directly to the source by showcasing customized pricing and financing options to help customers grasp the value of your product offering in a way that seamlessly flows with your existing sales process.

Whether you prefer to share simple price comparisons, offer discounts or show financing options, this collection of pages allows you to provide customers with the essential information they need. Plus, they’re easy to set up; just select the page you like, add it to your existing presentation and input your company’s unique pricing information and voila! Your team is ready to close more deals with immediate pricing information.

Profile Builder are a series of screens in our Teams Web Console that allows users to customize their:

These profiles support the Dynamic Content capabilities of the Ingage platform and can be leveraged by premium content templates like Profile Pages.

Profile Pages are a series of page templates that can be installed via the Ingage Content Marketplace. These page templates are pre-configured and designed to leverage user, team and company profiles.

The unique nature of Ingage presentations allow the presenter to control the narrative of the presentation by progressively disclosing information when the time is right. Instead of the traditional way of presenting content with tons of images and “walls of text” on a single page, Ingage allows users to move that content into buttons. The presenter can choose the right time to disclose the information by tapping or clicking on the button to allow – or choose not to present it at all if they feel the content behind the button will not be relevant to the viewer.

API is an acronym for Application Programming Interface. It’s a common set of instructions for two computer systems to talk to each other. It allows one computer system to execute code on another system and get a result back in return.

APIs generally have a layer of security enabled to ensure that the system calling into the API only has access to the information that belongs to the caller. This security is commonly solved using API keys that are generated on the target API. API Keys for Ingage can be generated in the Integrations tab in the Teams Console Website.

Ingage currently supports three public APIs:

The Automation API allows another service to pass data into our API, and in return our API reads that data, creates a presentation based on that data, then returns to the user an URL to a web shared version of the presentation. The calling service is required to have a special presentation in their company that has special “automation tags” embedded in it. Automation tags can be specified in our Desktop Page Editor.

The Analytics API allows another web service to automatically extract our analytics data into their own Business Intelligence tools for additional analysis beyond what our Teams Console offers.

The User API allows customers to add users to their company and assign those users to a role and team.

Customers will likely require their own engineering teams to write the code to interact with our Public API’s.

Pages can be organized into sections. Sections allow content to be logically grouped and assist in helping the presentation tell a story. When presenting a presentation, the sections are displayed as clickable buttons in the presentation’s bottom navigation bar. This enables non-linear navigation through a presentation.

A share alias is a unique short identifier that can be used to identify a presentation. The share alias for an Ingage presentation can be identified by looking at the presentations deep link. An example Ingage Deep Link looks like this:

ingage://present/sY74cv

The share alias it the code that follows present/. In this example, the share alias would be sY74cv

Single Sign On is a technology that permits a user to use one set of login credentials — for example, a name and password — to access multiple applications. SSO is very popular with enterprise organizations because it eases the management of users, credentials and security across multiple SaaS applications.

Ingage supports SSO as an integration. If you are interested in discussing SSO for your organization, please reach out to your account manager.

Companies can organize their presentations into Teams. Teams need to have members assigned to them, hence the term “Team”. Members of the team can have different roles assigned to them that determines what they can do to/with the presentations in the team.

The Teams Console is for Ingage company administrators or guest administrators who can manage their company’s users, teams and presentations. From this website you can also view their analytics to measure your salesforce’s adoption and usage of the Ingage Suite. New product features can be accessed through the Teams Console including accessing content in our Marketplace.

Most systems that support multiple users, have ways to group users by the types of work they are able to perform within the system. In Ingage, we call these User Roles. Every user on the Ingage platform has a role and each of these roles provides a unique set of permissions.

There are two categories of roles in Ingage:

Company Roles are the default role that a user would have when they are added to a team. For example, if a user has a company role of “Viewer”, when they are added to a team they will be given that default role. In the special case of the a Company-Level “Analyst”, if the user has the Company Role of Analyst, they can view Analytics for any Team they’ve been added to regardless of Team Role.

Team Roles specifie the role that a user actually has on a team. A user could have a company role of “Viewer” but could be given a higher role like “Editor” or “Creator” on a specific team.

There are a number of default roles available in a new Ingage company:

If the company has Guest Teams enabled, the following additional roles are available by default:

While the above roles work for 99% of all Ingage customers, the Ingage platform allows for custom roles that can be created for unique use cases.

Example(s):

User 1 with these Roles and Permissions:

What can User 1 do?

User 2 with these Roles and Permissions:

What can User 2 do?